Erik on Nostr: rossbates two things I'm thinking for the kind 2002 event that would potentially make ...
rossbates (npub1u65…332p) two things I'm thinking for the kind 2002 event that would potentially make it more interoperable / usable.
1) The "i" tag can just be any general information about how to find the song. The MBID schema is great if a user has it, but I don't think it needs to be limited to that. Having `spotify:track:{spotifyId}` or `tidal:track:{tidalId}` would allow clients to more easily link to a spot where the song can be played.
2) I think adding a `source` would be fun, then a client like scrobble.nostr-music.cc can show which player the the scrobble event came from. Cmus, spotify, last.fm, etc...
This would also tie in nicely to building out a more structure graph of how to find music on the web. Something can ingest this data piece together the spotify link, tidal link, mbid link, etc... and turn that into a Song event.
I almost have a little app done that will handle publishing these events directly from your spotify plays, rather than having to go through last.fm, and I think that will open up this event kind to many more users.
Published at
2024-09-20 16:28:42Event JSON
{
"id": "322240cfeecfe310be696cee373a6a1975c6baa84cca2e8f1a7cd4708db43224",
"pubkey": "1f7178d5579ae2eebc09059e1c91f93414d1e0c9c3fa281f3c1ba79c959cd559",
"created_at": 1726849722,
"kind": 1,
"tags": [
[
"p",
"e6a9a4f853e4b1d426eb44d0c5db09fdc415ce513e664118f46f5ffbea304cbc"
]
],
"content": "nostr:npub1u656f7znujcagfhtgngvtkcflhzptnj38enyzx85da0lh63sfj7qva332p two things I'm thinking for the kind 2002 event that would potentially make it more interoperable / usable.\n\n1) The \"i\" tag can just be any general information about how to find the song. The MBID schema is great if a user has it, but I don't think it needs to be limited to that. Having `spotify:track:{spotifyId}` or `tidal:track:{tidalId}` would allow clients to more easily link to a spot where the song can be played. \n\n2) I think adding a `source` would be fun, then a client like scrobble.nostr-music.cc can show which player the the scrobble event came from. Cmus, spotify, last.fm, etc...\n\nThis would also tie in nicely to building out a more structure graph of how to find music on the web. Something can ingest this data piece together the spotify link, tidal link, mbid link, etc... and turn that into a Song event.\n\nI almost have a little app done that will handle publishing these events directly from your spotify plays, rather than having to go through last.fm, and I think that will open up this event kind to many more users.",
"sig": "90456c8e860db94b29ef5f41aeda33de3e2df59665a4773203d4471d3f3c7556597263be222f097cdff2e800aaf1be606e0a07cf00b1e8a4397b7d864271c061"
}