This is just wrong. Another platform similar to tiktok(spark) is in beta with their own infrastructure outside of all Bluesky servers and they have to deal with their own moderation. They can choose to read in any Bluesky data they please and bluesky can do the same with theirs.
If Bluesky shuts down all servers tomorrow they still exist. The federation is simply adopting their Lexicon into your relay and appview.
If you want a microblogging platform specifically you can easily run your own infrastructure similar to running an instance, intake all BlueSky posts and if Bluesky shuts down your app will continue operating using BlueSkys lexicon, however you’ll have to manage your own moderation.
But what about the DIDs, the things used to actually identify accounts within the ATproto ecosystem:
But Bluesky has developed its own DID method, did:plc. Today, did:plc stands for “Public Ledger of Credentials”, however it originally stood for “Placeholder DIDs”, with the hope of replacing them with something else later. The way that did:plc works is that Bluesky hosts a web service from which one can register, retrieve, and rotate keys (and other associated DID document information). However, this ledger is centrally controlled by Bluesky.
It’s literally not possible to have a functional PDS without registering with a Bluesky server and they maintain indefinite control over the ledger. All your data is tied to this DID, it’s how the entire protocol is designed to identify stuff, how decentralised is your data if it’s dependent on Blusky (the company) assigning you an identity?
This is false, they support did:web which ties your identity to ownership of a DNS name (which is its own can of worms, but not controlled by bluesky like PLC).
Unless you mean that you still have to register your pds it to get indexed by the relay, so people can read your posts without querying your server directly (which is possible but discouraged). This is actually an advantage over mastodon/activitypub however, your personal pds will not crash if a post goes viral (unlike a personal mastodon instance).
I spent a couple hours trying to create an account on pds.flamingos-cant.xyz that uses a did:web following the instructions here and the account at the end ended up with a did:plc, so IDK how you create a PDS with a did:web but it’s clearly not something they put a lot of effort into supporting.
Because it’s not functional without BSky servers and BSky also retains control of moderation.
This is just wrong. Another platform similar to tiktok(spark) is in beta with their own infrastructure outside of all Bluesky servers and they have to deal with their own moderation. They can choose to read in any Bluesky data they please and bluesky can do the same with theirs.
If Bluesky shuts down all servers tomorrow they still exist. The federation is simply adopting their Lexicon into your relay and appview.
If you want a microblogging platform specifically you can easily run your own infrastructure similar to running an instance, intake all BlueSky posts and if Bluesky shuts down your app will continue operating using BlueSkys lexicon, however you’ll have to manage your own moderation.
Its not wrong. The COO of BSky herself told me this.
After reading the article i think you might be wrong with this one.
From what i got now is that there are 3 layers
First is storage which can be completly or is decentralised
Then backend/server/application layer which can be bsky or whatever ticktok alternative gets made which is not decentralised
and then user layer/view which depends on the application
What i want to say is that the relay can be exchanged through something else and then entirely including moderation and all
So pro atProto is:
And pro ActivityPub is:
pro ActivityPub? (unsure about the technical details)
But what about the DIDs, the things used to actually identify accounts within the ATproto ecosystem:
It’s literally not possible to have a functional PDS without registering with a Bluesky server and they maintain indefinite control over the ledger. All your data is tied to this DID, it’s how the entire protocol is designed to identify stuff, how decentralised is your data if it’s dependent on Blusky (the company) assigning you an identity?
This is false, they support did:web which ties your identity to ownership of a DNS name (which is its own can of worms, but not controlled by bluesky like PLC).
Unless you mean that you still have to register your pds it to get indexed by the relay, so people can read your posts without querying your server directly (which is possible but discouraged). This is actually an advantage over mastodon/activitypub however, your personal pds will not crash if a post goes viral (unlike a personal mastodon instance).
I spent a couple hours trying to create an account on pds.flamingos-cant.xyz that uses a
did:webfollowing the instructions here and the account at the end ended up with adid:plc, so IDK how you create a PDS with adid:webbut it’s clearly not something they put a lot of effort into supporting.i forgot the DIDs
Oh no
They support did:web too if you don’t like did:plc