I can't boost your track - it says there are no splits?

How odd. It seems random somehow. But... thanks for trying and sharing the experience. I appreciate it 🙏 ♪

Good to know that it's probably not Wavlake and hopefully limited to @6538925e…571e55c3 ...even though that's problematic enough.

Exactly. It was empty at the time I mentioned it. But then I checked again when you brought it up 7 hours ago, and then it was showing. So yeah, clearly some kind of lag was playing tricks on something 😅 You’re of course 100% right about promoting fully self-hosted #DeMu. I totally agree it’s better to be fully responsible for it yourself. But at the time, when I was completely new to all of this, Wavlake felt like a nice way to dip my toes into RSS while still managing everything else with my old routines. Now I feel a bit stuck with Wavlake, since I apparently can’t combine two separate RSS feeds for one artist. I have realized that I need to take everything down from Wavlake to transition fully to DeMu. My original transition plan was to start doing my own feed that would co-exist with Wavlake, and then take down Wavlake eventually, just like you would do in the legacy world where you could have part of the catalog on DistroKid and another part with Tunecore, while Spotify users would never know since everything was nicely presented under one artist name. But now I understand that this cannot be done with RSS. This does not change anything about me making the transition, but there are a few nice features in Wavlake that I would like to figure out how to replicate myself first. For example, it is really nice to have some basic stats on releases, just to see if anyone is actually checking out the music, even if they are not zapping it. I would also like a clean way to include a proper player preview in my Nostr posts when I link to music. I have been using Wavlake for that so far. But I just realized that I can just share a Fountain or V4Vmusic link instead. Pretty obvious, but I guess I had too much on my mind back then, haha. Also, when I tried that before, I did not get a player preview in Primal, but Wavlake worked fine, so I was a bit confused about the whole thing. However, I just tested again in Yakihonne and non-Wavlake links works fine there, getting a nice player in the preview, so I guess that was just a Primal thing combined with a confused rock guitarist brain 🎸 Anyway, I am rambling now 😉 Yes, I will make the transition within the next couple of months, just trying not to stress it while juggling everything else ♪♫ By the way, how are you doing it? Have you found a nice, simple setup you would recommend? My first thought is just to use my existing website hosting for the feed and audio files, but I have not figured out how to make nice stats and things like that yet.

Agree that a thriving music ecosystem has a bright future here on nostr. Good on you, sir

🤘🧡🎶 well done!!! And ok, it’s already March, but still—happy 2026! Let's make it full of unchained music energy

Yeah is writing today. Thanks.

@ChadF and 33 others since Wavlake don't support feed redirects - the best thing for Artists if they want to switch to self-hosting is to delete their content from Wavlake after they've setup new feeds on Music Side Project. However if not done correctly this creates another issue of duplicate artist profiles in Fountain and other apps. Maybe Music Side Project could have an "Import from Existing Feed" function that maintains the publisher, album, and track guids? The most important thing is that the guids stay the same - if this is the case we can resolve duplicates on our side easily without losing any of the nostr data.

Interesting discussion. I'm learning a lot. Btw... I just had a look at my SK page and can see that it misses 6 releases. Is that because Wavlake has changed something, or a SK thing? That being said, SK looks great ♪♫ https://stablekraft.app/publisher/henrik-flyman

OK so if originally I used wavlake to distribute, which created my original artist publisher GUID hence my artist page in fountain and other RSS apps, would the play be to simply add that publisher guid generated by wavlake into any self hosted XML? And then the release should appear under our artist page? Or would the better play be simply to use the publisher feed feature in MSP to aggregate the releases as they are without changing the XMLs? And is deleting from wavlake necessary for both of these options to not break anything? Asking because it looks like our latest RSS release has not been placed into our original artist page. @Oscar Merry @Music Side Project 2.0