Oddbean new post about | logout
 Wrong. DID creation is generating a key and storing it on their central registry. The DNS part is just an alias like NIP-05 and has no significance. 
 Mike  and Fiatjaf are correct on DID.  Matt’s perspective needs some nuance. One of DID’s challenges is decentralizing the resolution layer so maybe pegging to sidechain might do the trick but I don't fancy tokens so not something I have a clear assessment of. DID can exist independently as long as it is retrieved together, both metadata and verification keys. 

But all of you big boys need to zoom out. 

** Firstly, Bluesky and Twitter today have become a reflection of the extreme polarization that plagues America - and that is incredibly sad. Nostr must remain non-partisan, enabling clients with footprints of Bluesky and Twitter, among many others in it - and it's up to people to pick relays and peek into different worlds within Nostr. . 

Until and unless Bluesky opens up a client for the right wing folks and anyone else, it remains centralized. There is no need to talk about “what if”. 

** Secondly, user adoption is key. Only thing to understand about Bluesky is that they knew who their target early adopters were and went for it. That's all we need to learn from them. 

Who are Nostr’s early adopters? Tech folks (and it's not the 3 to 4 of you here but millions out there), bitcoin folks, people who need censorship resistance (investigative journalists, people from challenging places), people who are curious and those who just want to see all the client devs here succeed. 

** Thirdly, listen to the users. Brazilian users were all here first but did not know how to find people who matched their interest. Then they left. I always see devs pissing on users for voicing out their problems instead of trying to understand the concerns. 

Privacy is needed for some people - and while Nostr can’t provide it atm, don’t forget about it - open it up to any devs who want to focus on it. 

**Fourthly - let your imagination run wild with Nostr use cases. Web5 was an incredibly simple and powerful decentralized platform but nobody understood the application side or impact of it globally. Man it breaks my heart to see it go but if there is anything you want to take away from it - start focusing on applications and use cases

** And lastly, one cannot just keep building stuff and then whining when nobody shows up. Builders have to go out there and start hustling for early adopters (i.e. figure out the persona of the target audience and creatively reach out). And then listen to them. Improve your product. And keep repeating the process - again and again until you hit your mainstream users.  





 
 So, @fiatjaf, the founder of Nostr, now uses a client which randomly adds meaningless "e" tags of type "mention" when he replies to a thread, pointing to some previous item on the thread.

The standard thing for a client to do when displaying such posts would be that of showing the referenced note as a quoted note. I don't think this is the intention.

Why do client include tags that make no sense?

See this posts for instance:

nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqsyrugq33u5gmnzlm74k3ke974txvg2xkgfdsdz8gufxfkh4x37xvcg8764u
nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqs25gcgd4c8356tlhl2wgrefhh6s0hnzedmhcsjgz6xhp4h2mvc2ng0urenl
nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqsg3szzyxr2ckav425thg2ygelf0xhspwrcx5chwrc6yjw2wgkjfqcuu4ck2
nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqsqsk3wnha6cl0x2p6x70p09pyze483509el9rup6ytjaj26kydjvqv9zfrf 
 nostr:nprofile1qyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr9mhxue69uhkxmpwwp6hyurvv4ex2mrp0yhxxmmd9uq3kamnwvaz7tmxv4jkguewdehhxarj9e3xzmny9acxjcmnqqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgs4ep8kn  someone is complaining about your client here. 
 e stands for Electroencephalographically which flatlines after reading your note more than once. 
 > that post

You too see the quoted posts?

It seems like a "feature" of the client he is using.

nostr:nevent1qvzqqqqqqypzprhy9yxf3vst9xv38zej9arxagsvw4sg7452k570z9yjh7djapyuqqsx56hsq8axc3phutmxa0fztjhfw27wrr20y2zglzg2pqn5cnzqvlqsuaks9 
 nostr:nprofile1qyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr9mhxue69uhkxmpwwp6hyurvv4ex2mrp0yhxxmmd9uq3kamnwvaz7tmxv4jkguewdehhxarj9e3xzmny9acxjcmnqqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgs4ep8kn  someone is complaining about your client here. 
 in bluesky they use a "root" and "reply" pair for structuring thread trees, i think in nostr there is exactly this as the third parameter of `e` tags

this thing about mentions is stupid, who proposed that in the first place? at best, IMO the reply's parent (to which the "reply" marked `e` tag points should implicitly be notified and there should be no explicit need for the use of mention tags that are implicitly generated like this 
 It's there to allow notes to get all descendants, even if they're not roots. I'm not sure if anyone uses it though. 
 the use of mentions? coracle does it too

it's stupid, it should be a third type, so you have root, the OP, and then you have reply, the direct parent, and then maybe you can have ancestors or something, and they should be `e` tags and yeah then you can find all of them but mentioning doesn't do nothin 
 Hence kind 1111 
 awwwawwwwawwwwawwawwa https://i.giphy.com/tZ6zAdNZbWOhq.webp 
 Mine too, mine too 
 the use of mentions? coracle does it too

it's stupid, it should be a third type, so you have root, the OP, and then you have reply, the direct parent, and then maybe you can have ancestors or something, and they should be `e` tags and yeah then you can find all of them but mentioning doesn't do nothin 
 Hence kind 1111 
 awwwawwwwawwwwawwawwa https://i.giphy.com/tZ6zAdNZbWOhq.webp 
 Mine too, mine too 
 Hence kind 1111 
 awwwawwwwawwwwawwawwa https://i.giphy.com/tZ6zAdNZbWOhq.webp 
 Mine too, mine too