If you have the means, then why not?
Curious about the tradeoffs.
Discussion
Upkeep and maintenance I would assume, but that should be minimal. Upgrading the application when it needs it.
What platform do you use for PCR? I have several years experience using Anchor and thats it.
I work with nostr:nprofile1qqsraq473e8q6gmd932yjpf99hhvwzh97m3kmnlsvwhe08a2vwryktgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3wamnwvaz7tmjv4kxz7fwvehh2mn5v95kutnxd5lgn9h3 and RSS Blue.
It’s like 5 bucks a month. He’s an RSS wizard.
Our show was very informative with him.
As for the podcasting index we need to get that on Nostr as well.
Yeah I'd love to see someone fork podping to store on a relay instead of Hive.
I think it makes sense to have it on a distributed ledger like Hive. Anyone can host a copy of it and all of the copies are kept in sync with each other.
Having it on Nostr means you need to figure out which relays are hosting it and hoping they're up-to-date. You could do something like WebSub (which was used before Podping) and have the RSS feed indicate which relays it uses for events.
If it's on Hive there's only one copy, whatever the Hive witness say is the copy. As Hive continues to centralize around the few people interested in continuing to buy it (it's dPos after all) eventually you're down to nothing different than a single VPS hosting because it's already to a point where Blocktrades controls the chain for all intents and purposes. (tl:dr Hive isn't distributed now and is only getting worse)
If it was on a nostr relay that was hosted by Podcast Index then everyone would likely just sub to PI for their updates. If you did want to keep your own copy for some reason (maybe you want to backup PI and keep them sound) you could just sync those events to your own relay for safe keeping.
The ultimate goal of the Podcast Index is to decentralize and to not host anything. They don't want to be the single point of failure that they are right now. The index should instead be hosted by anyone that wants to host it.
They're looking at the Iroh library right now to do this, but maybe there's a Nostr way of doing this as well.
Hive was used because the guy who built is a huge Hive enthusiast, built it out, and proved its usefulness. And it has been proven to be quite useful. If someone built a better solution on nostr that proved to be as reliable, I don’t see any reason for it not to work on both nostr and Hive. The podping api could simply notify both networks of the updated podcasts. One thing about the PC2.0 community is they’re very pragmatic but busy, so the builders decide the direction of things much more than the idea makers.
Yeah in no way a knock on the work that Brian has done. I really hope it didn't come off that way especially after this week's boardroom. All the respect in the world for Brian.
Nah, no disrespect came across. More just noting that nostr may be a great alternative, and trying to encourage those that want to build a nostr based podping to do so. The more the merrier.
Rug pulling and control and curiosity. If you host with a host, you’re only able to put in your feed what they allow you too. With self hosting, you can put any tag in your feed you want as long as you’re curious enough to figure it out. If your host goes tits up or decides to censor your feed or add dynamic ads to offset host costs, you’re at their mercy. And some people just like the idea of being in control of the means of distribution of their content. But that extra freedom and control comes with the extra responsibility of maintaining your own feeds.
I get the sovereign side. But what’s the negative side?
As in how much development work is necessary. How do you evolve with the technology and etc.
If podcasting 3.0 come out what is required to adjust or conform.
I ask as a gentle pleb whose time is scarce and it’s something I am honestly interest in.
Down side is not as much help. If you break your feed or your server goes down, you have to troubleshoot.
No development work is necessary. Your feed is literally a text file you can edit in Notepad. You just have to be able to read the docs and format the text correctly in your feed so an app is able to read it and display your images, media, description, etc.
We call it 2.0, but that’s just marketing. Under the hood, it’s the same podcasting it’s been for 20 years, we’re just adding new features to the docs and building apps that can read those new features and display them properly.
Got it. Thanks
What a host provides is an easy interface for you to pick and choose the features you want, an automated feed builder (which you could do by hand in a text editor), a server, some promotion, and tech support. I think for most people, a host is a great way to go.
And I say that as the creator of Sovereign Feeds. SF gives you the easy interface, but you have to do everything else your self.