Podcasting Chat Community

@silas I don't know if this is still the case, but I think Fountain was partnered with Zebedee (now ZBD) for supporting Bitcoin Lightning wallet integrations.

Bitcoin for everyone on ZBD!

Play free games, take surveys, and more to earn real Bitcoin rewards.

(zbd.gg)

I have really wanted to avoid the responsibility of maintaining people's wallets directly...I'm hoping we have options similar to "Checkout with PayPal" where we can facilitate V4V transactions without directly having any stewardship over people's money.

@silas we've been using @js's livewire podping listener for a few years now, and it seems to be quite reliable for detecting podpings.

Re: "reparse the feed every minute", I would suggest the responsibility is on the podcaster (usually their RSS feed hosting company) to make sure their RSS update process is aligned with the Podping process.

We've run into issues with requesting cached feeds in the past, but that is something that should also be handled by the RSS host.

podverse/packages/mq/src/functions/mq/rss/runLiveItemListener.ts at develop · podverse/podverse

Podverse monorepo for all infrastructure, modules, applications, and deployments - podverse/packages/mq/src/functions/mq/rss/runLiveItemListener.ts at develop · podverse/podverse

GitHub (github.com)

@silas afaik podpings are merely “rss feed updated” signals. The rss feed should (but isn’t guaranteed to) be updated before a Podping is broadcast. The RSS feed is still the source of truth and should be parsed to determine current live start or live ended status.

@ericpp @dave @alecksgates I didn’t know about the metaboost tag. Seems like exactly what we’d need to support LNURL without losing boost message data.

Boost message data should probably be pulled out of the keysend implementations anyway since it’s so restrictive.

Podverse might be open to hosting a metaboost API as well. I don’t know how we’d manage the spam and abuse problems though…Alecks if you have ideas and would ever be up to talking about them I’d appreciate it.

@silas I’d be open to writing V4V documentation for devs but…I don’t have the answers to it myself yet.

@silas we’re about to start implementing V4V in Podverse Nextgen, but I’m still not sure how we facilitate the transactions. In Podverse Legacy we rely on Alby’s API endpoints. I intend to continue supporting Alby as an option, but it would be nice if we have more options. Are the other HTTP API services we can use? Are there non-HTTP solutions we can use?

I’m having a hard time figuring out how to do this. There’s no documentation geared towards devs for V4V implementations that I know of.

@beshr “Gatekeeping in Open Source: The Scott Shambaugh Story.”

The title had me dead

At least the bot presented itself as a bot. Ars Technica offloading all editorial responsibilities to LLM seems more reprehensible and dangerous.

Strange future we are living in.