Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://podcastindex.social/users/js/statuses/112537972136070566">John Spurlock (js@podcastindex.social)'s status on Saturday, 01-Jun-2024 21:35:13 JST</a><a href="https://podcastindex.social/@js" title="js@podcastindex.social"><img src="https://gnusocial.jp/avatar/58273-48-20221207220514.webp" width="48" height="48" alt="John Spurlock" style="position: absolute; left: 0; top: 0;">John Spurlock</a><div><a href="https://podcastindex.social/@adam/112537804824588804" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/83772" title="ademan@thebag.social">Ademan</a></li><li><a href="https://gnusocial.jp/user/99786" title="dave@podcastindex.social">Dave</a></li></ul></div></section><article><p><a href="https://podcastindex.social/@adam">@adam</a> <a href="https://thebag.social/users/ademan">@ademan</a> <a href="https://podcastindex.social/@dave">@dave</a> </p><p>Why the need for keysend again?  </p><p>It looks like this is a way for the listener app to orchestrate lightning invoices/payments while steering clear of compliance stuff (which would fall on wallet providers, or "self" for self-hosted nodes I guess)</p><p>ie wouldn't you build on this if you were starting the value tag idea today?</p><p><a href="https://blog.getalby.com/an-open-payment-api-for-podcast-apps/" rel="nofollow noreferrer">https://blog.getalby.com/an-open-payment-api-for-podcast-apps/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3177484#notice-6281651">In conversation</a><time datetime="2024-06-01T21:35:13+09:00" title="Saturday, 01-Jun-2024 21:35:13 JST">about 6 months ago</time> <span>from <span><a href="https://podcastindex.social/@js/112537972136070566" rel="external" title="Sent from podcastindex.social via ActivityPub">podcastindex.social</a></span></span><a href="https://podcastindex.social/@js/112537972136070566">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
John Spurlock (js@podcastindex.social)'s status on Saturday, 01-Jun-2024 21:35:13 JSTJohn Spurlock
in reply to
@adam @ademan @dave
Why the need for keysend again?
It looks like this is a way for the listener app to orchestrate lightning invoices/payments while steering clear of compliance stuff (which would fall on wallet providers, or "self" for self-hosted nodes I guess)
ie wouldn't you build on this if you were starting the value tag idea today?
https://blog.getalby.com/an-open-payment-api-for-podcast-apps/
In conversationabout 6 months ago from podcastindex.socialpermalink

Public

Embed Notice

HTML Code

Corresponding Notice