I hope there's a useful error message, that could be very annoying to troubleshoot.
We did include a meaningful response body to help.
I image with how techy and fos lemmy tends to be, I'm sure there's a ton of people using VPNs, so a lot of people will probably run into that issue.
It'll come up in a curl or httpie request. All our WAF errors have meaningful returns, I make sure of it ❤️
I know I’m late to the party here, but sadly there is nothing obvious if you are on a desktop browser. The only feedback you get is an endless spinning gear.
I just found this post from a search and I’m sad I can’t connect with a VPN. :(
Ah, yeah, I wish there was a better way to let clients and browsers know. I'll add a note to the sidebar at least.
What do you mean when you say a "response body"? What is it ? Does it show anywhere in a browser ?
That's a bummer that CSAM is still being posted. I get that y'all need to stop the people posting it immediately, and I agree with whatever you need to do to make that happen. However, I hope you can find a solution later down the road that allows VPN users to continue fully interacting with the site.
Indeed. I don't use the Internet at all without a VPN connected. These days you can't possibly be blocking people for that reason. There are other ways to find child porn or whatever. Like calling the authorities.
Since lemmy.world is on cloudflare, a worker function could disallow images in comments (or POST to any of the routes that create content) from those IP ranges. I assume the driver here is CSAM and other problematic imagery.
We've looked into worker functions before for other things like routing on the edge (neat stuff). We're all DevOps folks, and love to get feedback from the community ❤️
The issue is even folks linking to images unfortunately. Yeah, it's mostly CSAM related, but also prevents other types of abuse as well.
I appreciate everyone being understanding, all of us try hard to keep everyone on LW (and folks we federate with) safe.
Yeah, my main thought was if the body contains any kind of URI/url from those IP sources, you could drop it as you are now. Or possibly just 
