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.
That there are actually multiple relays. There’s no hard coded single relay, that would be ridiculous and idk why people keep repeating it
There is a hard coded relay in the official bluesky app, just like it has a hard coded moderation service. But both of those are changeable with third party appviews/clients
I was oversimplifying a bit such that it wouldn’t be overwhelming to a self-described uninformed person asking for an explanation.
Yes, there are multiple actual relays but they functionally constitute a single layer or class of components in a birds eye view of the whole system.
As far as I am aware, no one other than BlueSky runs the relays, or has the code to do so.
If I am wrong about that, I would appreciate a source indicating such.
Does anyone other than BlueSky actually run a relay?
Several people have self hosted relays. Afaik nothing that anyone has used in “production”, everyone just uses the default one. I expect that will change as people figure it out, and trust in bsky pbc drops with things like the current Turkish censorship incident
Example of self hosting https://bsky.app/profile/why.bsky.team/post/3lkwg2djrfk23
The code to run a relay is here https://github.com/bluesky-social/indigo
Your “example of self hosting” is not an example of self hosting the relay, just an appview which is still being fully dependent of other Bluesky services like the relay. It’s pretty unlikely that the relay would be at all practical to host on a RPi5. But even if it was the problem still remains that the network is set up in a way where self-hosting it only results in you creating your own separate bubble, not meaningfully participating in the official one.
I also doubt anyone has selfhosted relays long-term since right now there’s very little purpose to that and the resource requirements are massive as well as keep growing at a fast pace in terms of the disk space required.
The whole architecture is built around content addressing and allowing every account hosting server (PDS) talk to multiple relays and to allowing mirroring.
The whole point is to NOT create bubbles.
People already run their own PDS servers and participate with the official bluesky network, and can talk to users there, because their self hosted PDS syncs to the bluesky relay.
If you run your own relay and appview it STILL works, and you can talk without bubbles, if you still link your PDS to the bluesky relay to make yourself visible to their users, and if you set your appview / relay to retrieve content from the bluesky relay then you see content from bluesky users too.
Self hosted relays do exist, they’re just not open to the public (mostly used for archival / development currently)
PDS is not very significant, it’s just a tiny piece of the puzzle and doesn’t really prove anything about the architecture. See this for more on what I’m getting at: https://neuromatch.social/@jonny/113365406995624763
That post is very misguided.
First of all, he’s saying “you SHOULD make your PDS invisible to the bluesky servers because otherwise what’s the point”, but that’s exactly equivalent to saying “our community want it’s own Mastodon server - that means we MUST defederate Mastodon.social or what’s the point?”
That’s nonsense. Don’t enforce silos on people.
Also, which relays to support are not chosen by users, it’s chosen by the services the users choose. The PDS choose which relays to sync to, the appview does too, just like feed generators and moderation labelers does.
Also moderation labelers can be shared.
Hosting a PDS is very cheap, it’s just storage and bandwidth for the posts multiplied by the number of relays you directly sync to. With a few users on each that’s nothing. It’s in the range of free tier VPS hosting, RPi grade.
Deduplicating is probably the most trivial part. There’s already code for handling duplicate events in streams. But more practically speaking, there’s algorithms like set reconciliation which can make it significantly more bandwidth efficient to subscribe to multiple relays even when they have overlapping content.
Can you explain what do you think “backfill” means in the context of the linked post?
Sorry if that sounds disrespectful but we kinda need to have shared definitions for stuff
I have zero need to play games with you. Make your case if you have one.