So Zapstr now supports tracks published by Wavlake
A few caveats:
At the moment Wavlake zaps are broken except for zaps created with a special format from their app
Wavlake tracks are not published/signed by authors/publishers but by Wavlake (which makes sense for the time being) so zaps would only go to Wavlake if they did work, which is not what I have in mind for Zapstr -- probably something that will be fixed when there's more tooling
Playlists support is already kiiiinda working on Zapstr, it's a bit alpha but it works.
If you listen to a track through a playlist, that curator gets a split of the zaps, just like on zapworthy 😉
Also, Playlistlists can be nested, don't know if this might be valuable, but it's cool so why not. If a playlist contains another playlists, both curators of the playlists and the author being listened to are on the zap splits.
Oh, and one last thing, track events in zapstr have an `e` reference, I wrote those in the spec to allow an author to compose a track that references other tracks (looking at you stemstr.app rock (npub1yau…7h9m)); all those track components would be on the zap split as well
This is super alpha still!!
https://zapstr.live
and here's a playlist I quickly put together (no Lana del Rey on this one, I promise)
https://zapstr.live/a/naddr1qqg8v7pswe4x2vr60fk827fhxpaxxq3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqpax59hstd6#
PABLOF7z
npub1l2…tajft
2023-04-20 21:51:02
Author Public Key
npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajftPublished at
2023-04-20 21:51:02Event JSON
{
"id": "09d9b242016abe1dd810dabc15f3b945b8b2917059f8b7bae6979edea6721bd2",
"pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"created_at": 1682027462,
"kind": 1,
"tags": [
[
"p",
"27797bd4e5ee52db0a197668c92b9a3e7e237e1f9fa73a10c38d731c294cfc9a"
]
],
"content": "So Zapstr now supports tracks published by Wavlake\n\nA few caveats:\n\nAt the moment Wavlake zaps are broken except for zaps created with a special format from their app\n\nWavlake tracks are not published/signed by authors/publishers but by Wavlake (which makes sense for the time being) so zaps would only go to Wavlake if they did work, which is not what I have in mind for Zapstr -- probably something that will be fixed when there's more tooling\n\nPlaylists support is already kiiiinda working on Zapstr, it's a bit alpha but it works.\n\nIf you listen to a track through a playlist, that curator gets a split of the zaps, just like on zapworthy 😉\n\nAlso, Playlistlists can be nested, don't know if this might be valuable, but it's cool so why not. If a playlist contains another playlists, both curators of the playlists and the author being listened to are on the zap splits.\n\n\nOh, and one last thing, track events in zapstr have an `e` reference, I wrote those in the spec to allow an author to compose a track that references other tracks (looking at you stemstr.app nostr:npub1yauhh489aefdkzsewe5vj2u68elzxlsln7nn5yxr34e3c22vljdqkn7h9m); all those track components would be on the zap split as well\n\nThis is super alpha still!!\n\nhttps://zapstr.live\n\nand here's a playlist I quickly put together (no Lana del Rey on this one, I promise)\n\nhttps://zapstr.live/a/naddr1qqg8v7pswe4x2vr60fk827fhxpaxxq3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqpax59hstd6#",
"sig": "71286e57e51019962b22d7848a891e9d5a16b585605d1bcc576f8b28570bbfb7177fc2833762fe2ef4dbfd0bad0855996e891ce397aaa31abe5a2ffb6aea996c"
}