Oscar Merry32d ago@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.
💬 2 replies
Thread context
Root: 68f2ae2e0d83…
Replying to: b16f636d2d26…
Replies (2)
ChadF and 33 others32d agoKeeping the GUIDs and deleting the items from wavlake is the plan if that's what people want to do. The site will import any music feed and allow users to edit the sections I support.
0000 sats
Strange Love31d agoOK 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 @78aa9a1b…bf8789ee
000