Leaderboard

I figured it out, I had a mix of problems. DuckDuckGo, the search engine in the URL bar of all my browsers except Brave, kept taking me to this URL: "https://adult-fanfiction.org/" -- All the FireFox browsers display "trimmed URLs", that look like this: "adult-fanfiction.org" My problem was I couldn't see that I didn't have the proper link. I'm disabling the "trimmed URL" feature in each of my browsers for the future. I think the age verification should have a link like, "Having trouble? Click here and try again.", to ensure that all visitors will be in the right place, even if they can't tell. -- Thank you DemonGoddess, your help was appreciated.

The coder tested on Firefox. Did you clear the cache and cookies for ALL TIME, restart your browser, and then go to https://www.adult-fanfiction.org?

I checked again with FireFox, TorBrowser, DuckDuckGo, LibreWolf; this time with all their cookie restrictions turned off completely, I still get the same result. If you go directly to the Archive, you won't get past the age verification. If you go to the Forum, don't click anything, then go directly to the Archive, you won't get past the age verification. If you go to the Forum, use a link to "https://adult-fanfiction.org/", from within the forum, then the age verification works. I've tried this on Android 13, Windows 10, Zorin 18 and Debian 13; A phone, two PCs and a laptop. I think there may be something wrong with the Age Verification prompt, at least in regards to browsers based on FireFox, because no other site acts that way for any of my other devices or browsers. At the very least, maybe there should be a warning on the age verification that it may not work with browsers based on FireFox. -- Am I the only FireFox user here?

It sounds like in your Chromium based browser, you allowed the new cookie to be set. Whereas in Firefox you have not.

Numbers…. for several mine (I generally record in the mornings): Dale’s Game – Jan 1st @ 3704. 20th @ 3711. 28th @ 3791 Repair Guy – Jan 1st @ 5087. 20th @ 5099. 28th @ 5238. Jefferey – Jan 1st @ 19218. 20th @ 19261. 28th @ 19514. Thus, many dozens/hundreds. So if it’s genuine on the increase, that’s good. If it was, for whatever reason, being under-counted before, and that’s fixed, that’s good. My worry was it being bogus due to a glitch as I know how code can go.