Oof, that’s never fun. When I’m typing a long comment, I always spam copy it so that I can paste it back if I end up losing it. On PC, you can even use Windows+V to pull up a clipboard history, which has come in handy more than once.
Anywho, glad my reply was helpful! There are a lot of ways to interact with the content on the fediverse, and it seems like you’re well on your way to finding one that works best for you. Hope you enjoy it here!
I think there are a few culprits here.
Not everything wants to be an everything app. While everything in the fediverse uses ActivityPub, that doesn’t mean everything has to aim to be interoperable. I wrote a lengthy rant about this here, but essentially, it’s important to have things with a more specific, restricted purpose if we want the fediverse to be accessible. If someone just wants a thread aggreegator (i.e., just Reddit’s style of media), they shouldn’t be forced to grapple with microblogging features more fit for a Twitter-like. There are some platforms that aim to combine different media types—Kbin/Mbin has both thread aggregation and microblogging, and I’ve heard that Friendica tries to work well with everything. Even so, if someone wants federated Reddit, they should be able to have federated Reddit, and Lemmy aims to provide that. The same way that Pixelfed (an image-sharing platform like Instagram) doesn’t need to incorporate Reddit-style threads or Twitter-style microblogs, Lemmy doesn’t have to do it all.
Federation is still in the works. Something to keep in mind is that most of these platforms are early in development and still working out a lot of bugs. Kbin (the platform I use) is an obvious example due to its currently incredibly spotty microblog federation (tho I’ve heard that Mbin has implemented fixes to fare better in this regard). We have to be patient while all the kinks are worked out. As much as we all wish it didn’t, software development takes time—a lot of it.
Admins can sometimes be a bit trigger-happy with defederation. I don’t think the fediverse has quite grasped that defederation is essentially the nuclear bomb of instance moderation tools, cutting off interaction with all users of an instance. While there are times where this is justified (even preemptively, such with Threads imo), there are times where the nuke has been threatened over a quarrel between admins or disagreements about other defederations. Hopefully, this will cool down as the fediverse matures, but we’ll have to see how that pans out (especially with Threads federation growing ever nearer).
They’ve been mostly resolved in my experience. Kbin.social has been working great.
@interstellar is being developed for Android, and Lunar is working on Kbin support for iOS. Still a good ways to go tmk, but we’re getting there!
If I’m not free to join the Fediverse from the server of my choice, whether that’s mastodon.social or threads.net, is the Fediverse truly free?
Joining the fediverse is just a matter of using a platform that implements ActivityPub (the protocol that lets servers communicate with each other. If Threads implements ActivityPub, it’s part of the fediverse, and the people on Threads can interact without any instance that chooses to federate.
However, instances don’t have to federate with Threads. That’s part of the freedom of the fediverse. If an instance admin decides that they don’t want to deal with an influx of hate, don’t want most of the content their uses see to be from Meta, or just don’t want to federate with a for-profit company that has an awful track record, they should be able to defederate. If a user of that instance really wants to see Threads content, they should be able to move to an instance that lets them, but defederation doesn’t make the fediverse or ActivityPub less free.
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.
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.
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.
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.
@juggles
Can’t say I’m great at it either. Honestly, platformer game type is a weird concept for Geometry dash, but I don’t mind it. The way different game modes are incorporated into it is really fun though
That’s because I’m not fully sure on how people should act in respect to this Threads situation (which is what got me thinking about all of this in the first place). In the recent past, I was all “defederate defederate defederate defederate,” but now considering that multiple large platforms (like Flipboard) will be joining in, it’s less likely that one company will control a majority of activity. Of course, you don’t need a majority for there to be a problem — just a large enough portion for other instances to have issues defederating due to the amount of content they’d lose — but a mere large portion and not a supermajority may not be reason to defederate. Of course, there are other things to consider as well, and I’ll probably make yet another wall of text with my new thoughts on how instances should handle this in the near future. For now, this thread is for me to share the ideals that I think people on the fediverse should prioritize and for others to discuss what they think on the matter.
Of course, these platforms have only federated a handful of accounts, so the “chaos” right now is in the reaction and discourse. However, I don’t think it’s unjustified.
I’ve outlined my main issues with Threads federation here, and while I’m not as sold on preemptive defederation as I was when I made the post, I still find it reasonable to be concerned about about for-profit companies controlling a vast majority of the content, especially when (A) the users making that content may be unaware that they’re on the fediverse to begin with and (B) companies like Meta have a terrible track record and would have incentive to grab a ton of users by defederating if they’re able (though with so many other parties joining in, whether they’ll be able to pull something off like that is becoming more questionable, hence me being less sure of the need to defederate).
Nah, just some teen making very inefficient use of his time
@rah Maybe I’m not being clear. When I say that “we” means “the fediverse in general”, I don’t mean that everyone should gather 'round and come to a consensus on what values they should uphold and who should be excluded. This is obviously something that should occur on an instance or individual level, as (A) there are a large variety of different people and instances on the fediverse with different priorities and (B) as you stated, anyone can implement ActivityPub and tap into the fediverse if they want to, regardless of what anyone else thinks.
What I mean is that people should be thinking about what they think instance owners should aim for and form their opinions on the current situation based on that. My goal with this post is to show what I think an “ideal fediverse” looks like and have others share their thoughts. Having thoughts about what’s healthy for people on the fediverse and having wants based on that isn’t misunderstanding the technology — it’s simply expressing preferences.
@rah I’d say the fediverse in general, particularly those on instances with microblogging (as they’re the ones affected by Threads, Flipboard, etc.). Obviously, everyone won’t have the same values, but I think it’s still important that everyone at least thinks about what they want the fediverse to grow into.
- 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.
3/3
- 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.
2/3
Why the fuck do people even follow the site any more.
Unfortunately, that’s where all the content is. Things like this don’t bother a lot of people — for example, discussion about YT videos wasn’t something I ever used Reddit for — and as long as Reddit is the only platform providing what they’re interested in, they’re going to stay.
Ah, I follow. Even so, I’d love to see Kbin grow as a platform for viewing, interacting with, and posting microblogs. I have gotten a ton of value out of the All Content view, and I think that more robust microblogging will make Kbin a much more attractive platform. Thus, I think it’s important to consider the impact (for better or for worse) of big contributors like Flipboard and Threads, even if most of the people on Kbin rn aren’t bothering with microblogs.
I’d disagree that they don’t matter at all. Even if you don’t, there are plenty of people who use the microblog side of Kbin and care about what’s in the microblog feed. Obviously, this doesn’t concern people who only use threads, but that’s not a reason to assert that we shouldn’t care.
the comments on the satirical tiktok are absolutely hilarious
Do you plan to do this with Firefox?
Yes and it will be named Poopenfartenfox.
You can’t help but appreciate the sheer amount of cognitive dissonance you gotta have to say, “God is perfect,” and “…for some reason He allows … bad things [to] happen.” How delusional can you be to say that raped children giving birth is part of some perfect, divine plan?
Social conservatism is a complete joke.