Even if the dev community around BlueSky/AT Protocol grows and there are lots of clients, I can’t get past the fact that it basically uses a slightly modified version of Fediverse instances.

That means the same problems will exist involving centralization of user base around a few overloaded instances, and the whole “instance administrator acts as a feudal lord” and “instance can’t afford to operate at this scale” issues.

Even if it’s easy to migrate between instances, the vast majority of casual users just aren’t going to think to do that.

Nostr’s model of not tying identity/content to a single instance is a critical advantage there.

Reply to this note

Please Login to reply.

Discussion

So Bluesky is literally a Mastodon clone?

Nostr is definitely the way.

Migrating between AT Protocol instances is definitely more streamlined than how it is for Mastodon, but that’s about it.

And technically a instance admin could prevent sharing the data needed for a merge?

*migration..

#DestroyAllKeyboards

There'd be no way to stop them, nothing the protocol can do to prevent it when it's based on the federated instances model since your profile is centralised.

Relays > instances

That's a shame. I was hoping it was more innovative than that.

Nostr is honestly the only "Twitter alternative" (it's obviously much more than that but you get me) that actually tries a new approach to improve on legacy social media rather than providing a way to self-host the same exact thing.