Sir Alecks Gates

@ericpp@podcastindex.social @StevenB@podcastindex.social @dave@podcastindex.social We think it's just the list of endpoints. It hasn't been updated in 2 years. So I'm going to update the list and make it configurable. Maybe have dave provide an endpoint of known good endpoints the user can opt-in to using.

@StevenB @merryoscar @ericpp @francosolerio The solution needs to be payment provided agnostic regardless. Bitcoin or not. Everything else in the feed is from the "host" -- the source of truth. Why would we change that now?

@ChrisLAS @merryoscar @dave @adam I am disappointed that alternative, self-hostable metadata solutions were not discussed.

@ericpp@podcastindex.social @StevenB@podcastindex.social I'm going to try to get the hive writer changes done tonight to help mitigate this for podping.cloud. Ultimately we are going to try to get a non-Hive solution in place. I have a decent plan but I want to hear what @dave@podcastindex.social thinks about it first. Unfortunately, the next few months are going to be very busy for me between work and moving states. And I'm just a volunteer with all this.

@ericpp@podcastindex.social @StevenB@podcastindex.social Primarily JSON-RPC, which is over HTTP.

@ChadF Nostr is literally a middleman solution. By design. Still waiting for someone to tell me why that's a good thing. (And it's not even a good one)

@ericpp @merryoscar @StevenB @francosolerio How dare you suggest an open standard with no middleman! Let's go further and add KYC to prove the sender's identity.

@ericpp@podcastindex.social @StevenB@podcastindex.social @dave@podcastindex.social And yeah, let that sink in. People take for granted how stable this whole thing has been. You're welcome.

@merryoscar @StevenB @ericpp @francosolerio @js Sorry what exactly is the problem with an API in the feed managed by the podcast host? I haven't seen a legitimate criticism.

@merryoscar @StevenB @ericpp @francosolerio @js I think I'm missing something. What does the wallet have to do with it? Why does it need to be aware of the metadata outside of a link to it? I'm replying during my day job (ask Adam/Dave how hectic it is) from a mentioned notification, so maybe I overlooked something obvious.

@merryoscar @StevenB @ericpp @francosolerio @js This doesn't make any sense. They could just host their own metadata.

@merryoscar @StevenB @ericpp @francosolerio @js What about other payment methods?

@merryoscar @StevenB @ericpp @francosolerio @js You just said we should continue to host metadata on wallets and now you're coming back with this, which appears to be an entirely different thing. This is going in circles. One seems to be a specification and the other is an implementation detail. I don't really care how you implement it. As long as the standard to host metadata is payment agnostic and determined by the podcast/host in the feed. A link to that metadata in the payment is fine.

@ChadF I am not running albyhub. I'm tempted to ask Adam to remove my keysend address from the pc20 feed and shut down my node altogether. I don't even care if I get boost metadata. Unfortunately, the bitcoiners now live in an epistemic bubble. It's not even an echo chamber anymore because everyone else left. A lot of people just don't want to bother. Those opinions are being left out of these discussions -- and the insidiousness of that is it's hurting podcasting as a divisive force.

@StevenB@podcastindex.social How are you submitting to Hive?

@ericpp@podcastindex.social @StevenB@podcastindex.social I mean, you can use spurlock's websocket if you want. I try to promote more decentralization.