Games do not fall under this law, as they are already have laws around age restrictions. So if you can buy Minecraft they you are allowed to play Minecraft..
Verification only needs to be reasonable. For us a system something what you have suggested would be reasonable for us. And/Or use a content warning popup like other NSFW sites. By continuing you are agreeing that you are 16 years or older etc...
I think by doing that and modifying the signup process it will be reasonable enough. Considering these laws are clearly not targeted at us and any watchdog will be targeting the "major" social medias like that TokTok site and the FaceSpace.
I was initially super sceptical about it but I think there is a way to navigate it while not compromising our ideals. (Which I kinda need to write in a more concrete fashion!)
To be fair on the EFF it has been less than a week and the requirements are still very much in the air. The minimum user count is drumroll 2. I forgot to include this lovely picture for the exact wording.
Thanks. I might wait until .8 then.
I too would love to know what your experiencing (so I can fix it!)
I made sure that cerbot did an nginx reload after it provisioned the cert.
Article says the initial compromise of the non-airgapped systems is an unknown vector. So how they got into the organisation(s) in the first place is still a mystery
Turns out it wasn't the certificate, but the post-renewal restart of the web-server wasn't working.
We've fixed that up and now LW content is coming in hot and fast!
This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn't look at it yet).
So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
Or use something as self hostable like hydra.
Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
The best part, if you don't agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.
Hope that gives you an idea behind why this feature is warranted.
Possibly, as it's one generic endpoint, but it also blocked a few other things people in the fediverse created, which are mighty helpful in diagnosis of these and other issues.
So using some AI model or whatever CF uses is probably not going to be the best thing for us as it classified a POST request as a crawler?? ๐คท
I'd have to whitelist every regular endpoint as well and then it gets messy as CF only gives you so much control as a free user.
So, for the moment I've blocked the most annoying ones based on UserAgent.
We enabled the CloudFlare AI bots and Crawlers mode around 0:00 UTC (20/Sept).
This was because we had a huge number of AI scrapers that were attempting to scan the whole lemmyverse.
It successfully blocked them... While also blocking federation ๐ด
I've disabled the block. Within the next hour we should see federation traffic come through.
Sorry for the unfortunate delay in new posts!
Tiff
๐