Oddbean new post about | logout
 Can we also do it the other way around, with embedding "nostr:npubbunchofnumbers" and "nostr:neventbunchofnumbers" and etc. in issues?

Then, if I see someone mentioning a bug in a Nostr note, I could just grab the id and paste it into an issue and @ them in it. Instant feedback and then I don't lose track of who reported the bug. 
 Good idea 
 I started to working on extracting bech32 nostr references from the content of events but it turns out that NDK does it automatically when signing events. pretty helpful. thanks @verbiricha 
 I actually meant to tag @PABLOF7z as he added the automatic tagging in NDK.
I'm not sad that I tagged @verbiricha as he doesn't get enough credit for all he does in the space. 
 Thanks for the shoutout! #NDK is awesome, even hashtags are added to the post when using them in the content. 
 users are actually already tagged if the full bech32 is used
nostr:nevent1qqszhs8y93mnj76va0wascdm0dt550e7683pqqdq5zh4fkw855w86wgpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6l6xc6n
but there should be away to select from a list when the @ symbol is typed. 
 Problem is actually that it isn't displayed in your client as an @, not that it doesn't work as a mention. 
 Tagging from a list is nice, but not really as high-priority as other features, since we can just use other clients for that. 
 feedback like this is so important. evaluating what the most important next thing to work on is really hard at the best of times. especially so when having to 'wear every hat' in the software development process. 
 Yeah, I'm used to prioritizing a backlog.

Also, I won't mind, if you reject an idea as being inefficient or out of scope, or whatnot. I just like getting a prompt response: yes, no, maybe later. 
 Do you mean that an inline reference to a users like @Laeserin should render with their name instead of long npub displayed as text? 
 Yes. 
 Ask and you shall receive. Implemented in commit 44fb751eca41de2859562a724ac9a567080a75d9  
 There is more of a dopamine hit when there is one issue per feature. There is like 6 other things to implement before this issue can be closed. 
 You could always create smaller issues and post their hyperlinks into a note under this one, and then close this one.

Cleaner issue management. 
 Yes. 
 Ask and you shall receive. Implemented in commit 44fb751eca41de2859562a724ac9a567080a75d9  
 There is more of a dopamine hit when there is one issue per feature. There is like 6 other things to implement before this issue can be closed. 
 You could always create smaller issues and post their hyperlinks into a note under this one, and then close this one.

Cleaner issue management. 
 feedback like this is so important. evaluating what the most important next thing to work on is really hard at the best of times. especially so when having to 'wear every hat' in the software development process. 
 Yeah, I'm used to prioritizing a backlog.

Also, I won't mind, if you reject an idea as being inefficient or out of scope, or whatnot. I just like getting a prompt response: yes, no, maybe later.