The dilema of charging the users and a solution by integrating blockchain to fediverse
I'm planing hosting an instance, and I think that in the end I'll have to let the users pay for subscription. But just when I was imagining how I should design the subscription, I found there's a dilemma arose from the nature of fediverse:
(assume that people really like my instance for some reason)
If I charge my users, they may simply register on another instance and keep interacting with my instance to avoid paying the fees.
I can limit activities of the users who don't register on my instance to force them to subscribe my instance, but such action is obviously destructive to the fediverse.
I think this is not only my own problem. I think every instances with some scale faces the issue of costs, and relying on donation forever may not be a long term solution. So here's the question: how to let the owners of the instances get paid without violating the values of fediverse, i.e. decentralization and federation? Moreover, the solution should let the instances with higher popularity earn more money, so that'll encourage people to host high-quality instances. And I just figured out a (possibly very rough) solution by integrating blockchain to fediverse.
First, there will be a blockchain. There will be these cryptocurrencies:
the universal currency, let's say "fedicoin". Fedicoin can be traded on trading platforms like normal cryptocurrencies.
the currency of every single instance, e.g. InstanceA coin for InstanceA, InstanceB coin for InstanceB. The instance-specific coins are only used for federation between instances.
and the blockchain holds these data:
how many fedicoins and instance-specific coins each instances owns.
how many fedicoins each non-instance users owns, if any.
I guess it would be better that only the instances can own instance-specific coins.
For operating the blockchain, there should be nodes to hold the data and process the transactions. The nodes can be either served by the instances or the non-instance machines. The nodes earn fedicoins.
When instances are federating with each other, every "demand" requires paying some instance-specific coins. The price of each type of demand will be predefined in the federation APIs. For example, if a user on InstanceB want to post on InstanceA, then InstanceB have to pay 10 lemmy.world coin to lemmy.world, and vise versa.
To earn instance-specific coins to pay for the demands, all the instances will "trade" automatically with other instances, and the "exchange rate" will be determined by some algorithm, possibly based on the amount of demands between each two instances. For example, if on average the demand from InstanceB to lemmy.world is 5 times more than the demand from lemmy.world to InstanceB, than in a trade, InstanceB may get 1000 lemmy.world coin, while lemmy.world may get 5000 InstanceB coin.
There will be an upper limit for every instance to own other instances' coins. For example, when lemmy.world owns 100,500 InstanceB coins, which exceeds the limit 100,000, then lemmy.world will refuse to trade with InstanceB by InstanceB coins. Under such condition, InstanceB have to trade with lemmy.world by the fedicoin. The owners of InstanceB will have to purchase fedicoin to let InstanceB trade with lemmy.world to maintain the fedaration.
Currently I think that the exchange rate between fedicoin and an instance-specific coin should be controlled by the owners of each instance, because each instance may have different costs for machines and moderation.
Finally, (hopefully) we'll have a fediverse like this:
The highly-demanded instances earn fedicoins, which can be exchanged to real-world currencies. Such mechanism also encourages hosting high-quality instances and more open federation.
The instances can simply charging their users normally by real-world currencies, so the users don't have to bother about cryptocurrencies.
Other side notes:
Defining the prices of the demands may be tricky? For example, if my understanding is correct, there's no actual action like "read" when instances are communicating with APIs.
For the automatic trades between instances, of course there should be some controllable configuration, e.g. "don't buy coins over some price from some instances".
I'm just interested in the fediverse, and I hope my ideas can be helpful for its development. Any comments or crossposting are welcome and thank you for your reading.
That's just as extreme, and just as short- sighted.
Enshittification is about companies that offer a bunch of things for "free" (actually, using VC funds) on an attempt to get to dominate the market first. When they get the users and establish a monopoly, the VC starts demanding to see the returns of their investment and that's when enshittification happens.
Smaller service providers that make a living out of charging directly for their services do not need VC and have no reason to squeeze their users and the nature of the Fediverse ensures that no single provider can create a monopoly.
Small, independent businesses are healthy and should be encouraged. Saying "money = bad" is a recipe to keep things indefinitely small and unable to compete with the alternatives.
Who will keep the money? Who will calculate what users will have to pay? Who will verify that the money is being used for the purpose it was paid for? How will bringing crypto payments to fediverse increase users, considering that 99% of people have never used crypto before? What will happen to the data of users who decide not to pay anymore? Let's assume that all instances offer paid membership; wouldn't monopoly occur if a corporate/suspicious instance offers completely free membership? Wouldn't offering paid memberships hold instance admins legally liable?
Who will leave the mainstream platforms that are completely free and have many more users, and then pay and use a platform that is 1 in 100,000 times the size?
Even though I received a donation of about $10 for 1 year, I think the current system should continue. If money is involved in something, it would be abused.
You are creating a strawman. I'm not saying that this particular model proposed by OP is something interesting. I'm not going to respond to that or the crypto part, but I can respond about the "money movement" required by my service :
Who will keep the money?
It's a business. People pay for a service. The service provider keeps it.
Who will calculate what users will have to pay?
It's a business. There is a price for the service. Service provider says "I want $X/month for the service". Customer pays if the price is acceptable to them, and goes elsewhere if not.
Who will verify that the money is being used for the purpose it was paid for?
It's a business. As long as the service is provided at a level that the customer is satisfied, customers have no deal in "verifying" anything.
You know what is funny? For years we have talked about "If you are not paying for the product, you are the product", and yet completely ignore this when it comes to the people hosting Mastodon/Lemmy/Pleroma/Matrix servers. I don't think people really have learned the lesson.