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.

    • CyberTailor@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      1
      ·
      7 months ago

      Right. However, instances hosted in Russia can’t federate with lgbtqia.space anymore.

      • db0@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        20
        ·
        7 months ago

        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

      • tourist@lemmy.world
        link
        fedilink
        arrow-up
        9
        arrow-down
        1
        ·
        7 months ago

        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?

        • CyberTailor@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          9
          arrow-down
          1
          ·
          7 months ago

          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.

      • hemko@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        7 months ago

        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