Mastodawn

1d ago

Sir TJ The Wrathful 1d ago

@algrid @ChadF @adam @dave @podcastguru sorry if these are dumb questions 😅 but I'm trying to understand the vision. how would boostagrams work? How would a podcaster switch to and get LNaddress? Guessing you'd need a whole new system for a helipad type thing too?

I also tested episode 1 of No Solutions that has a Primal wallet in the splits and that split worked.

Just saw that the PodcastGuru Beta has Strike integration now.

Connected with no problem but only 3 splits (strike) were paid to PC 2.0.

Also the Strike logo is hard to see in the setting (3rd pic) in dark mode.

5d ago

Anyone else having issues Boosting from the Podverse website? It only pays the first split. This was fine until a few days ago.

Alby extension works fine on the PI site but not Podverse.

@mitch I doubt you changed anything but just wanted to report the issue.

6d ago

Cameron 6d ago

Anyone having problems with their Umbrel (1.4.2)? Tried updating bitcoind and thunberhub. Both are stuck in limbo.

Tried reinstalling thunderhub, but it just stares at me.

IPFSPodcasting payments are down until I can figure this out.

Podcasting 2.0 June 27th 2025 Episode 226: "TechNeck"

Adam & Dave are joined by Rockie Thomas of Soundstack to talk LIT, Chat and Workin' Wood http://l.curry.com/fQB

Jun 26

Hey @js

Does your PodcastsLive bot post anywhere besides here on Mastodon?

I'm asking becasue @bitpunk_fm and I are trying to push LIT on Nostr and having it post over there would be cool. It's mirrored via Mostr but thats hit or miss because most people don't connect to that relay.

Bitpunk mentioned to @StevenB about maybe adding it to Sovereign Feeds but your bot would catch them all.

I've been playing with Nostr bots so I'm going to try and repost the Mostr ones to see how it goes.

https://castamatic.com/+qKL68eWg/

Jun 25

bitpunk_fm Jun 25

I just published this episode. It was my talk from dev/hack/day in prague about podcasting 2.0 from the XML.

The biggest ask I have, which I discuss, is for podcast players to consider, immediately prompting the user to also subscribe to a podroll when they subscribe to a podcast.

Substack does this like this, and it's crazy effective. I think it's a much more word-of-mouth way to socialize podcasts.

bitpunk.fm unwound Live with Lightning from Dev Hack Day 2025

The talk I gave at dev hack day in Prague 2025 on livestreaming with lightning.

Jun 25

@francosolerio does Castamatic support rectangular chapter images? The other apps just letterbox the top and bottom.

This is the episode I'm listening to.

bitpunk.fm unwound - Live with Lightning from Dev Hack Day 2025 https://castamatic.com/+qKL68eWg/

@bitpunk_fm

Just saw that the PodcastGuru Beta has Strike integration now.

Connected with no problem but only 3 splits (strike) were paid to PC 2.0.

Also the Strike logo is hard to see in the setting (3rd pic) in dark mode.

I also tested episode 1 of No Solutions that has a Primal wallet in the splits and that split worked.

Alex (Podcast Guru)3d ago

@ChadF @adam @dave @podcastguru Hopefully more podcasters will switch to lnaddress (Strike doesn't support keysend).

@algrid @adam @dave @podcastguru

Lots to still hash out with the wallet stuff but seeing more options is a nice start.

Signing in with Strike was easy I just entered my email address, got a code emailed to me, entered it into PodcastGuru and I was all set.

Listeners could just setup weekly Bitcoin purchases in Strike and they would be set and not have to think about wallet management in apps anymore.

Sir TJ The Wrathful 1d ago

Jason (Podcast Guru)1d ago

@sirtjthewrathful @algrid @ChadF @adam @dave Not dumb questions at all, AFAIK Alby and Strike both support lnaddress and if you have an Alby account you should already have one, but Strike doesn't support keysend. This just just gives people more options. @algrid correct me if I'm wrong? As far as helipad is concerned, I'm not sure if any changes are required.

Kolomona - Sir Libre ⚡🤘1d ago

@podcastguru @sirtjthewrathful @algrid @ChadF @adam @dave

From what I understand Helipad only relays boostagram info received from the tlv record (keysend). So any lnAddress boostagram would not show up.

lnAddress only supports 200ish characters of metadata which makes boostagrams very small. A different messaging system would need to be employed to relay TLV data. I believe Fountain is using Nostr for this.

AFAIK there is no agreed upon way of supporting full BGs with lnAddress.

@Kolomona @podcastguru @sirtjthewrathful @algrid @adam @dave

1d ago

a lot of us want to figure this stuff out but its not really going anywhere sadly. :(

good news being able to pay from a wallet that only does lnadress/lnurl (dont know the difference) is very helpful for test.

@Kolomona @podcastguru @sirtjthewrathful @algrid @ChadF @adam @dave

Cameron 19h ago

@ericpp Does helipad plan to accept/log/show lnAddress payments?

I don't see an easy solution since you need a web server to negotiate & generate invoices on the fly.

Without feed, episode, & play timestamp (at least) in the payment message, it can't be linked to a podcast/episode/vts.

IPFS Podcasting also needs this info to distribute to the proper IPFS nodes. Without this info, it's just "I got sats".

@cameron It will once we figure out how to deal with the metadata problem in bolt11.

@merryoscar proposed Podpay https://podpay.org/ , but it got shot down because Nostr. Now he's using the funding tag to somehow capture the metadata.

Alecks Gates suggested a metaBoost tag (HTTP endpoint): https://github.com/Podcastindex-org/podcast-namespace/discussions/676

@StevenB built the The Split Box to split payments and store metadata: https://github.com/thebells1111/thesplitbox

@russell built a custom lnurl server and his own Helipad: https://github.com/podtoo/boostagramLIVE

Pod Pay

@cameron All of these options require the apps to adopt them.

I think we're headed into a very fragmented direction unless it gets figured out.

and those of us that are bought into lightning just keep using our own nodes with AlbyHub, Helipad and what ever apps support sending with Alby.

@ChadF @cameron Yep. Helipad will keep working fine with keysend payments.

You can have an LnAddress that points to a keysend address rather than lnurl. e.g. https://getalby.com/.well-known/keysend/ericpp

I think that would be the best option for self-hosters. It's just people using wallets that aren't Alby or Fountain that have to deal with this.

Cameron 18h ago

@ericpp I agree. TLV was a nice solution.

Sending, storing, & retrieving metadata via various methods & protocols feels "kuldgy".

Was considering a separate address/wallet for every incoming podcast/split, but that also feels messy, and doesn't solve the episode/VTS needs.

I don't have any "good" ideas. : (

@cameron Keysend is great because you don't need any additional infrastructure besides a Lightning node.

LnAddress on its own requires an HTTP server, which I think most podcasters have.

Lnurl requires an HTTP server application that can talk to your node.

Metadata requires an application and a database.

I liked Podpay the best out of the options because it's easy to integrate and to run a relay. Others didn't like it because of the Nostr social network and no privacy of metadata.

One cool thing I think we could do with Nostr is make Boost(agrams) way more visible. Just post to the major relays but I think that might get rate limited.

You could also just run your own relay so its all private or run a relay that you let other shows post to so its kind of like we have here but with Boost data.

I have chadf.nostr1.com and it cost 7k sats a month. I have it whitelisted so only certain people can post to it but anyone can read from it.

nostr1.com

Eric P 15h ago

@ChadF @cameron Yep. You can run your own relay or share a relay with others. It's just a dumb content store and it doesn't matter which one you use because they all work the same.

Privacy can also be handled through encryption, which is how private messages are kept private on Nostr.

@podcastguru @sirtjthewrathful @ChadF @adam @dave It looks like the biggest concern on the podcasters' side right now is about the lack of metadata. We put the boostagram message into the comment field for bolt11, but that's often too short.

@podcastguru @sirtjthewrathful @ChadF @adam @dave Regarding the Helipad thing that everyone seems to use - could someone explain to me what it is and how it works? Is it a standalone app or some web service or some Alby plugin or something else?

@algrid @podcastguru @sirtjthewrathful @adam @dave

14h ago

Its the best Boostagram reader we've ever had. Its this or use 3 other services and hope you see them all.

It runs on your node and reads all the PC 2.0 Boost that come in.

The Sent tab here does show what I send from apps like PodcastGuru that use Alby/Hub.

@ChadF @podcastguru @sirtjthewrathful @adam @dave I wonder if it could be extended with a small HTTP server. The apps would send boost metadata to it...

@ChadF @podcastguru @sirtjthewrathful @adam @dave Or Helipad could theoretically pull some data from Nostr. Or maybe podcast players would put a link to metadata into the bolt11 comment field and Helipad would pull that... I wonder what devs of Helipad think about all this.

Kolomona - Sir Libre ⚡🤘14h ago

@algrid @ChadF @podcastguru @sirtjthewrathful @adam @dave

@ericpp has been maintaining Helipad. It's awesome.

https://github.com/Podcastindex-org/helipad

It basically polls the node for tlv data and displays it in an easy to understand fashion. Plus other cool things like webhooks and reports

GitHub - Podcastindex-org/helipad: This is a simple lnd poller and web front-end to see and read boosts and boostagrams.

This is a simple lnd poller and web front-end to see and read boosts and boostagrams. - Podcastindex-org/helipad

GitHub

@Kolomona @algrid @podcastguru @sirtjthewrathful @adam @dave @ericpp

13h ago

The power of Helipad is that it runs in the same place your sats get sent to aka your node.

Could this be replicated? Probably, you just need all the data speaking the same language I guess. Just like cross-app comments. 🤪

@ChadF @podcastguru @sirtjthewrathful @adam @dave

Eric P 12h ago

@algrid That's the crux of it. There needs to be a publicly accessible service that accepts the metadata from the app and stores it for the user.

Helipad could expose an HTTP server, but most self-hosted nodes are behind home internet and NAT and not publicly accessible.

Nostr relays are public which makes them an easy solution. Custom HTTP services that store the data could work too as long as we agree on a common format and API.

Dave 10h ago

@ericpp @algrid @ChadF @podcastguru @sirtjthewrathful @adam Nostr didn’t get shot down as far as I remember. I was on board for everyone just building out what they thought would work best and then we just see what works best. Fountain is running their own Nostr relay and it seems to work ok for them. The issue will be keeping a websocket open on a mobile app. That’s why the metaBoost api was proposed. To give a way to send to a feed defined endpoint.

Dave 10h ago

@ericpp @algrid @ChadF @podcastguru @sirtjthewrathful @adam Nostr could work. It just needs something more friendly than a socket for this use case imo. But I could be wrong. I’ve been wrong before.

Eric P 10h ago

@dave Sorry, shot down probably isn't quite accurate. I think you all were happy with it as a solution in the board room, but the community had reservations over the Nostr part of it and it didn't get adopted.

I think the metaboost tag with a simple HTTP service is probably the way to go then. That lets you have whatever back end you want to store the data. But we need a common format and API to get data in and out. @algrid @ChadF @podcastguru @sirtjthewrathful @adam

Franco (Castamatic)4h ago

@ericpp @dave @algrid @ChadF @podcastguru @sirtjthewrathful @adam I think the common format should simply be the bLIP10 TLV record itself as defined in the specs. It's easy to send and receive that as a json object.