Original post: https://bsky.app/profile/ssg.dev/post/3lmuz3nr62k26
Email from Bluesky in the screenshot:
Hi there,
We are writing to inform you that we have received a formal request from a legal authority in Turkey regarding the removal of your account associated with the following handle (@carekavga.bsky.social) on Bluesky.
The legal authority has claimed that this content violates local laws in Turkey. As a result, we are required to review the request in accordance with local regulations and Bluesky’s policies.
Following a thorough review, we have determined that the content in question violates local laws in Turkey, as outlined in the legal request. In compliance with these legal provisions, we have restricted access to your account for users.
Not how federation works. Let’s take a lemmy post as an example. If a server is federated with another and a new post is made, all subscribed servers are notified and a copy of the item is sent in that notification. If the original is “taken down” the copies still exist on the other servers and any deletion event is in ALL of their modlogs. ANY instance can “undelete” or revert the removal, or just ignore the deletion request all together (or roll back the database, or any number of operations to revert a change). The items doesn’t just go away. The “origin” doesn’t have all that much power to force other listening servers to do anything.
This also extends to comments. I run my own small instance with me and a few friends. My server never had serious downtime because it’s just us. Our access to larger instances never “vanished” even as their sites went completely down. The local content is effectively cached regardless of the state of the origin server.
Good luck with that… There’s a lot of servers that can talk the same federation protocol. You’re not going to get them all. Forget all the normal means of bypassing blocks… you have so many fediverse and threadiverse servers to attach to in order to access largely similar content.