Oddbean new post about | logout
 One of the superpowers of nostr is interoperability and putting users in control of how they want to see and interact with the content. These examples are the antithesis of openness :Sadge: 

nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqqsvnckcwg2c9lytgu6m4n4dv078xh3xj3act46jwke9gfzv5clfr3cqjhd35 
 Nosta tries to respect NIP-89 and link out to clients that the user recommends. First, the user who created the content, second the reader, and then it falls back to some common/reliable clients. That only works if users post those recommendation/preference events. Maybe that needs to become easier. 
 On one hand, for my client, making URLs sexy again by making it short and readable is desirable, tho on the other hand I don't want to remove those addresses in case the client domain gets nuked and those shared across the net sexy links won't mean anything anymore / the user can't grab the address to put it on another client.

So sticking with unsexy addresses in favor of ease of interoperability/sharing + in case of client/project nuke. 
 I had to search for an article event, to be able to set the long-form entry. Would be nice, to just be able to go down an event-kind list and select the correct app for each type. Don't know if it has that feature.

https://image.nostr.build/66bb9f8820738d7c01a6ffd3aa8f96a9ccacd34f16a1b166ac846bcfa7858cfb.png 
 Definitely needs to be easier and better integrated across clients. 
 cc @brugeman  
 Well I thought you'd be setting it naturally for each event kind when you open it for the first time, there should be a 'remember' switch.  
 Definitely needs to be easier and better integrated across clients.