nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg we’ve gotta get a #music section in your feeds list! 💜 would be great to work with nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg to get our 1808 notes streaming into your client 🔉
Let's do it! We win by working together.
Sure!
We just incorporated #music into our default list of feeds. I also added 1808 note rendering to our to-do list. Hope to be live with this in the next 2-3 weeks.
hey nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what do you think about adding support for nostr:npub1stemstrls4f5plqeqkeq43gtjhtycuqd9w25v5r5z5ygaq2n2sjsd6mul5 music notes in your app?
Sure thing. It would be nice if nostr:npub1stemstrls4f5plqeqkeq43gtjhtycuqd9w25v5r5z5ygaq2n2sjsd6mul5 sent a NIP PR to describe this kind 1808. Otherwise, I would just reverse engineer it.
good call out. in the meantime here’s the spec we use
Any chance you can add a hash to every download file? I would love to show that the file hasn't changed since the author posted.
It doesn't work for m3u8, but for the download it definitely does.
you thinking like a download_hash tag or something?
our download_url values actually already include a hash - that’s how we identify files, by their content hash. but ultimately we want the media api to be user configurable so I think this makes sense.
Or just an `x` tag with the hash as the NIP_94 does
Also, which relays do you have your content on? I can barely find it.
x sounds good to me.
1808s are only sent to relay.stemstr.app at this time. now that other clients are consuming them we need to start broadcasting further. there’s already a design for “share to my relays” - nostr:npub1xv6axulxcx6mce5mfvfzpsy89r4gee3zuknulm45cqqpmyw7680q5pxea6 keep me honest here
Do you have more info on the 1808 kind? We've been using our own as well for Wavman (32123) -- would be nice to unify on something
