- cross-posted to:
- fediverse@lemmy.world
- cross-posted to:
- fediverse@lemmy.world
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.
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?
That’s technically possible but no major fedi software implements it because you can’t trust a third-party server.
No, but the users could just create account in any other instance federated with the blocked instance
Or just spin up a new one in heitzner or something
Russian bank cards are accepted virtually nowhere, and only few hosting operators accept cryptocurrencies.
Yeah true. So other instances is the best bet, and better used over tor to mask the connections
But hosting ops do accept crypto. Have a look on https://monerica.com
Would it be possible to have a shadow instance with the only purpose of circumventing blocks?