Apart from running it well and keeping up to date (recent update seems to have gone well, with a nice example of instances and admins helping each other!?), some redditers seek the big instances?? Curious how communities will adapt.
Secure a place in history. Create the source material for hundreds of journalists, bloggers and shitposters writing about the downfall of reddit and the rise of the threadiverse. (also missing!)...
I would risk a hot-take that Threadiverse today is where Fediverse was in April 2022: some infra exist, some long-established communities are there, and there is now sudden popular interest, stress-testing the network.
So, is it time now for "spread mastodon/fediverse" to adapt somewhat and spread the "#Threadiverse" (my moniker, fediverse for reddit-like platforms, eg #Lemmy and #kbin)
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 is a major downside to how federation works currently and something we shouldn't need extensions for, but as a stopgap solution I am glad they exist.
⚡ Fresher stats
⚡ New graphs
⚡ Top 20 lists updated more often
⚡ 14d server graphs
⚡ Server instance.json
⚡ Stats updated more often
⚡ Sus subdomain detection
⚡ Improved mobile layout
⚡ New favicon
Finally got an android phone to daily drive for a while. Wanna give some Material You love to #ArtemisApp. Checkout those colors and tab bar. Not just an iphone ripoff 😂 #android#kbin#Threadiverse
Believe the hype, y’all. @hariette and the team are building something special with @ArtemisApp. The alpha feels better than some finished products I’ve used recently. So much polish in every pixel of this thing. #artemis#threadiverse#RedditMigration#reddit
Defederation drama hits the #threadiverse, but with the twist of community/group dynamics being a major factor: see discussion with important links here: https://lemmy.ml/post/1281130
Here defederation is concerned with open signups (lemmy.world) and beehaw’s ability to moderate effectively, where they’re finding lemmy’s tools lacking, on which see this thread on an upcoming review: https://hachyderm.io/@thisismissem/110550824230711531 (@thisismissem).
TLDR: lemmy/kbin aren’t ready yet, need 6mnths-2yrs to mature
TLDR: Poor discoverability impedes the threadiverse's growth by making life hard for new users. Here are some suggestions on how discoverability could be improved....
You can be the one to create the kbin page on wikipedia (en.wikipedia.org)
Secure a place in history. Create the source material for hundreds of journalists, bloggers and shitposters writing about the downfall of reddit and the rise of the threadiverse. (also missing!)...
Missing search results when looking for federated communities (at Lemmy)
Hi all,...
OC Making threadiverse communities more discoverable - some suggestions
TLDR: Poor discoverability impedes the threadiverse's growth by making life hard for new users. Here are some suggestions on how discoverability could be improved....