I see you used nostr:npub10z4f5xu9g4rjjvqx4zhhn9hnrqddpczlchq4w3v0wn6430u838hqdlx7l3 also which is cool.
You update the xml file and it updates everywhere. One and done with the adding it to podcastindex.
I see this is on satellite.earth which might cause issue when you update the feed but we won't know until you do. We've not really explored this space yet.
Ok so I would simply open MSP2.0 add the name and info of another song, create the updated XML, and simply input the new xml into the index and it will just add the song to the album a few hours later? What potential issues would satellite.earth cause?? It seemed like an easy and cheap way to host and I can simply pay with sats to store my files.
I gotta think about this a bit but you made the xml file in MSP 2.0 and then added that to satellite.earth?
This issue with satellite.earth is that it hashes the file so when you upload the updated xml file there it with be a different file name.
This is what you added to PI right?
https://cdn.satellite.earth/5adeca59ff9337d8e840eeb883c5628b06386d818e0a0d6e00bdb6ccd3208696.xml
Normally you just update the xml and upload the new version to the server and since it's the same file name PI just looks in the same spot and sees that you made changes.
When you upload the updated xml with more tracks to satellite.earth I think that file name will change so PI will still be looking at the old file.
This isn't a satellite.earth issues it's a Nostr hosting issue in general.
It's super complicated but the file is signed with your Nostr keys when you upload and that's why the file name has a bunch of random numbers in it. You change the file in anyway and it changes those numbers when you sign it because it's a different file even though it's just a changed version to the original.
RSS feeds need to have static urls to point to and the info changing each time you update the file is an issue. One we can solve but we need to know what needs fixed and you doing this helps a lot actually.
You have a track up and it's working which is great so the hard part is over and we just need to see what happens when you add a new song and go from there.
MSP 2.0 should save the info locally but if not just click import and use the xml you saved from before I hope ð. MSP 2.0 isn't designed to save anything long term so don't rely on it for that. It's a creation and editing tool and also days old. ðĪŠ
Yes thats the xml file. Ok i understand the hashing thing. SO what You are saying is I would essentially have to delete the old feed and take down the song, create a new rss feed with more songs and it would be updated? But I would have to take down and replace each time i want to update??
You should not have to take down or delete anything. You need a static URL so you can simply add to/edit the RSS feed. A new song is just a new item tag. Once the location has been established, you update that file and everything updates / all the apps grab it.
Is there a way to add a new item tag to the XML without changing the hash of the file on the blossom server?
Hm, I don't know the answer for certain so let's see if nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99uq35amnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6tc4uevew is around to answer...
No, unfortunately it's not that convenient since the hash is of the hole file. Also it would defeat the point of using the hash if something in the file could change
Thanks for the confirmation. I'm working on rebuilding nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9's MSP with nostr:npub10z4f5xu9g4rjjvqx4zhhn9hnrqddpczlchq4w3v0wn6430u838hqdlx7l3 and nostr:npub1l5hwyh7saazz4gdhgp9fx4939e25asx74kq6dj9ahrx69lcfxulsudhdrf is my guinea pig for testing these Nostr hosting solutions.
MSP 2.0 will host feeds for users so the issue is solved at least for me.
WOuld the easy fix be that I host the audio and art and you can host the XML file for me like you mentioned in your MSP2.0 tutorial?? That way when I want to add songs to the album the XML isnt a hashed file??
Yes, that's the current work around I have setup. I do have a blossom uploader option also that you should be able to enter satellite.earth there and it adds the new feed there and I just give you a static url that points to the one on satellite.earth.
I've only tested that with my own blossom server but it seems to work.
You then would then have to upload what's in PI but I'm not sure how to do that without breaking stuff but breaking stuff is part of the process.
nostr:nprofile1qqs2p9fwkqd9vm4rqac0zvh87pqgt2k3l9csgks2jhc7wrxj89vwcmgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytc5xext6 nostr:nprofile1qqsyymc3xj8lpcld5t2mjpheed7ewsc8t2u9aweuzh2hlwqtfcj7c0spr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tc6jsvp7 nostr:nprofile1qqsr5qnsn6medetj3vexljqqvy99gfdrgsp7hs9f52kdvrryz6gwkrspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t083w42h nostr:nprofile1qqszm7l9ew24usqckahx2s4rhpuzz3xatatnty2dhxfpl5jv8v73qmgpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzamhxue69uhhyetvv9ujuum5dahx2u3wvdhk6tc6kjzv3 how do you update the url where the feed is hosted without breaking what's currently in the index?
Oh so you also have a sort of adaptor that can provide like a go between URL that can remain unchanged, but lead to updated files hosted on satellite.earth? Would that be easier than MSP hosting the XML?
MSP hosted I'm hosting the whole xml file for you and you host the media.
Blossom the xml file is on your blossom server which is satellite.earth in this case and MSP is just pointing to the current xml file on your blossom server.
Both ways you're still using S.E for the media and I'm just helping out. The only difference is where the xml file is located. Either my server or your S.E account.
So either way I would have to go through you to add songs to the album?
Yes if you want a place to host the feed.
OK. So I guess I will be hosting some xmls with MSP
or your own server but you talked with nostr:nprofile1qqsr5qnsn6medetj3vexljqqvy99gfdrgsp7hs9f52kdvrryz6gwkrspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t083w42h enough I'm sure all that is hashed out already.
I do not have my own server. Is a Bitcoin node essentially a server? If I was running a Bitcoin node would I be able to host xmls on that? I do not have one but was curious.
Yeah it is but that won't work here but we've talked about it before. Kind of a one stop shop. Get a mini pc, put some software on it and have everything you need. If you hear "Helipad" mentioned that's basically software running on a Bitcoin node to trigger sounds effects and receive the Boostagrams from listeners so you never know what's possible.
You could host the xml on your bands website if you have one also but MSP 2.0 is designed to do it for artists as they learn how all this works.
When I talked to boo-bury he said I couldn't host the audio from a wix site and make an XML. So I assume I wouldn't be able to host the XML there but I could try.
I save and download the updated feed (even in instances when new songs are added) over top of the file on my desktop. From there, I locate the file on the dreamhost website and upload/replace the old file. The xml filename must match exactly as the prior name. From there podping and you'd be set.
