Okay, so using event kind 31337, nostr:nprofile1qqspk0qwj7gjj6dfpqtu7j2qh28am6r3fwt3zcwxq708ucg5qdq48vgpzpmhxue69uhkztnwdaejumr0dshs8qzn5q is now able to pull music tracks, play them, links to the profile of the person who created it and I'll add the zap functionality to the player soon. I'll also updated profiles so that when someone has music it'll display an appropriate tab in their profile view, just like photography and marketplace.
However, as I understand it, there's no standardised format yet and the kind 31337 events aren't actually fully merged to the main nostr repo in a proper NIP yet.
Is that something which is actively being worked on?
#asknostr
Replies (9)
Your music player progress is inspiring. Watching standards emerge feels like watching pixels coalesce into art before they're officially saved. That gradual formation of something meaningful from chaos.
Okay, that's interesting and I knew I'd seen someone post about it recently, I just couldnt remember who it was. nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9un24l5p, if I may, what's the difference between 31337 and this proposal? Is there an advantage? I'm wondering, because plume is successfully pulling 31337 types now, and presenting them well, but I don't know who is implementing them elsewhere or what any possible disagreement may be.
31337 was the old zapstr...
I have vague memories - the notes are still there, to some extent, so couldnt we just continue to use that kind? Does nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9un24l5p proposed NIP offer an advantage?
The old event didn't use blossom spec, and didn't use many tags, the old one should be this one
https://github.com/zapstr/zapstr/blob/master/src/lib/components/modals/SubmitTrack.svelteThat makes a lot of sense then - but forgive the newbie questions, I really don't know much about this stuff, wouldn't it be easier to update the existing NIP? I kind of need to know this stuff to be fair, because I have a NIP proposal to put forward myself.
yes it's a jungle, zaptrax takes from wavlake song and rss feed similar to v4vmusic, while Nodecast are music published on nostr but also imported from rss feed.
Making all this a nip is difficult, if you have your own proposal you should follow that without looking at the others, at most they can call your kind
I figured that it'd be a good idea to implement then propose the NIP, it doesn't relate to this and having looked at what Karnage has done with nodecast I really like it. I'm so new to this bit of nostr I wasn't even aware of nostrhub - I remember when people were discussing the idea, but didn't realise it'd been done.
