What’s the point of this spec? I’m so confused
Created a PR on Damus to start extending support for NIP-27 (#[0], arthurfrance, #[1])
It adds the necessary parsing code to detect nostr: bech32 entities and represent them as regular mentions. nostr:naddr and nostr:nrelay get parsed but don’t have any special UI as of yet.
With this functionality, DMs are one step away from not leaking mentions any longer. Instead of converting mentions to #[idx] they could be converted to nostr:npub… and not added to the tags field.
Any feedback is welcomed!
https://github.com/damus-io/damus/pull/837
#[2] 
Discussion
Haha, one reason is to make it optional when you mention someone if you want it to notify the person or not. Clients can decide whether they place mentions into the tags field or if they leave them inline. And particularly for DMs to avoid the mentions being leaked to the public they should stay inline
ah got it, although not sure what the ui for that would be 🤔
Yeah I think clients should pick a default for now and worry about that later. But at the very least it will improve the privacy of DMs
In your DM code you will now be able to have a different render_blocks() function that makes the mentions inline and doesn’t put them into the tags field without it looking any different to the user
Yeah would be definitely handy for DMs, I was going to do an ad-hoc fix but this seems better
It's better than the #[x] stuff. This is more flexible as you can decide to add tags or not, or embed relays or not in the bech32, and for raw viewing of an event (or very nascent clients) it's easier as they can just display the raw NIP-19 code and that kinda works. Also it's simpler for clients to format/render notes that have raw npubs pasted that were not caught by autocompleters and turned into tags as the text was typed.