I 100% appreciate your efforts and will continue to support however i can.
But the reality is nostr native music content is sparse. Whereas there is a massive library waiting and growing on RSS and its foss tech. Yes you can do it without, but... why?
Splits are a deal breaker as well imo. From a music professional pov, if it cant simply handle native auto splits, its a non-starter. They are essential.
It’s not native in RSS either - those splits are done on someone’s server. It’s not permissionless. We actually do have splits but currently with NWC
Im mostly tech agnostic but i very much understand whats happening under the hood. If it works for the intended audience or use case then thats where I go.
The RSS splits are absolutely permissionless if you're running your own node and hosting your own files.
If you're not, we'll its no different than having a custodial lightning wallet (it literally is that).
The RSS feed simply has a text file with a tag to a lightning or node address. If you self host your feed (on any server) as well, then everything you are doing is 100% permissionless.
If you're talking about the payment rails being used, thats lightning network. Keysend vs lnaddress vs whatever else is a bitcoin lightning problem, not an rss issue. RSS (or more accurately DeMu) uses both keysend and lnaddress but its a bit of a mixed bag of semi compatibility so admittedly not a perfect situation either.
How many people do you suppose will run their own lightning node …
Very few. But i have no problem with that. I dont believe most people in the world will be their own bank when hyperbitcoinization hits. I have no belief this happens in music either.
But I respond as such because you characterize RSS disengenuously similae to as if you said all lightning was custodial. Yes custodial flavors exist, but there are also 100% non custodial options too.
For the record, not every boost running through DeMu is fully decentralized and super based blah blah blah. I dont care. I believe custodial options are necessary too. What i care about, is the option to be fully 100% self sovereign exists in this ecosystem IF i want to put in the PoW to learn to do it. The tradeoffs you make are your choice. That's real freedom tech in action.
If you're talking about hosting non wavlake or fountain, then yes, agreed those splits are not permissionless if you're using their wallets or hosting your feed on their server.
Thats sorta how it works by definition... If you chose a permissioned option in your workflow then the whole workflow becomes permissioned.
But if you dont... and only chose permissionless sovereign options in your stack then... youd be permissionless.
Guyputsstickinbikewheel.meme
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.
You can do this with Nostr. Replaceable events make it possible.
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?
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.
