Nuh 🔻 on Nostr: Pubky does NOT use anything from that stack. It is fair misunderstanding for ...

Pubky does NOT use anything from that stack. It is fair misunderstanding for historical reasons, but approach pubky with fresh eyes and you will find it an extremely light, performant and straightforward stack.

We try so hard to be just as easy as using web api, just elevated to sovereignty without too many leaky abstractions.

quoting note1wxc…urdn

#Pubky is Slashtags rebranded. Rebranding is never a good sign. Its the same group as the Keet guys. Fundamentally they are struggling with traction, their protocol is obtuse and difficult to build on.

I get that having a bittorrent style DHT might be useful but the latency and discoverability issue is not gonna compete with nostr websockets. And there is a solid reason why SimpleX is using websockets and unidirectional pipelines for their chat servers. It just *Works* better. Not perfect p2p networks but for the purpose of social connectivity you gotta cut some edges off.

Love the idea, but also felt like I wasted enough time looking at Keet/Kademila/Hypercore rebranded twice to Pear. Great marketing but underlying adoption will not happen at Nostr Speed.

Nostr has its problems but its strength is that weekend warriors can contribute and for a scrappy distributed protocol this is what you want. Not $10 million dollar per VC app companies that refuse to hire american citizens and don't really welcome opensource part time contributors.

You are gonna need all the hands you can get to build something anti-big tech and by removing as many complexity barriers as possible you can achieve it with max leverage, less labor and less time to generate the network effect for survival.

#Nostr Will Survive. There are enough builders who don't need a PHD to make it work. That's the #1 key factor here.