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.
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.
@vkc Don't worry. In the near future, we'll be working on integrating with, among others, Peertube. For now, you can search for people from Peertube and follow their accounts, for example, "warroza@tube.pol.social." At some point, their content will start appearing in your feed ;) Enjoy.
