this post was submitted on 19 Sep 2024
-65 points (7.8% liked)

Fediverse

28483 readers
1095 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago
MODERATORS
 

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)

  1. If I charge my users, they may simply register on another instance and keep interacting with my instance to avoid paying the fees.
  2. 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:

  1. the universal currency, let's say "fedicoin". Fedicoin can be traded on trading platforms like normal cryptocurrencies.
  2. 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:

  1. how many fedicoins and instance-specific coins each instances owns.
  2. 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:

  1. 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.
  2. 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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 2 months ago

Because it's a professional service and they are willing to pay to not have to deal with:

  • instance drama
  • overloaded moderation teams
  • other entitled users who are not paying and still find themselves in the right to complain
  • admins who are doing this as hobby, so may disappear because their day job got more demanding and they can not maintain the instance
  • admins who were overly enthusiastic but not experienced enough and lose a whole database
  • etc, etc, etc.

There are some other benefits (specific to my business):

  • I pledged to give 20% of the profits to all the open source projects I host. So people paying me are indirectly supporting the Fediverse.
  • Full integration with Mastodon/Lemmy/Matrix/Funkwhale
  • Paying members can participate in a zero-commission crowdfunding platform (which is a shame that haven't caught on)

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.