@adam @dave @podcastguru @algrid

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.

@ChadF @adam @dave @podcastguru Hopefully more podcasters will switch to lnaddress (Strike doesn't support keysend).
@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?
@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.

@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.

@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".

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

@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.

@ericpp @cameron

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.