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 nostr:npub1yauhh489aefdkzsewe5vj2u68elzxlsln7nn5yxr34e3c22vljdqkn7h9m); 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#

Reply to this note

Please Login to reply.

Discussion

nostr:note10grhd9vmazxatqatu3upswssh7wqpzmx70ydeu9t4q2qk907tz7satukh4

probably should have tagged nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk on this one since it has more context πŸ˜…

I was more worried about distribution. Once people listen I m happy, until the zaps are featured

I need feedback to get more confident at music

Thanks

Working on some donations, as you have created value for me

This is amazing.

πŸ™ŒπŸ™ŒπŸ™ŒπŸ§‘

Nice to see some integration happening!

Re: zapping. We intentionally did not put a lightning address on the npub we're using to publish track events so that we wouldn't receive generic zaps. Our goal was to only enable zaps for specific events (tracks) so that they could go to the artists.

I think there is still a bit of ambiguity on how to handle zap requests for these NIP-33s... we're sorting through that now. But great to see some progress and hoping we can help clarify things for future dev

You do have the zap tag on the track event though, that’s what I’m looking for and the endpoint I’m trying to zap πŸ˜…

Why not have your users sign the tracks though? Even if they are derived as custodial keys, you could generate for them and at least they would have the option of later having those keys πŸ€”

Sounds like a great feature for wavman 2.0 πŸ˜‰