Oddbean new post about | logout
▲ ▼
elsat | 5 months ago (raw) | root | parent | reply | flag 
 Designers how might we help guide users whose nostr app just failed to find a note? 

https://github.com/nostrability/nostrability/issues/42

@rob @elidy @GBKS @Karnage @nielliesmons
▲ ▼
Karnage | 5 months ago (raw) | root | parent | reply | flag 
 “It appears this note had other plans and showing up wasn’t one of them”
▲ ▼
elsat | 5 months ago (raw) | root | parent | reply | flag 
 Yes, and besides the @fiatjaf type message, whats the next step?
▲ ▼
Karnage | 5 months ago (raw) | root | parent | reply | flag +1 
 >button< shut it all down, go bloom outside
▲ ▼
elsat | 5 months ago (raw) | root | parent | reply | flag 
 @saunter
▲ ▼
elidy | 5 months ago (raw) | root | parent | reply | flag 
 Error messages for non-compatible features would be nice too.
This note includes a feed, it opens empty on Damus, has just the nostr:addr… on Primal. 

nostr:note1n9z7fltdg5u638rfa5gc8k4p5yln4pndvs7wq20esenw3su8lyhq2h0rwc
▲ ▼
elidy | 5 months ago (raw) | root | parent | reply | flag +1 
 Nostur has a nice link back to Coracle. Great job @Fabian 
#networkeffects https://image.nostr.build/3810134fa5f053db82663e117bdd0a90dfa28c9b0f8624077aa34cf3cf7e1798.jpg
▲ ▼
elsat | 5 months ago (raw) | root | parent | reply | flag 
 Thanks @elidy 

I think this points to handling unknown event kinds, and recommended app handler NIPs, which damus has yet to implement. 

Nice work @Fabian !
▲ ▼
Fabian | 5 months ago (raw) | root | parent | reply | flag +2 
 Thanks @elidy and @elsat, this is indeed handling of unknown event kinds, I added this after @PABLOF7z suggested it in nostr:note16pgkeuxvkl3y8c7zgn9zvnn8w4xwqals9henwag5edez3gx8e9wqm33qep

More clients should implement this, its one of the few ways we leverage the current kind-1 network effect to grow the Other Stuff