Replying to Avatar BITwise 🐳 >>= RIGHTish

I think im unclear when I say native auto splits. My bad on that. I shouldn't have used native.

What i mean is: the ability to input my own splits, have the ability to update them permissionlessly at any time, and for them to be broadcast and globally updated automatically everywhere with reasonable assurance that every client playing my audio has the updated splits.
Avatar
HoloKat 0mo ago

You can do this with Nostr. Replaceable events make it possible.

Reply to this note

Please Login to reply.

Discussion

Avatar
Haikustr 0mo ago

You can do this with

Nostr Replaceable events

make it possible

This haiku was found in the wild by npub1halkcws4lz49fdcznckk9unhsfh8yd6n6n7cnl68alkej7qptmxqjk60zq

Read the origin of this art: https://njump.me/be57313f00689b11c3db1e539426ee0f47dd9eefb7f74ccbd0da7ec0d52b9761

Avatar
BITwise 🐳 >>= RIGHTish 0mo ago

What's the implementation look like?

Playing contrarian, id be concerned if someone is not connected to one of my relays, they might not get the update (like how follower count is not accurate).

Are replaceable events backwards compatible? Both the relay and client would have to support them to see anything right?

Avatar
HoloKat 0mo ago

Nostr by its nature is probabilistic. You don’t really know if the latest version of a replaceable event is truly the latest but there may be ways to reduce the likelihood of on old / stale event. I’d be talking out of my ass if I pretended to know how to do this well but I do believe there are ways. The most important is multi-relay publishing at the time of event signing so you query multiple relays at client level and reconcile them to select the latest event. You can probably also add relay hints to events themselves - but I’ve never done this.