#assetflow — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #assetflow, aggregated by home.social.
-
we need decentralized fiat. my bank to your bank. no crypto, no middleman.
-
we need this worldwide. being able to fully integrate direct and automatic payments for media we consume into apps (without the problems of crypto) would free creators from the limits of corporate gatekeepers. the way the money currently works is what keeps people on YT vs #peertube and #owncast, for example. or consider a decentralized alternative to #Spotify. it would open up so many opportunities.
-
yes but I don't think coops in the middle solve this either. they become more useful as they get bigger but that gives them more power and they can always eventually abuse that power. or maybe even just do something that only a quarter of the musicians hate. it can't sustain.
instead imo we need less work on competing systems, more work on protocols/APIs, apps and servers. and then a fuckton of advocacy for decentralized fiat.
-
I have been thinking about payments on the Fediverse (for a while).
3/
That obviously is not an exhaustive list of archetypes with their wants and pains.
But, I do think we need an extensive list — that we can check any proposed Fediverse payment system against.
.
-
I have been thinking about payments on the Fediverse (for a while).
2/
For example —
A parent (archetype) may want to send money to their spouse, or give allowance to their child, etc.
Someone working abroad (archetype) may want to send money back home to their family (i.e., remittance).
An SMB (archetype) may want to accept payment for the sale of a product.
A freelancer (archetype) may want to get paid for their irregular income.
Etc.
...
-
I have been thinking about payments on the Fediverse (for a while).
1/
To make sure a Fediverse payment system is useful we should think in terms of a set Archetypes and each of their wants and a pains.
(Product people often call "Archetypes": Personas. Marketers often call "Archetypes": Segments.)
...
-
"Nowadays, if I want a book or song, there’s a good chance I can buy it online from the person who makes it, with no third party except the payment processor."
We've technically decentralized media production/consumption and the attention machine. Of course we still need to make these systems easier and greatly increase adoption.
But the money people still have us by the balls. That's really why creators aren't here yet.
-
The hash-tag to talk about Fediverse Payments is:
(It also includes transferring things that are non-money, too. Thus the generic name.)
-
I have been thinking about payments on the Fediverse (for a while).
Another factor to consider is — does a asset flow destination such as:
＠joeblow＠example·com
Eventually resolve to one concrete low-level asset flow address, or multiple?
For example, when I go to a store, they accept loyalty points, cash, credit card, etc.
There are pros and cons for both.
-
2/
As, software may want to resolve:
flow:joeblow＠example·com/a/b/c?d=e
To:
https;//host·example/some/prefix/a/b/c?d=e
As an intermediary step.
(For example, the low-level asset flow destination address or route could be in an HTTP header, or in the HTML <head> as a <meta /> or <link /> or <script>, etc.)
-
1/
I have been thinking about payments on the Fediverse (for a while).
If we wanted to come up with a new URI scheme — basically something like acct URI with paths. I think we should also support URL queries, too.
I think it will make (downstream) resolution steps easier.
We'd have to pick a scheme now. For now, I'll just use "flow" for now.
So this:
＠joeblow＠example·com/a/b/c?d=e
Would turn to:
flow:joeblow＠example·com/a/b/c?d=e
As…
-
4/
So, that suggests we may need to create a new URI scheme for this.
(Of course, I think we would still want a way to make it work with acct URIs, too, as a back-up. But the new URI scheme would be attempted first when trying to do a resolution.)
-
3/
So, if you wanted an alternative to acct URIs that include a path, what are our options.
The closest thing I can remember to an acct URI with a path is:
tag URIs (IETF RFC-4151)
https://datatracker.ietf.org/doc/html/rfc4151(Tag URIs have nothing to do with hash-tags.)
But, I don't think tag URIs would work for this use case. tag URIs require a date that I suspect doesn't make sense for this use case.
So...
-
2/
Fediverse IDs get turned into acct URIs before they given to WebFinger.
But, acct URIs don't support paths.
So, what do you give WebFinger if you Fediverse ID has a path.
As I mentioned before, either you (1) have to use some other type of URI with WebFinger, or (2) use an acct URI with WebFinger and have the path come into play at some point AFTER the WebFinger step.
Or, do both. First trying №1, and if that fails trying №2.
So...
-
1/
I have been thinking about payments on the Fediverse (for a while).
Let's talk more about what you give WebFinger if you are trying to send an asset to a Fediverse ID with a path such as:
＠joeblow＠example·com/prd123
Or, the asset flow address is somethinglike:
%joeblow＠example·com/prd123
(Assuming we use the "%" character as the prefix.)
...
-
3/
Do you somehow give that information to WebFinger?
acct URIs don't support paths.
So, either you (1) have to use some other type of URI with WebFinger, or (2) use an acct URI and have the path come into play at some point AFTER the WebFinger step.
Or, could do both, trying №1 first, and if that fails, trying №2.
-
2/
What happens if you want to send it to a sub- asset flow destination. The exact notation for it is yet to be decided, but, what if the Fediverse'ish ID is somethinglike:
＠joeblow＠example·com/prd123
Or, the asset flow address is somethinglike:
%joeblow＠example·com/prd123
(Assuming we use the "%" character as the prefix.)
How is that resolved?...
-
1/
I have been thinking about payments on the Fediverse (for a while).
If you want to send an asset to a Fediverse ID such as:
＠joeblow＠example·com
Or, and asset flow address such as:
%joeblow＠example·com
(Assuming we use the "%" character as the prefix.)
Then how to resolve that is straightforward.
I.e., change it to an acct URI, run it through WebFinger, get the activity URL from the JRD WebFinger gave you, etc.
But...
-
I have been thinking about payments on the Fediverse (for a while).
Another thing I have been wondering about — should the asset flow destination address be a Fediverse ID such as:
＠joeblow＠example·com
Or maybe, should the first character change to something else. For example:
%joeblow＠example·com
(Or some other character prefix.)
There are pros and cons for doing it each way.
(Could always support both.)
-
I have been thinking about payments on the Fediverse (for a while).
One thing you'd want is to be a able to send an asset to a Fediverse ID.
For example, send $5 to:
＠joeblow＠example·com
Resolving a Fediverse ID to something you can send an asset to is straight-forward.
One challenge is, what if a user wants to have multiple destinations?
What should the notation for that be?
＠joeblow＠example·com/prd123
＠joeblow+prd123＠example·com
＠joeblow＠example·com?prd123