Shit's not looking good, and like OP I doubt the uniparty would stop this madness at this point. But I'm not looking to implement any of those invasive age check bullshit.
Now, if someone comes up with a non-invasive way that's not a PITA to implement (like browser sending an is-adult header with every HTTP request, then I can just deny every request with is-adult: 0 in nginx config), I might implement that (there has been some push to move this whole shit into OS level anyway, but none of the tech illiterates managed to ask the question how would this work on a non walled garden platform).
So long story short, unless there's some easy workaround, I'd rather go underground than comply with this ridiculous idea.
But anyway, according to bill, covered platform is:
>(A)that is accessible by the public;
>(B)with respect to which more than one-third of the material made available thereon is sexual material harmful to minors; and
>(C)with respect to which the provider of such platform knowingly makes available the sexual material harmful to minors described in subparagraph (B).
As soon as the ratio of nsfw is under 1/3, no verification needed. So time to create a /slop/ board, then ask the AI to write an 5000 page essay why big gov is good for you and vax is safe and effective and whatnot, and fed whatever nonsense it spits out into /slop/ :D (Even though to do this, I'd probably need to download a non-uncensored model to prevent accidental wrongthink appearing in the output.)
One thing I'd need to think about is moving the servers somewhere else from burgerland. BuyVM has a datacenter in Switzerland, as far as I can see they didn't attempt age verification bullshit yet, and since they're not part of the EU, bullshit usually takes a bit more time until it reaches them, while still being a place where you have infrastructure. Downside is loli seems like a grey area https://en.wikipedia.org/wiki/Legal_status_of_fictional_pornography_depicting_minors#Switzerland
We could look into other countries too, but given the trajectory of things, this is a temporary solution at best.
>>1777
What you could do is redirect the user to chanauth with referrer-policy set so they don't get the referrer, and in a hash parameter (after the #) send the url of your site. What's under the # is never sent to the server, but available to javashit on chanauth. So after successful verification, chanauth can send you back to your original site (with the auth code), making the whole thing more convenient while still masking which site asked for the verification code from chanauth. The downside is if chanauth gets compromised, it's trivially easy to inject a script which will collect these query parameters.