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: neuromatch.social/@jonny/113365406995624763
Comment on Bluesky has started honoring takedown requests from Turkish government
Natanael@infosec.pub 3 days agoThe 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)
73ms@sopuli.xyz 3 days ago
Natanael@infosec.pub 3 days ago
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.
73ms@sopuli.xyz 3 days ago
I don’t think you got the point tbh. It isn’t about wanting to separate but about how dependent you are on Bluesky Corp. in every other scenario (and how hard it would be to deal with the situation if they decide to go rogue).
Natanael@infosec.pub 3 days ago
But that IS the point. The possibility of running independently PLUS the ability of bluesky users to migrate their account wholesale away from bluesky servers to 3rd party servers means you’re not dependent on them.
They’re literally designing for the principle of “the company is a future adversary” (see: Twitter, et al).
sp3ctr4l@lemmy.dbzer0.com 3 days ago
Blorgbob exists, and people use their own blorgbobs, but also people are not allowed to use blorgbobs, and they are only in archives or experimental development.
… Please tell me you understand you have just said completely self contradictory nonsense.
Leaving the actual truth or falsity of your claim aside… what you have just stated is a logically impossible paradox.
Natanael@infosec.pub 3 days ago
Choosing to not understand the architecture is your failure, not mine
sp3ctr4l@lemmy.dbzer0.com 3 days ago
Ok, noted, you are a fanatic who does not understand that the statement of yours I replied to literally is a logically impossible paradox.
Take a few deep breaths and … maybe try to reformulate your words.
Natanael@infosec.pub 3 days ago
Not knowing what a relay does and going on the attack over it makes you the fanatic.
It’s an archive node, which can (but doesn’t have to) forward ingested data