Found this interesting podcast with nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 and nostr:npub1kuy0wwf0tzzqvgfv8zpw0vaupkds3430jhapwrgfjyn7ecnhpe0qj9kdj8 on differences between nostr and Bluesky

So Bluesky and nostr developers have similar backgrounds and objectives but took different paths

Bluesky went for replicating Twitter services on a decentralized protocol built around existing protocols

This approach led to relative complexity which hinders the pace of decentralization

The protocol stores identities on servers, so users can login using emails and passwords

Now I kinda understand that the heavy lifting placed on nostr clients is because the key management is local

Bluesky had a lot of publicity which made open collaboration difficult

Whereas nostr took everyone by surprise

Having used nostr for only a few weeks I don't think I could go back to remotely stored / managed identities

Not your keys not your notes

It's a paradigm shift

https://www.curiousdk.com/p/bluesky-vs-nostr-with-rabble

Reply to this note

Please Login to reply.

Discussion

I actually think we should find a way to easily support custodial and non-custodial key and identity management.

just please tell him we will be "proprietary" if he gets here in october

AND THERE IS NO "RAIN CHECK OR SUBSTITUTIONS"!

Agreed

The thing I love about nostr is that the protocol is agnostic

Ppl can build beautiful walled gardens or beautiful wild free for alls and everything in between

Build everything and let ppl choose

That's freedom

Also some ppl will never grasp key management

That's reality