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 (13 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 (10 children)

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

[–] cabbage@piefed.social 3 points 7 months ago (2 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.

load more comments (7 replies)

load more comments (9 replies)