this post was submitted on 11 Apr 2024
204 points (98.1% liked)

Fediverse

28465 readers
482 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

Admin team of LGBTQIA.Social Mastodon instance received abuse email from Russian censorship agency, where they demanded to remove an account. The account in question represented a small group that ran a collaborative blog for LGBTQIA youth and adults in Russia.

Shortly after refusal to comply with agency's demands, the instance was blocked and is now unreachable from Russia.

All previous blocks of Fediverse instaces in Russia were related to hosting CSAM.

you are viewing a single comment's thread
view the rest of the comments
[–] rglullis@communick.news 32 points 7 months ago (2 children)

But blocking the instance at the DNS level does not stop the content from reaching other Russian instances, right? They would have to basically track every server that is federating with them and block like this.

[–] CyberTailor@lemmy.world 21 points 7 months ago (4 children)

Instances hosted in Russia can’t federate with lgbtqia.space anymore.

[–] Vorticity@lemmy.world 30 points 7 months ago* (last edited 7 months ago) (1 children)

Other instances hosted outside of Russia but available from inside Russia can still federated with them, though, right?

[–] CyberTailor@lemmy.world 15 points 7 months ago (1 children)
[–] aniki@lemm.ee 13 points 7 months ago (1 children)

Yeah this seems like a total misunderstanding of how activitypub works from the orks. Not surprising a bunch of fascist idiots don't understand modern federation technology.

[–] abrahambelch@programming.dev 16 points 7 months ago

And it once again shows why federated social media rocks 😎

[–] rglullis@communick.news 13 points 7 months ago

You could fix it with a relay, or having the instances conn extend with the rest of the Internet through a VPN/proxy.

Yeah, a PITA but can still be worked around.

[–] Damage@slrpnk.net 7 points 7 months ago (1 children)

If it's a DNS block I guess Russian instances just need to direct the domain to the IP address in their hosts file

[–] CyberTailor@lemmy.world 9 points 7 months ago

It's always IP + DNS + Deep Packet Inspection. To access blocked websites, you have to use some sort of proxying.

[–] cabbage@piefed.social 3 points 7 months ago (1 children)

Curious - would boosts from users on non-blocked servers bypass the block here? In other words, does traffic for boosts go via the original instance, or is it direct between the boosting and the receiving servers?

[–] CyberTailor@lemmy.world 4 points 7 months ago (1 children)

does traffic for boosts go via the original instance

That way. You can't trust a third-party instance to proxy content, every server has to get its own copy.

[–] cabbage@piefed.social 6 points 7 months ago

Fair point, would be an incredibly easy vector for abuse in any other way. Good thing I'm not a software engineer.

[–] CyberTailor@lemmy.world 7 points 7 months ago (1 children)
[–] rglullis@communick.news 11 points 7 months ago

They know it already.

Anyway, it is interesting that this particular case is better handled by something like Nostr.