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 understand the point you were trying to make. You're just wrong, in my opinion.
You are also focusing on the wrong software.
Mastodon, as the place most people start with ActivityPub software, absolutely should be able to view other types of content.
The important point is to not force anyone to view that content or display it particularly badly.
When all I know about Kbin is that it doesn't work with my Mastodon account, why exactly do I use it?
@ThatOneKirbyMain2568
@ernest
@tcely
I disagree. Yes, Mastodon is the first ActivityPub-based platform for most people, but that doesn't mean it's obligated to be an app for all social media on the fediverse. Most people go there for microblogging, not to see threads from Kbin or images from Pixelfed or videos from PeerTube. They just want a Twitter alternative, and Mastodon should provide that imo. If people already view the mere act of selecting an instance as enough of a barrier to prevent them from trying it out, you're going to lose more people if you complicate things by shoving YouTube-style or Reddit-style content into the platform.
This also makes me think that it wouldn't be very effective way of supporting other platforms. You're not going to get much engagement from Mastodonians on other types of content because those types are just not what they're there for. At best, you'll get people commenting on Lemmy threads thinking that they're microblog posts and thus not actually understanding the format of the thing they're replying to.
At best, it's an opportunity to organically introduce other types of content and the associated software to people through the social graph they chose to participate in.
If you did as you suggested, by adding posts / threads / communities / magazines without the consent of the users, that would indeed be a problem.
Preventing Mastodon users from seeing the content after they made the choice is also a problem.
@ThatOneKirbyMain2568
@ernest
@tcely
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.
As for selecting an instance, if that is a barrier, then forcing users to create and use multiple accounts in different ways to see all the content they want to is an even larger hurdle to present to users.
One of the biggest problems with Mastodon is new users who think they need an account on every instance website they interact with.
@ThatOneKirbyMain2568
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.