Oddbean

Because Nostr is still very early and now's the time to enhance, build, or change it. ActivityPub is from 2016 and much more set in the ways on how to accomplish tasks and features - it's more mature. Nostr is more malleable.

It is nor up to us. We want the best censorship resistance available, and that requires a large overlay network, in this case the best is Mainline DHT, but ANY overlay network you can think of uses ed25519 keys, not secp256k1. So right out of the gate, we can't use npubs to represent identities, at best we can use a sub key to use Nostr relays as free infrastructure, but without real interop because Nostr clients don't know that these sub keys are all part of one identity delegated to by an ed25519. would that have been "enhancing Nostr"? if so, feel free to do just that right now. If that is what "other folks on Nostr bringing DHT" means, perfect. Let everyonr have a sovereign ed25519 key. And call it Nost if that makes you happier.

Sames. We have too many 🤣 nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qyg8wumn8ghj7mn0wd68ytnddakj7xph5zr perhaps remembers. He used to share it I believe.

You analyzed it correctly. Makes every npub a censorship-resistant dns so you can own a piece of the internet. Where nostr is 6 nodes #pubky is 6 million. The two systems can work together but pubky is working now. Nostr could integrate it. It might take a day, it might take a year, but it wont take 10 years. Users get 10x or 100x more options. So some are adopting early.

#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.

Because it isnt, really. Slashtags was an attempt to build our vision using hypercore, we scrapped that design and made Pubky instead. It took us 1 year to make Pubky. This is a the product of the hard work of a dedicated team trying to help users. If you want to learn about new things, we have lots of info about what makes Pubky different, but we also understand people feel loyal to their social media protocols, and might prefer to discredit us.

I guarantee, you can understand Pubky and build a good application on top of it in a weekend, and get out of it underwhelmed too because it felt just like building a local web app with FetchAPI. But in reality you would have built a censorship resistant application with users having perfect credible exit by controlling who hosts their data and their URLs working transparently even if they migrated to other hosts.

I do not think pubky is a nostr competitor... the technologies barely overlap imo ..... at the same time, both can benefit from each other... or at least that is how I understood pubky.. Also pkdns is such a cool thing https://github.com/pubky/pkdns

I have no idea what #pubky is, and at this point, I'm too afraid to ask. nostr:nevent1qqs8kfa37ldpxwu9nzf5xk7yrvdex90aeuy9hfrz80t4f8p3sj88dhgprfmhxue69uhkummnw3ezucm9wf3kzarjdamxztndv5hsygplwuxkt5a8vj5utj6s8tsj8e3wcavc45p4mqmw92qs7wrh5azmyspsgqqqqqqstcs05g

The most important thing is that it doesn't matter, permissionless protocols don't care about personal opinions, if the thing is good, it will find its way. Keep buidling 💪 nostr:nevent1qqs8kfa37ldpxwu9nzf5xk7yrvdex90aeuy9hfrz80t4f8p3sj88dhgpz9mhxue69uhkummnw3ezuamfdejj7q3q8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqxpqqqqqqzsh9yse

I thought we are all here because we want to maximize freedom, not because we want to belong to a cult. We should use all of the tools available to make a better world, and it doesnt really matter who or what created them as long as they provide solutions towards a better future. We are building for freedom. its hard enough as it is to fight the forces of centralization and compliance without fighting between ourselves and creating new divides. nostr:note10vnmra76zvactxyngddugxcmjv2lmncgtwjxyw7h2jwrrpywwmwsqfcdcc

problem with Keet is the front is still not Open Source after 3 years. I am grinding on this hard because i was an early beta tester. DHTs can also be a central point of failure but can't even see the deets of how Keet is implemented on the front, unless you want decompile all of that javascript. I don't know what they are hiding and why so long.

Yes and Holepunch team didn't invent or maintain Mainline...they have an entire whole other DHT. And we only use Mainline to map keys to web servers, then you proceed like you do after you find the IP address from DNS. No p2p swarming, no Hypercores or even Torrent. Just http, simpler even than websocket and nostr events. If you know Fetch API you know pubky