hodlbod

> Ignoring moderators This isn't about moderators, but about authors. Most publications don't allow just anyone to submit an article. > Sure. As long as the "publication" organization is fine...

Maybe I am misunderstanding the use case then, if it's peer-to-peer collaboration that's a whole different thing, which I don't think any of these approaches probably solves.

Sure, the goal of this nip is just to have a standard that everyone likes for publishing audio tracks. I think this probably requires that it be 1. replaceable, and...

> Wavlake zaps were implemented almost a year ago when the [NIP-57 spec had this](https://github.com/nostr-protocol/nips/blob/8b39976e78f90fe766ad7149e250777cddacbb5e/57.md#protocol-flow) Very interesting, I didn't remember that. Maybe we should even bring this back, it seems...

@pablof7z it seems 31337 is used both in NIP 89 and for zapstr.live. Any preference for how to handle that collision? I think probably creating a new kind for this...

> NIP 89 doesn't use it, it just mentions it as an example 😅 Oh hey, I didn't read closely enough, that's perfect. Back to using 31337. The one area...

> would it be helpful to add the a tag to the example so it's explicit what needs to be included? Just so people know what it looks like to...

Go for it! I'm hoping to hit this in the next week or two. If you want to use Ainsley's music as a pilot I think that would be awesome.

Mostly repeating what @pablof7z said: - It looks like the `a` tag is pointing to the same event, which seems nonsensical to me. - I'd like to see at least...

> The a tag follows the [spec](https://github.com/nostr-protocol/nips/blob/master/01.md#tags) for parameterized replaceable events. From what I can tell it's accurate but maybe I'm misinterpreting the spec `a` tags are intended to point...