I've been thinking a bit about this post regarding #Mastodon's responsibility to be compatible with the #threadiverse (#ActivityPub thread aggregators like #Lemmy & #Kbin). Right now, a thread from Lemmy or Kbin usually federates to Mastodon with truncated text and a link to the actual thread. However, many want Mastodon to be more compatible with threads so that the people over on Mastodon interact with the threadiverse more.
I was initially in agreement as a Kbin user. But having given it some thought, I think this is an unwise approach that'll only serve to overcomplicate platforms on the #fediverse. Yes, people on Mastodon should promote other parts of the fediverse (and vice versa), but complete interoperability shouldn't be expected of every platform.
As much as many would like it, you can't have long-form video from PeerTube, images from Pixelfed, threads from Kbin, blogs from Writefreely, etc. all neatly fit in a microblog feed. These are different formats made for different platforms, and the people making them are expecting them to be interacted with in completely different ways. When someone makes a thread in a Lemmy community, they're probably expecting that the people who are going to see and interact with the thread are people that want to see threads and are thus on a Lemmy instance (or another thread aggregator). If someone from Mastodon were to interact with it as if it were a microblog post, there'd be a big mismatch. People interact with microblogs differently than they do with threads — that's why they're separate to begin with. You don't see everyone on Twitter also wanting to use to Reddit because people who want microblogs don't necessarily want Reddit-style threads, and vice versa.
The other option, then, is to separate these different formats into different feeds or otherwise make them clearly distinct from one another. Kbin does this by separating threads and microblog posts into two tabs. While you can view both in the "All Content" tab if you'd like, they're styled differently enough that it's very clear when you're looking at a thread and when you're looking at a microblog post. This distinction lets users treat threads like threads and microblog posts like microblog posts, which is really helpful since the two formats serve different purposes and have different audiences. This option — clear distinction — is a great way to solve the conundrum I've been talking about… if your platform is meant for viewing all these different kinds of content to begin with.
And that's what it really comes down to imo. Mastodon is a platform for microblogging. Most people go to Mastodon because they want a Twitter alternative, not a Twitter alternative that's also an Instagram alternative and a Reddit alternative and a YouTube alternative. Even if you put these different content types in separate tabs, it would inevitably make things seem more confusing and thus raise the barrier of entry. Add a Videos tab to Mastodon to view stuff on PeerTube, and people are inevitably going to go, "Wait, what's this? Is this like YouTube? I thought this was just a Twitter alternative! This all seems too complicated," even if you tell them to ignore it.
It's probably best to leave Mastodon as it is: a microblogging platform that has some limited federation with other formats. The way Kbin threads currently display on Mastodon is fine. In fact, when I post a Kbin thread, I'm expecting it to be viewed via a thread aggregator. If people on Mastodon were part of the target audience, I would've made a microblog post.
Now, if you want to make something that lets you view everything on the fediverse via different tabs, feel free. As aforementioned, Kbin supports both threads and microblogs, though it comes with some challenges (e.g., trying to fit magazine-less microblog posts into Kbin's magazine system). However, this doesn't mean every platform on the fediverse needs to seamlessly incorporate everything else. I'd love people on Mastodon to promote and even try out Lemmy & Kbin more, but that doesn't mean Mastodon needs to also become a thread aggregator.
This isn't a hurdle because people typically aren't going to the fediverse with the idea of "I want a single app for all my social media." That's not how social media works outside the fediverse, so it's not really going to be a surprise that the Twitter replacement is a Twitter replacement and not one for 5 other platforms. If someone really wants to view Reddit-style threads, they're straight up better of making an account on a different platform (just like they would make a different account for Reddit) because Mastodon is a microblogging site.
Even the best attempt to incorporate all these different types of content into Mastodon is going to further complicate the platform and make more people dismiss Mastodon as too complicated of a Twitter alternative. This isn't a situation where there's no harm at best. And the potential benefit? Lemmy comments having the occasional Mastodon user?
Mastodon itself is a good enough introduction to ActivityPub without needing to make it support other things. It shows how people on different servers can share & interact with a pool of media through the same protocol. When people learn about other platforms on the fediverse, they can go check those out. Just promoting the platforms will do the job fine without complicating people's entry into the fediverse.
Misskey, the fediverse microblogging platform that’s popular in Japan, has provided a recap of 2023, and it has been a big year for Misskey. The platform saw massive growth, the main server Misskey.io incorporated itself, and a number of new features and performance improvements.
The flagship server Misskey.io grew from 500 daily active users in January to 28k daily active users in December. They grew from around 20k registered accounts at the beginning of the year to over 400k accounts now. As with most social networks, growth happened in bursts, with a major increase in March and July, while the other months grew much slower.
With the growth came other changes as well: the server misskey.io incorporated itself, and main developer Syuilo became a director of the organisation as well. Donations and sponsorships also grew significantly. For the future, Syuilo says that “there are limits to relying solely on donations from everyone, so I would like to find a way to monetize the project.”
Misskey Pages allow users to create custom web pages on the platform that they can share. It can be programmed as well, and Misskey created a custom scripting language AiScript so people can safely add code to their Misskey Pages as well.
Other updates include refactoring of code and performance improvements, more information on that can be found here and here.
Misskey’s vision for fediverse servers is visible in their updates on moderation; every user can be assigned different roles that control permissions of the user in detail. In the update they say that this has greatly affected the operation of the Misskey server. This implies a vision for Misskey of larger servers, with a more complex structure for administration and moderation.
The future plans for Misskey focus heavily on the playful aspect of social communities: two games will be added that can be played on Misskey; Misskey Room as a way to play with other users in 3D space, as well as a chat interface. This puts Misskey further it’s unique place in the fediverse.
I strongly suggest that only stable builds be considered for usage in this flagship instance.
In case of Firefish, making the flagship instance a sandbox was not a good decision. Also, the major database update did not live up to the expectations as timelines still continue to feel buggier.
Though not dead, since Firefish is not fast enough in fixing issues that affect real users and real admins, I see that some Firefish instances are migrating to Sharkey or Iceshrimp.
Otherwise, for the most part, usage of Firefish has been a nice experience.
From a user perspective, both Sharkey and Iceshrimp have good prospects.
The latest beta of the Relatica mobile and desktop Friendica client, version 0.9.0, has just been released. Along with a slew of small bug fixes and tweaks this release now has a mechanism for viewing, filtering, and exporting the log events generated by the software. This will help users interact with developers (well me right now) in diagnosing problems on their system. This release also has the long requested feature of opening up tag searches on the user's home server not the remote server when they are clicked on. This is available for Apple and Google stores for those in the test program (ping me if you want access) and should have approval in the next 24 hours. Direct downloads for Android, Linux, and Windows are available from the install page. #relatica#friendica#fediverse My Social Portal / Relatica · GitLab
Another update to my #kbin userstyle idkbin (now at 1.2.6.1)! The "new comment" marker recently added by Ernest is now stylized by idkbin (mainly to work with rounded edges), and a bug with borders has been fixed. #kbinmeta#kbinstyles
I've noticed that a lot of people on the #fediverse aren't particularly welcoming to those who don't initially get it or have trouble with it. You'd think that if multiple people say they have trouble picking an instance, it might be a genuine barrier to entry that we need to consider when introducing them to the fediverse. But no, instead of suggesting an instance to get rid of that barrier everyone gives unhelpful advice like "just pick one" or "it's not that hard." We'd have a much easier time getting people on the fediverse if there weren't so many people with this attitude of "the fediverse is simple, and the people who don't get it are lazy and should try harder."
The issue is that there isn’t really anything more to choosing an instance than just picking one though, and we don’t want to funnel every new user to a single instance lest this end up becoming just reddit with extra steps. Or the reccomended instance gets flooded with more traffic than it can handle.
At most, a new user may want to look at what instances have defederated from the one they want to sign up on, but that’s a concept that isn’t going to make sense to someone who is already having trouble understanding “sign up somewhere, interact with everywhere” setup.
Numerous guides to all of this have been created. Rather than tilting at windmills (you will never stop people from being rude online, best to just accept it) your effort would be better spent being the friendly guiding hand. That’s far more effective than trying to call out people who probably don’t care whether we’re attracting more users or not.
@wizardbeard I'd argue that telling people to join largest (or at least a larger) instance isn't a bad thing. If I was telling someone to join Kbin, I'd tell them to just pick kbin.social. Later on, once they get accustomed to fediverse and understand the idea better, they can go to a smaller instance if they want
(e.g., if it's focused on a topic you like, it has features or moderation policies you prefer, or you just want to take some load off the larger instance). Having people initially go to larger, more established instances — where the experience tends to be more approachable due to more active hosts, more old content being federated, a larger community within the instance, etc. — greatly reduces the barrier to entry.
And the danger of a lot of people on a single instance is really exaggerated. If things go badly on, say, a Lemmy instance that most people are on, they can just move to another one with the same features, same UI, and similar access to content. It's not like Reddit or Twitter where moving means you're missing out on a ton.
You're right that it's usually better to be the change you want to see as opposed to simply criticizing others, but I think it's still important to discuss how we introduce people to the fediverse.
If you want to receive these updates during the week directly into your fediverse feed, you can follow me at @LaurensHof. The WordPress blog has been connected to the fediverse for a while now, but I'm starting to make more active use of it.
All of these shorter articles will also be boosted from this account to make things even easier, so they'll just show up in your microblogging client of choice.
I'm thinking I might stop using the term #fediverse#fedi or #activitypub when I want to talk about this community of federated social media services.
It's confusing and to be honest sounds way too much like a corporate brand trying to sell something.
I'm thinking I might start using something like "open internet" in general and "open social media" in particular to make the point that fedi isn't some specific thing; it's the default social media for the open internet.
I admit that it might be a bit of a "lies to children" (Pratchett et al), but it might be the first steps to carefully lead people away and towards a place where that brighter and wider future is visible.
I am using another term #Peopleverse, but not with intent for that to be a real name. More a vision for an online landscape that seamlessly aligns with our offline world and is in support of our daily lives.
Do I know anyone here who is willing to share their experience deploying an institutional Mastodon server? A contact of mine is looking for someone to discuss the experience as he works on getting a government agency to deploy their own instance. Boosts appreciated #fediverse#mastodon
