It has nothing to do with protecting children, and everything to do with backdooring the linking of adult IDs to social media accounts in case of wrong-think

I’ve reviewed their votes and there’s nothing to suggest they interact with your account regularly or are manipulating any downvotes.

❤️ im glad people enjoy them :)

Apparently he is coming back to youtube soon

[email protected]

I thought scientifically water actually wasn’t wet, rather that it makes other things wet by adhering to them.

Gonna have to look up some peer reviewed studies now.

Like mastodon in SSH (and yes, no blocking the line!)

Incredibly niche! :)

Probably why i like it so much.

Not seen one more detailed than this, although worth checking against fedidb.com - also, missing my new favourite from the list, stegodon (stegodon.social, stegodon.zip)

Come with us Charlie!

.ml banned the mod

Ah good, what everyone said would happen is exactly what is happening.

Sure its not the data verification company directly, but proves that the whole process is so sufficiently complex that your ID could end up with multiple different providers and then be stolen. Not great.

It’s very annoying.

FYI these are all on ASN 49453

The other (lazier) option is to block/challenge the ASN

Always knew I was a chatbot

My response wasn’t regarding the geoblock, but to the above poster saying we block VPNs (which isn’t true)

But just so you’re aware, we dont geoblock federation traffic and all our posts, comments etc are federated without issue.

The only thing geoblocked is the UIs, so UK visitors can’t access the UI.

If your client tries to direct you to lemmy.zip rather than the crossposted article, then that client isn’t working properly and you should log a bug. Like any crosspost, the content federates fine.

Hope that clears it up for you.

Sorry but your posts are FUD. You’re trying to equate people misusing tlds (which happens across many other tlds) as somehow lemmy.zip is “bad” instance that should be avoided.

Not only is that not true, you are also purposely misunderstanding how federation works as if youre somehow safer not interacting with lemmy.zip. Again, not remotely true.

If you want to block .zip TLDs you go for it, no one is stopping you, but you may as well block .com TLDs while you’re at it as that’s where most scams take place.

Just to clear up, you aren’t interacting with lemmy.zip communities directly from your instance. You never directly interface with lemmy.zip, instead the servers send copies of posts and comments between eachother.

There is no risk from lemmy.zip (obviously) - its a lemmy instance that’s been around over 2 years and is perfectly legitimate. There’s just as much risk from every other tld where people intentionally misspell company names or try to insert similar looking characters. Practice basic Internet security (i.e. dont click on links you aren’t expecting) and you’re pretty much covered.

We dont actually block VPNs, but we do block ASNs where we get abuse traffic. Just so happens that Proton VPNs servers in France are on that ASN.

Hey dont share my email out 😡

I don’t use it currently (except on one of the front ends we use as a test) but I believe the easiest way would be to use nginx to separate the paths you want to pass traffic to, so it doesnt apply to api traffic etc, only the ui. I use traefik for piefed so I don’t know how it integrates in there yet, but I know a few people have got it working for lemmy by using the nginx paths.

There is also go-away as an alternative option.

I have made extensive use of cloudflares challenges too