Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 16-Jan-2024 02:12:06 JST Alex Gleason

   • Dave
   @dave How should zaps be used across the Mostr bridge to work with Podcasting Index in a useful way?
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jan-2024 07:33:29 JST silverpill

     in reply to

     • Dave

     @dave @alex Is it possible to encode necessary information in URI?

     Re-purposing PropertyValue is a nice hack, but I think a better solution is needed. I wonder if FEP-0ae0 is applicable: https://codeberg.org/fediverse/fep/src/branch/main/fep/0ea0/fep-0ea0.md

     Alex Gleason likes this.
   • Embed this notice
     Dave (dave@podcastindex.social)'s status on Tuesday, 16-Jan-2024 07:33:30 JST Dave

     in reply to

     @alex Good point. If I start adding the LUD-16 to the actor profile would that be a solution? It doesn’t solve splits but I don’t think Nostr has real splits yet anyway.

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 16-Jan-2024 08:25:49 JST Alex Gleason

     in reply to

     • silverpill
     • Dave
     @silverpill @dave I was thinking the same thing.
   • Embed this notice
     errhead (errhead@poa.st)'s status on Tuesday, 16-Jan-2024 21:59:01 JST errhead

     in reply to

     • silverpill
     • Dave
     @silverpill @dave @alex >Is it possible to encode necessary information in URI?
     
     well, there's:
     - lnurlp zap getalby.com/.well-known/lnurlp/alexgleason
     - keysend zap getalby.com/.well-known/keysend/alexgleason
     
     That FEP seems like a perfect match for the podcasting 2.0 funding tag github.com/Podcastindex-org/podcast-namespace/blob/main/docs/1.0.md#funding
     Alex Gleason likes this.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jan-2024 23:37:41 JST silverpill

     in reply to

     • Dave
     • errhead

     @errhead @dave @alex

     FEP-0ea0 also supports payment URIs like BIP21.

     Perhaps someone already proposed an URI scheme for LUD-16 addresses? Similar to mailto: for email addresses and acct: for webfinger addresses,

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 16-Jan-2024 23:39:38 JST Alex Gleason

     in reply to

     • silverpill
     • Dave
     • errhead
     @silverpill @errhead @dave Yes. I'm not sure about the spec, but I found them here while poking around yesterday https://github.com/nbd-wtf/js-lnurl/blob/master/src/helpers/decodelnurl.ts#L15
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 16-Jan-2024 23:46:02 JST Alex Gleason

     in reply to

     • silverpill
     • Dave
     • errhead
     @silverpill @errhead @dave Also lnurl is an insane concept to begin with. It's literally a binary encoded URL for the sole purpose of being bech32 compatible. Like for the same reason you would put a protocol in front of some identifier just so it parses as a URL. lnurl is the equivalent idea for bech32. lud16 identifiers can be converted into lnurls by simply taking https://${host}/.well-known/lnurlp/${name}, converting to binary, then bech32 encoding it. To me it's kind of a crazy idea that makes everything more opaque to users and it's extra work. It's weird people have built so much up around this idea.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 16-Jan-2024 23:47:48 JST Alex Gleason

     in reply to

     • silverpill
     • Dave
     • errhead
     @silverpill @errhead @dave It gives the impression to users that it's not really just a plain URL. That it's somehow a key like bc1 addresses.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jan-2024 23:48:02 JST silverpill

     in reply to

     • Dave
     • errhead

     @alex @dave @errhead

     Here's how I would represent LUD-16 with FEP-0ea0 (and hypothetical lud16: URI scheme):

     "attachment": [ { "type": "Link", "name": "⚡", "href": "lud16:alex@alexgleason.me", "rel": ["payment"] } ]
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 16-Jan-2024 23:52:26 JST Alex Gleason

     in reply to

     • silverpill
     • Dave
     • errhead
     @silverpill @errhead @dave We should probably put the actual lnurl in there since it has known URI forms and can be converted to from lud16 ids.
   • Embed this notice
     Dave (dave@podcastindex.social)'s status on Wednesday, 17-Jan-2024 23:27:30 JST Dave

     in reply to

     • silverpill
     • errhead

     @alex @silverpill @errhead Podcasting 2.0 doesn’t use LNurl. It uses “keysend” because it eliminates the need for round-robin to get an invoice and thus makes things simpler/faster for podcast apps sending payments sometimes multiple times per minute.

     A custom URI format is probably needed here in order to bring all of that payment information over intact. It can include a key/value pair for routing the payment.

     Alex Gleason likes this.