@Chocobozzz@thelinuxEXP@Techaltar@dansup@jwildeboer I would add that any implementation of a payment subsystem should probably be done at protocol level, so individual implementations of #ActivityPub don’t have to reinvent the wheel - doing #payments right is a hard problem, and it doesn’t make sense to fragment the efforts by solving the same problem multiple times on Mastodon/WriteFreely/PeerTube/Pixelfed etc.
The payments subsystem should be better integrated in the ActivityPub ecosystem compared to a “Donate here” link that redirects to a 3rd-party provider. This is probably the right chance of giving the HTTP 402 code the implementation it deserves.
I left the payments industry a few years ago so I’m not sure of what open solutions and protocols are in the market that could be already leveraged, but maybe something like OpenPayments could be a good starting point - there are many efforts on the open banking standards lately, with different degree of maturity, and IMHO a good implementation of payments over ActivityPub could be a great driver for adoption.
I’ve got the feeling that if we don’t do this right then Threads could scoop up this chance for an “embrace” to “extend” pivot.