ThatOneKirbyMain2568
@ThatOneKirbyMain2568@kbin.social
- Comment on Prove it wrong: the fediverse is not as connected as we're told, and it's splintering even more now. 10 months ago:
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!
- Comment on Prove it wrong: the fediverse is not as connected as we're told, and it's splintering even more now. 10 months ago:
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).
-
- Comment on xkcd #2878: Supernova 10 months ago:
Explanation for anyone who wants it: https://explainxkcd.com/wiki/index.php/2878:_Supernova
- Comment on [deleted] 10 months ago:
They've been mostly resolved in my experience. Kbin.social has been working great.
- Comment on [deleted] 10 months ago:
@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!
- Comment on The free fediverses should emphasize networked communities 10 months ago:
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.
- Comment on A take on an "ideal" fediverse 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.
- Comment on A take on an "ideal" fediverse 11 months ago:
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.
- Comment on A take on an "ideal" fediverse 11 months ago:
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).
- Comment on A take on an "ideal" fediverse 11 months ago:
Nah, just some teen making very inefficient use of his time
- Submitted 11 months ago to fediverse@lemmy.world | 28 comments
- Submitted 11 months ago to fediverse@lemmy.world | 0 comments
- Submitted 11 months ago to fediverse@lemmy.world | 0 comments
- Submitted 11 months ago to fediverse@lemmy.world | 0 comments
- Comment on Challenge accepted 11 months ago:
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
- Comment on Challenge accepted 11 months ago:
The names are an edit from the original xkcd comic, where the states are blank.
- Comment on Challenge accepted 11 months ago:
Many residents of Kentessee would love to change the name to Elevennessee, but that's been found extremely exclusive by the former Kentucky residents who were lumped into the state upon its creation.
- Comment on Challenge accepted 11 months ago:
Oooo, you're right. I originally had (north–south) Washington → Columbia → Oregon but then realized that Oregon's shape was second and so lazily swapped the two names. Cool to know!
- Comment on Challenge accepted 11 months ago:
That's the other part of Michigan, unless the Upper Peninsula decided to become Upper Dakota while I wasn't looking.
- Comment on Challenge accepted 11 months ago:
It's just a fancy name for "Dakota[citation needed]".
- Submitted 11 months ago to xkcd@lemmy.world | 107 comments
- Submitted 11 months ago to newcommunities@lemmy.world | 0 comments
- Comment on xkcd #2864: Compact Graphs 11 months ago:
Massive waste of space. Should've used a smaller font size.
- Comment on xkcd #2862: Typical Seating Chart 11 months ago:
Lots of wasted space on the tail. Could've fit a ball pit or two back there.
- Comment on xkxd #2860: Decay Modes 11 months ago:
What do you mean? They're all completely real
- Comment on YouTube warns it might make your viewing experience worse if you don't turn off your ad-blocker 11 months ago:
Well, looks like I'll just stick to using Invidious.
- Submitted 11 months ago to newcommunities@lemmy.world | 0 comments
- Kurzgesagt — An unofficial community for discussing Kurzgesagt's videos on space, biology, philosophy, etc.kbin.social ↗Submitted 11 months ago to newcommunities@lemmy.world | 26 comments
