#nostr is the EASIEST to use social network
If you want an account that can't be rugged and dm's that can't be decrypted by a third party
On Mastodon you need to
- install and run your own server [*]
On Bluesky you need to
- install and run your own server [**]
- create a did:web identity document and host it on a domain you control and use network commands to create and configure a Bluesky account to use it [***]
On Nostr you need to
- store your nsec like any other password and maybe install a browser extension
[*] and if you want to use other ActivityPub apps you may need to run more (different) servers
[**] and even then your server can be blocked from the network
[***] and your identity can still be rugged by whichever entity controls the TLD, although that's a small risk
I don't think it's appreciated enuf how much of a stunning 🎯 Nostr is in the set of tradeoffs that form protocol design
Benefits
* the identity sovereignty of P2P but without the performance and discoverability downsides
* the performance and discoverability of ATProto and ActivityPub but without the centralization of the former, the account portability issues of the latter, and the ruggability of both
* the accessibility of ActivityPub and the flexibility of ATProto
Costs
* users need to store their nsec securely, like a password 🙃
Good kit tips for playing electronic #drums in an apartment and not make ur neighbors mad #music #drumming
"the Nazi bar problem" combines so many generalisations and empty assertions it must be one of the world's silliest fallacies
Nostr has much room for improvement. The inspiration we might take from Bluesky are the labellers, feed generators, and the wide range of user-controlled moderation options
But if the goal is decentralization, Bluesky may take inspiration from Nostr
Bluesky has more severe problems than Nostr and they grow with every user
* it's completely and permanently centralized without major changes to the protocol (open access is not decentralization nor is it permissionless)
* open access microservice architecture but without decentralization (distribution within service layers) puts infra providers in the clusterfuck position of arbitrating between various competing interests and themselves, which will get interesting when things commercialise
* it's hard to resolve these issues when the protocol developer is also the app developer with 11 million Twitter refugees most of whom left because Elon wasn't censoring hard enough, and the complexity of the protocol is a friction against third party involvement
