Oddbean new post about | logout
 I see a blank event. What nip, kind, or format are you sharing? 
 Same 
 your clients don't support NIP-31 then

look at how coracle, which also doesn't support torrents, renders this


https://image.nostr.build/d28758f77a894d171b0e81d5751cdb19e9a0e7cbd1cab2ad84917321cae09e37.png 
 add in NIP-89 support and now coracle can even open a client that can handle that unknown kind

https://video.nostr.build/6b9c22f94ccf9d8bbc7c7873bf7caa1e1636ff97ed3fa4fea7f2bab2d9e6eae6.mp4 
 Regarding the suggested options to open this event, did Jon provide those, or are they provided/recommended by you Pablo? 
 None of the above.
They client asks around for handlers (and might or might not store / know about your  favorite apps for it). 
afaik 
 > They client asks around for handlers

Who does the client ask? 
 Users in your network.  
 Only just realized this when rereading the nip. 
That's not ideal, mmmm. It incentivizes apps to publicly add their app tags to events the user is publishing, without them knowing.  
 Does it? The client tag just helps people know what client published the note, which is a different thing from knowing how best to read the note, which is what handlers are for. 
 So you'd only look at kind 31989's published by users you know?  
 That's an extra action for the users to take (which very few currently do). 
@Zapstore might be the kind of app where it feels more natural for users to publicly recommend handlers. 
 Coracle looks for recommendations from people you follow, and surfaces any handlers that are recommended. This is all automatic, and shows up at the bottom of a note in a drop down you can use to open any recommended handler. It is an extra step, but I'm not sure how you could get it shorter. 
 We have been talking about adding this tag only to follow list updates on a temporary basis to try to track down the lost lists problem. We don’t believe it is a Nos problem bc we’re only seeing partial lost lists. 

In general I don’t think it’s a good idea to add these tags w/o user permission but the Nostr ecosystem also needs to stop losing user follow lists. If all the clients added the tag temporarily we could likely pinpoint the issue and stop frustrating users and also wasting dev time trying to figure out if it’s our respective app. 
 Hehe yep, I get why you'd do that. 
Follow lists are a mess though, I like the proposal to instead start using individual events for it: nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqyghwumn8ghj7mn0wd68ytnvv9hxgtcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqyqjwewmrj4yz58jnu87p5fevr4f8lwulavks4jkmwegyrfjnherqq6v33px 
 Yeah @rabble has another proposal somewhere as well on this topic.  
 relays

see NIP-89 
 Does this sound right: 

 it can either be:

1) an application that publishes (i.e. self-ceritifies) that it can handle a specific event/kind type, and/or
2) a recommendation from a user 
 yes

and provides a URL (which could be a deep link) to handle the bech32, so when, e.g.. coracle, wants to open a specific event, it knows what URL to use to open that specific event on the app. 
 So this pointer / link could direct to:
1) web app, and/or
2) iOS app store, and/or
3) zap.store deeplink? 
 hardcoding is an anti-pattern in nostr 
 Freakin' beautiful to see this in the wild 
 really really great job executing that UX 
 Same here, on #Amethyst v.0.91.0. 
 oh weird -- I thought Amethyst supported NIP-31 cc nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyd8wumn8ghj7cmpvd5x2vfwwpexjmtpdshxuet59amrzqpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewq9wvd8h 
 We do, I can see it 
 Ok, well I can see it, but I get this: 
https://image.nostr.build/f371656fb703aaf1a52d37ca915bcba2dc57fe059f39b016165de1c2a8618f08.jpg
Do I need to download something else to open it? 
 Yes, you need a torrent client to download the file.  
 Does this mean no nip-89 support today in amethyst?

Do you plan to add? 
 We also support nip-89, but this one is not about that. It's a magnet:// link that the phone is trying to open and there is no torrent app to load it.  
 (for context for nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uq36amnwvaz7tmxv4jkguewdehhxarj9e3xzmny9ahx2amnw3eqqgzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxtspe07r9  ; this is where the convo started touching on NIP-31+89)

nostr:note1h2eerkm9gnllr8gk0en59z8tykupyu4a32xn4g5ymppw4ruguytqcc32j0

(see the parent event too) 
 Makes sense. Amethyst does see the torrent event. It just needs any torrent app installed to download it. 
 How to watch torrent movies in browser without revealing your IP
https://webtorrent.io/ 
 Ah, ok, so you do see what's inside the embedded event right from Amethyst

nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qg3waehxw309ucngvpwvcmh5tnfduhszymhwden5te0wp6hyurvv4cxzeewv4ej7qgnwaehxw309amk7apww468smewdahx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgqh2wxu9f38d8gfgsl33smuhc6cl26mh7vpzu6592nutlchrmthcsqe3xt6  can you share a screenshot of what my note embedding the torrent event looks like in damus?