For-profit tech companies like #Threads and #Flipboard are beginning to implement #ActivityPub, and that’s been causing a lot of chaos lately. Thus, I’ve found it helpful to take a step back, consider what it is about the fediverse that I value, and think about whether federation with these large platforms will bring us closer to or further from those goals.

With that in mind, I’ve come up with a few statements (in no particular order) that describe what I think is an “ideal” fediverse:

  1. No actor controls a large portion of visible activity.
  2. Users can move between instances without penalty.
  3. Creating and running an instance requires minimal effort.
  4. People on or entering the fediverse understand the variety of available options.
  5. There is no downside to using free and open-source platforms over proprietary ones.

While this ideal fediverse isn’t necessarily realistic or achievable, I’d like to see instance owners act in the interest of these principles. These definitely aren’t comprehensive and are of course my opinion, so what do you think an ideal fediverse looks like? Do you think these statements are good goals to aim for or not?

Now, to elaborate:

No actor controls a large portion of visible activity.

This is important for instances to be able to defederate from those with bad moderation, harmful values, etc. If a person or group controls a big portion of the content that people see on an instance, then that instance will lose a lot of that content should they defederate. That person or group would essentially be able to do whatever, and instances would find difficulty defederating because they’d lose so much visible activity and thus users.

If a single entity gets enough dominance over activity, they could make defederation from them out of the question for a ton of users. Furthermore, that entity could cripple the fediverse by simply leaving it, taking a bunch of users from other instances with them. This is a big concern many people have with Threads; if 90% of the activity you see on mastodon.social comes from Threads, then Meta would be able to nab a ton of mastodon.social users by leaving the fediverse, facing those users with the choice of either losing a ton of their connections & follows or jumping ship to Threads.

But you don’t even need a supermajority of content to cause that much harm. For example, take the threadiverse (Lemmy/Kbin). A large portion of visible activity is controlled by the admins of lemmy.world. Thankfully, they seem to nice people, but if they were to start (for example) being more lax with hate speech, other Lemmy/Kbin instances would either have to deal with it or lose access to a large portion of the activity pool. If any threadiverse instance were to defederate from lemmy.world — even if the lemmy.world admins started acting against the interests of the fediverse and its users — that instance would lose a dangerous number of users.

Users can move between instances without penalty.

One of the main benefits of the fediverse is that you can move to a different instance and still be able to view the same content. If the admins of your instance start making moderation decisions you disagree with or you just decide that you want to be on an instance that you yourself run, you’re able to move and still interact with the content pool. Thus, as long as the platform your destination instance uses (e.g., Firefish, Kbin, Mastodon) supports the same type of content as your old one, you should be able to move without any downsides. The more penalty there is for moving, the more people will feel trapped on an instance even if they want to leave.

This is partially a matter of robust systems for moving accounts, but it’s also a matter of having good options available. Mastodon has a ton of active, stable instances, so if you ever want to move (e.g., because your instance is or isn’t defederating from Threads), you can do so and still be able to use Mastodon. However, the only such instance on Kbin is kbin.social (not counting instances that run Mbin, a fork with different features & development). If you want to move from kbin.social to another Kbin instance, you don’t really have a lot of options. And if you’re on something that’s closed-source, you’ll be forced to move to a different platform entirely, which may not be great for the user — an important reason why free and open-source software should be prominent on the fediverse.

Obviously, this is something that might be impossible to achieve. But even if we can’t eliminate the strings attached to moving to another instance, we should try to minimize them.

People can create and run their own instances to their liking with minimal effort.

If a user wants to, they should be able to control their interactions on the fediverse through running their own instance, and doing so should require as little effort as is feasible. Many people have already set up single-person instances for the purpose of having more control over their data. If people can’t do that, then they’re forced to put their account and content under the control of other people. Of course, most people are fine with this provided that they trust their instance admins, but the option to be your own admin should be as available as possible.

This is part of why it’s so important to have prominent open-source platforms. If Mastodon weren’t open-source, then anyone who likes Mastodon but wants to control their content would be out of luck. If you like the Threads interface but don’t want to be on an instance run by Meta, you just don’t have that option.

People on or entering the fediverse understand the variety of available options.

If someone isn’t aware that they’re on the fediverse, then they can’t really benefit from the openness and customizability that it provides. A mastodon.social user who knows nothing of the fediverse won’t know that they can move to a different Mastodon instance or interact with the same content using Friendica, as they won’t know that the options exist to begin with.

Furthermore, people will have more incentive to preserve an open fediverse if they’re aware that it exists. If the fediverse is filled with people who, for example, think that Threads is all there is or didn’t come to Threads with an awareness of the fediverse, the fediverse becomes much easier to undermine.

There is no downside to using free and open-source platforms over proprietary ones.

If someone wants to join a closed-source instance run by a for-profit company, they should absolutely be able to. However, that should ideally be because they prefer an instance moderated by Meta, not because the free and open-source alternatives are relatively lacking. Open-source software is extremely important in order for users to have options and agency, so we should aim for these factors to not come with a sacrifice. Otherwise, companies will be able to draw most newcomers to their instance and attain a large share of the content on the fediverse, which is bad as discussed with Statement #1.

Going by this principle, if the owner over a closed-source fediverse platform starts trying to create exclusive functionality that would attract people their instance, they should be regarded with extreme caution. If you’re familiar with the whole “Embrace, Extend, Extinguish” thing, a company doing such would be the “Extend” phase of EEE, and that’s a situation we should avoid at all costs.

  • kpw@kbin.social
    3·
    11 months ago

    So we should defederate because we will have issues defederating due to the amount of content we lose? Isn’t that kind of self-contradictory?

    • ThatOneKirbyMain2568@kbin.socialOP
      5·
      11 months ago

      Let me try to explain a bit better.

      Let’s take an instance called Instance A. Instance A is currently on the fediverse, which we’ll say is pretty evenly distributed. No instance has a large enough portion of users whereby others would have problems with activity loss if they defederated, which is good. If any instance starts doing things that Instance A doesn’t agree with, they can defederate, and less activity won’t be much of a concern with defederating from that single instance.

      But now, let’s take Instance B. Instance B is planning to implement ActivityPub and join the fediverse, and when it does so, it will control 80% of the activity. In other words, it has as much activity as the rest of the fediverse combined.

      However, Instance B isn’t particularly trustworthy. They don’t value the open web like the rest of the fediverse does, their moderation is extremely poor, and they haven’t cared for general well being in the past if it meant raising profits.

      Here, Instance A and instances like it have two options: defederate immediately, or wait and see.

      • If it defederates immediately, Instance A will see some users move to other parts of the fediverse because they’re excited about the 5x increase in activity from Instance B. They probably won’t go to Instance B now, but maybe Instance C or D. However, a lot of people will be fine. After all, activity is staying the way it is, and Instance B is untrustworthy anyway.
      • If it waits and sees, this allows people on Instance A to enjoy and get used to the 5x increase in activity. Not bad so far.

      However, let’s say Instance B starts having moderation issues (e.g., widespread hate speech and more-than-usual spam) as everyone reasonably predicted. Instance A now wants to defederate.

      • If it defederated before, no problem! Nothing needs to be done.
      • If it didn’t and wants to start defederation now, good luck. Now, everyone on Instance A has gotten used to the 5x activity on Instance B, and you’re going to have an extremely difficult time convincing them to cut the activity they see and the users they follow by 80%. Way more people will leave Instance A if it defederates now than if it had just defederated early on.

      In other words, if people on Instance A come to rely on Instance B for the activity they’re used to, way more people will join the camp of “I’m leaving if you defederate with Instance B” then if Instance A just defederated from the get-go.

      Let’s take another example. Instance B wants to try to grab a bunch of users, so after some time, they stop federating at all.

      • If Instance A defederated, the people there are fine. They never saw stuff from Instance B anyway.
      • If Instance A didn’t defederate, then 80% of the content that people are used to will suddenly be gone. Most of the accounts they follow will be disconnected, and activity will fall a ton. These users on Instance A will have two options: stay, with a horrendous drop in activity and no posts from the accounts they’re most interested in; or just go to Instance B.
        In either case, Instance B will be fine. Most interaction was between Instance B users, so this won’t be that much of a deal. But for users on other instances that are used to seeing stuff from B, it’d be catastrophic.

      In short, defederating immediately has much smaller consequences than trying to defederate when whoever you want to defederate from controls most of the activity that your users see.