Because Twitter replacement only works if it gets critical mass and Mastadon is not going to win that fight. You’re never going to see cities switch to putting notices on mastadon, but you might see them end up on Threads.
I wouldn’t say “never”. I’d say decentralised social media grows more slowly but it’s only a matter of time before threads does its own enshittification and there’s another mass exodus to Mastodon. Sites that don’t do enshittification because they aren’t centralised and corporate won’t have that kind of exodus, and will grow over time.
If they become so ubiquitous that they’re the de facto standard, then cities will put their notices on them. You’ll probably get official civic instances for notices, maybe hosted on their regular website domains.
I mean unless corporate social media finds some other way to subvert activitypub that’s more effective than “look at me I have money for developers and advertising”, then I don’t see this trend changing. Corporate platforms don’t seem capable of learning anything from their repeated failures, which is really strange. I think it happens because their hierarchies are inherently insulated against learning anything.
Marketing. The reason it's called a hype train is because everyone wants to get hitched to an engine that's already moving forward. Threads hit the ground running because Meta files it with money. Mastadon is a slow moving beast.
1 part 'Meta users 'already have' an account so getting into it is easy', mixed with 1 part 'The slightest possibility of inconvenience (like having to choose a Mastodon server) acts as a deterrent to most people when alternative means are available'.
Mate I think people are just kinda lazy and don't really care that much about privacy relative to ease of use and the presence of people they're interested in.
@BraveSirZaphod In that case, both of your hunches are right, no matter the Curb-Stomp Battle we indeed are facing in the name of the Internet's future path.
“Firefish is a hot new microblogging platform”: it’s not that “new” at all, #Calckey, which has been around since 2021, has only recently changed its name to Firefish
the antennas / news picker had apparently not yet been fully understood by the author: they do not fill retroactively and it is a full-text search that also finds parts of words. Therefore, if it doesn’t fit, search words can be excluded - it works very well for me! If you use it for a little longer instead of just taking a quick look, you can use it to structure your content very well.
“Lack of an official app is kind of disappointing”: “official” apps are perhaps important as a “brand” for some, the so-called “Mastodon” app is also the worst app ever for Mastodon (fortunately with many better alternatives). The PWA for Firefish works great on all devices, if you don’t want to miss out on any features and want the best look, you don’t need an app.
The biggest hindrance at the moment right now is the flagship instance at firefish.social:" The instance has clearly communicated that it primarily serves as a test instance, i.e. it does not strive for or want to guarantee stability. In contrast to mastodon.social, Firefish itself also makes clearer reference to the selection and there are now really many Firefish instances.
For me, the biggest disadvantage of Firefish at the moment is that it doesn’t yet federate properly with Lemmy.
kbin.social's admin (and kbin currently only supports one admin per instance) is also the main dev.
As I understand it, the sudden unexpected popularity of kbin caused infrastructure issues and made fixing bugs and limitations more important, while he still has to reach his feature goals to secure funding so he can actually continue working on kbin full-time. Additionally, real life had a lot of negative surprises in store he had to deal with.
All in all, he hasn't had much time at all to properly moderate the instance, And the past two weeks he's been gone entirely for real life reasons, leaving the instance unmoderated.
It's not an issue with the software itself, just with kbin.social (and of course other badly moderated instances) specifically.
just with kbin.social (and of course other badly moderated instances) specifically.
Yes, there’s clearly a moderation problem, but it’s not just kbin.social.
To rephrase the question: why is it that practically all the insufficiently moderated sites are kbin instances?
kbin currently only supports one admin per instance
An overwhelmed admin could partially explain why a lot of spam comes from a particular instance. But it wouldn’t explain why most of the small instances generating spam have chosen kbin instead of lemmy.
the main problem for non-kbin users, as @ono is using lemmy, is that kbin moderation actions, such as a moderator or admin removing spam will not federate to lemmy, as this is not implemented yet.
for a lemmy user, it appears that kbin doesn’t have any moderation at all, while spam is being removed for kbin(.social) users at least.
for this reason, several lemmy instances have already either defederated from kbin or removed kbin communities from their instance.
@donuts Kbin and Lemmy support is a little bit janky at the moment, it's also kind of easier to view this from the microblogging / social side of the Fediverse.
fediverse
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.