Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mitra.social/objects/01861ea7-a5f1-5662-7433-512b98ad1598">silverpill (silverpill@mitra.social)'s status on Sunday, 05-Feb-2023 07:59:48 JST</a><a href="https://mitra.social/users/silverpill" title="silverpill@mitra.social"><img src="https://gnusocial.jp/avatar/85321-48-20230105202807.webp" width="48" height="48" alt="silverpill" style="position: absolute; left: 0; top: 0;">silverpill</a><div><a href="https://gleasonator.com/objects/5b1ec37b-fd0a-4f4b-a743-0df95cf13b57" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/9080" title="jawsh@fedi.jmizzle.com">Jawsh Mizzle</a></li></ul></div></section><article><p><a href="https://gleasonator.com/users/alex">@alex</a> <a href="https://fedi.jmizzle.com/@jawsh">@jawsh</a></p><p>There's a thread on SocialHub where I posted some ideas about payment links: <a href="https://socialhub.activitypub.rocks/t/fep-8c3f-web-monetization/2719/21">https://socialhub.activitypub.rocks/t/fep-8c3f-web-monetization/2719/21</a><br>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:</p>{
  "name": "My lightning invoice",
  "type": "PaymentLink",
  "href": "lightning:lnbc50u1p3a665lpp565ng6amk4xsavfgmyr9ga3vej8nysmsxs3qhjz25qqdjm50g4ewqdpqgdhkven9v5s8gmeqwashymfqd4jjqatscqzpgxqyz5vqsp5uvcssdu3hu9n8v2jtrttwcy4wp7uu7vpcau3mt0nk0mnr805naxq9qyyssqavc6z5y6kcmhl3vqmq9lkparykwp8c3cme0vukmc206l7mx8jwtscv7vjufdxtzps8wtdzrv5cmcss5f00mvn7pk37msz6kkk7e37ksqgcy7nx",
  "rel": "https://bitcoin.org/lightning-invoice"
}
<p>Can be an attachment or a tag, IMO both are fine. Subscriptions links in Mitra are currently added to attachment array on actor object.</p><p>I've been planning to propose it as a FEP, so it's good to see people requesting such features.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/1146927#notice-2469477">In conversation</a><time datetime="2023-02-05T07:59:48+09:00" title="Sunday, 05-Feb-2023 07:59:48 JST">Sunday, 05-Feb-2023 07:59:48 JST</time> <span>from <span><a href="https://mitra.social/objects/01861ea7-a5f1-5662-7433-512b98ad1598" rel="external" title="Sent from mitra.social via ActivityPub">mitra.social</a></span></span><a href="https://mitra.social/objects/01861ea7-a5f1-5662-7433-512b98ad1598">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: socialhub.activitypub.rocks</div><h5><a href="https://socialhub.activitypub.rocks/t/fep-8c3f-web-monetization/2719/21">FEP-8c3f: Web Monetization</a></h5><div></div></header><div>I actually like the idea of “monetization” property, but I think it can be made more generic. There’s no reason to commit to a particular standard like WebMonetization.  We can make it an object with type property but treat everything else as implementation detail, for example:  {     "name": "Alice",     "monetization": {         "type": "WebMonetization",         ...     },     ... }  But also:  {     "name": "Alice",     "monetization": {         "type": "LightningAddress",         ...     }...</div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: bitcoin.org</div><h5><a href="https://bitcoin.org/en/">Bitcoin - Open source P2P money</a></h5><div></div></header><div>Bitcoin is an innovative payment network and a new kind of money. Find all you need to know and get started with Bitcoin on bitcoin.org.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
silverpill (silverpill@mitra.social)'s status on Sunday, 05-Feb-2023 07:59:48 JSTsilverpill
in reply to
- Alex Gleason
- Jawsh Mizzle
@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.
In conversationSunday, 05-Feb-2023 07:59:48 JST from mitra.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: socialhub.activitypub.rocks
  FEP-8c3f: Web Monetization
  I actually like the idea of “monetization” property, but I think it can be made more generic. There’s no reason to commit to a particular standard like WebMonetization. We can make it an object with type property but treat everything else as implementation detail, for example: { "name": "Alice", "monetization": { "type": "WebMonetization", ... }, ... } But also: { "name": "Alice", "monetization": { "type": "LightningAddress", ... }...
2. Domain not in remote thumbnail source whitelist: bitcoin.org
  Bitcoin - Open source P2P money
  Bitcoin is an innovative payment network and a new kind of money. Find all you need to know and get started with Bitcoin on bitcoin.org.

Public

Embed Notice

HTML Code

Corresponding Notice