Russia's first politically motivated block of a Fediverse server
Russia's first politically motivated block of a Fediverse server
cross-posted from: https://lemmy.world/post/14155096
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're viewing a single thread.
This can be easily circumvented using an alt Fediverse instance, right?
Right. However, instances hosted in Russia can't federate with lgbtqia.space anymore.
Hm, I feel that should be easily worked around through proxies, but the problem is that the Russian authorities would go after those russian instances then
Could a Russian instance federate with an unblocked instance (e.g. lemmy.world) which federates with lgbtqia.space and then federate lgbtqia.space by proxy?
Or does the protocol not work like that?
Russian instance users can still read comments from LGBT instance users if the comments are left on .world though, right?
Or does the protocol not work like that?
That's technically possible but no major fedi software implements it because you can't trust a third-party server.
Would it be possible to have a shadow instance with the only purpose of circumventing blocks?