Conversation

Notices

1. Alex Gleason (alex@gleasonator.com)'s status on Sunday, 05-Feb-2023 08:12:12 JST Alex Gleason

   • silverpill

   Thinking about ActivityPub crypto integrations

   https://gitlab.com/soapbox-pub/soapbox/-/issues/1355#note_1265864906

   @jawsh @silverpill

   • silverpill (silverpill@mitra.social)'s status on Sunday, 05-Feb-2023 08:12:11 JST silverpill

     in reply to

     @alex @jawsh

     There's a thread on SocialHub where I posted some ideas about payment links: https://socialhub.activitypub.rocks/t/fep-8c3f-web-monetization/2719/21
     I think payment information should be represented as objects with type Link (or it could be a new subtype of Link such as PaymentLink), because in most cases you can generate payment URI of some kind. For example, here's how we can represent LN payment link:

     { "name": "My lightning invoice", "type": "PaymentLink", "href": "lightning:lnbc50u1p3a665lpp565ng6amk4xsavfgmyr9ga3vej8nysmsxs3qhjz25qqdjm50g4ewqdpqgdhkven9v5s8gmeqwashymfqd4jjqatscqzpgxqyz5vqsp5uvcssdu3hu9n8v2jtrttwcy4wp7uu7vpcau3mt0nk0mnr805naxq9qyyssqavc6z5y6kcmhl3vqmq9lkparykwp8c3cme0vukmc206l7mx8jwtscv7vjufdxtzps8wtdzrv5cmcss5f00mvn7pk37msz6kkk7e37ksqgcy7nx", "rel": "https://bitcoin.org/lightning-invoice" }

     Can be an attachment or a tag, IMO both are fine. Subscriptions links in Mitra are currently added to attachment array on actor object.

     I've been planning to propose it as a FEP, so it's good to see people requesting such features.

   • silverpill (silverpill@mitra.social)'s status on Monday, 06-Feb-2023 00:05:09 JST silverpill

     in reply to

     • Raphael Lullis

     @raphael @jawsh @alex It seems that OP wants static links, and they can be represented as attachments or tags.

     In cases where actors need to interact somehow it is recommended to use standardized activities such as Offer() or Invite(). Any activity can carry payment details, what's more important is the context of payment

   • Raphael Lullis (raphael@mastodon.communick.com)'s status on Monday, 06-Feb-2023 00:05:10 JST Raphael Lullis

     in reply to

     • silverpill

     @alex @jawsh @silverpill

     Generalizing the use case, couldn't we have "PaymentRequest" and "Payment" activity types? And perhaps use the Payment Request Web API to implement the UI as a browser extension?

     https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API/Using_the_Payment_Request_API

   • silverpill (silverpill@mitra.social)'s status on Monday, 06-Feb-2023 00:23:31 JST silverpill

     in reply to

     • Raphael Lullis
     • teknomunk

     @teknomunk @raphael @alex I would send an Offer activity:

     { "type": "Offer", "object": "https://my-store.com/item/1", "paymentDetails": { ... }, "to": "https://example.com/users/happy_customer" }
   • teknomunk (teknomunk@apogee.polaris-1.work)'s status on Monday, 06-Feb-2023 00:23:32 JST teknomunk

     in reply to

     • Raphael Lullis
     • silverpill
     I think a "PaymentRequest" would be an (yet undefined) Invoice with one or more payment options attached/tagged. That may be useful to have anyways for when someone gets around to making a federated online store.