#pubky docs -- understanding home servers. https://docs.pubky.org/Explore/Pubky-Core/Homeservers

Hell threads are users attacking relay operators, who give up their time, to work for free. It's like going to a soup kitchen and throwing soup in the chef's face. Because they can. I understand tha aim is that the chefs, who work without pay, will improve their defenses. But a more likely outcome is that, when users throw soup in their face, they will just do other things with their free time.

One interesting thing about #pubky using a 12 word seed phrase instead of an nsec. It makes it obvious that your key also a wallet. #nostr keys are also bitcoin wallets, but I think most nostr users dont realize this immediately.

The strength of #pubky’s censorship resistance is that it doesn’t rely on DNS. With DNS, you can send a letter to a web server or relay and ask them to take something down — and history is full of examples where that’s exactly what happened. #Pubky works more like Bitcoin in that sense. To remove something from pubky, you’d basically need to take down the entire BitTorrent network. So far, it’s held its ground.

First impressions of #pubky vs #nostr mobile experience: pubkey is better than nostr desktop experience: nostr is better than pubky key management: nostr nsec is easier than 12 word seeds on boarding: pubky feels new and glitchy, but they are fixing things, nostr is more polished, glitches take longer to fix Still only day 1, but imho a great new addition to the open web. Cant wait to see how it evolves and for the public launch.

Testing #pubky app and it looks amazing so far. Both nostr and pubkey use the private key system (called nsec in nostr). So users can benefit from both apps. This will offer amazing new options, and full censorship resistance (ie 6 million nodes, vs 6 nodes) when it comes out of testing. Exciting possibilities for a truly-censorshp resistant new world!

running #pubkey -- wow!

In retrospect, the main value of did-nostr is its ability to unify Nostr and Bitcoin primitives within a single JSON object. This not only enables a 10x–100x architectural scaling potential for both systems, but also unlocks advanced use cases like on-chain zaps, trustless atomic swaps, decentralized contracts, consistent profiles and agentic Nostr. That said, I’m not entirely satisfied with the current DID spec—there are a couple of tweaks that would make a real difference. Still, it’s a significant improvement over what we have today, and those edge cases can be fixed later. 🔗

Nostr DID Method Specification

DID + Nostr + HTLCs = trustless swaps across Bitcoin and Lightning, with identity and coordination baked in. No middleman. Just keys, hashes, and open web standards.

DEV Community

Trustless Bitcoin Swaps with DID, Nostr, and HTLCs

🤔 The Problem Say Alice wants to send 100,000 sats to Bob. But: Alice only has on-chain...

We are pleased to announce the publication of the First Public Working Draft for the did:nostr method specification:

Nostr DID Method Specification

This specification defines a Decentralized Identifier (DID) method (did:nostr) that utilizes the cryptographic key pairs inherent to the Nostr protocol. It describes how a did:nostr identifier can be created, resolved to a DID Document. This initial draft represents the collaborative effort of several contributors. We would like to extend our sincere thanks to: - Maximillian George for valuable feedback and support throughout the initial stages. - Manu Sporny for providing an essential sanity check on the approach and structure. - The team at Block for engaging in insightful discussions that helped shape the work. We believe the specification is now at a stage where it is ready for broader review and contributions. We warmly welcome feedback, suggestions, issue reporting, and contributions from the CG and W3C DID community and anyone interested in integrating Nostr identities with did-identity standards. We look forward to engaging with the community to refine and advance this specification.

First Draft of did:nostr method from Melvin Carvalho on 2025-03-27 (public-nostr@w3.org from March 2025)

This is the way

"Always carefully review AI generated code". Thanks Martin. Not gonna happen. 🤣 View quoted note →

big if true

Possible compoents of a robust nostr reputation system, based on academic literature View quoted note →

#jumble is an awesome client. AFIAK it's the only client that lets you: 1. Log in with a nostr identity (hex private key) 2. And allows you to follow someone as a new user It gets the basics right. No other client does this.

Jumble

A user-friendly Nostr client for exploring relay feeds