Given Thread itself is more akin to Twitter, so Threadiverse would rather be thr Mastodon style microblogging rather than the community-oriented approach of Lemmy/Piefed/mbin/kbin.
The Threadiverse is not named after Threads by Meta Platforms, Inc. The term “Threadiverse” is older than Threads by Meta Platforms, Inc.
It is named after Lemmy’s and /kbin’s and Mbin’s and PieFed’s “killer feature” of enclosed threaded conversations, with exactly one post followed any number of comments, where everyone always receives all of the comments. Something that was (and often still is) considered exclusive to these four applications.
In stark contrast to the de-facto Fediverse default, Mastodon. Where everything in a thread is a post. Where the concept of comments doesn’t exist. Where conversations are a filthy hack because it’s social media, and replies to replies aren’t part of the concept.
Where timelines always only consist of single posts with seemingly no context, and only a small variation in a small icon tells you that there is a context in the first place. Where seeing even only the branch of a conversation that any given post is in takes some effort, and seeing the whole conversation with all branches takes even more effort, not to mention the knowledge that this can be done in the first place, much less how it can be done.
Where you have to be mentioned to know that someone has replied to you. Like, where I would have to mention everyone in this branch of this conversation (@fonix232@fedia.io@speedythefirst@lemmy.zip@OpenStars@discuss.online@ceiphas@feddit.org) so that even only they receive my reply (everyone else in the conversation doesn’t). Where whoever will reply to me will automatically mention these four participants plus me.
The “Thread” in “Threadiverse” doesn’t stand for Meta Threads. It stands for “we can do proper threads, as in enclosed threaded conversations, something that Mastodon can’t, something that most Mastodon users believe the whole Fediverse can’t!”
I think nodeBB also is included as part of the Threadiverse, although it seems not a full-fledged member, and I am not well-versed enough to know why (perhaps connection via the ActivityPub Protocol is still being rolled out to all the instances?).
Meta’s Threads is indeed entirely irrelevant to any of this, except that they wanted to horn in on our fun, but they killed themselves before they could begin, though not before we had already preemptively blocked it all! 🤣
Oh, and also they stole our name. Or rather tried to, but fuck that noise - we took it right back!!
Ah, thank you for sharing your experience there. So it’s possible but difficult, like Mastodon (where behavior is also inconsistent) - good to know! I should probably stop listing nodeBB as a major player in the Threadiverse then.
Technically speaking, Friendica, Hubzilla, (streams) and Forte ought to be parts of the Threadiverse, too. They’ve always had enclosed threaded conversations and even discussion groups built in. Except for Friendica, they support FEP-171b “Conversation Containers”.
But look at how few people on Lemmy have even only heard of Mastodon. Friendica is much more unknown there. Those who know Hubzilla are a subset of those who know Friendica. And (streams) and Forte are next to completely unknown beyond Hubzilla’s actual users.
Tbf if you are interested in topics rather than people, then Mastodon is simply inferior to the Threadiverse - as you gave the best description I’ve ever seen on that point.
Friendica is inferior as well, but more on the technical side. It is struggling and instances shutting down due to lack of stability and efficiency, with costs rising far too high along with number of users. They’ve put out calls for programming aid to help fix those issues. As a non-user, I thought their main focus was on people rather than topics of conversation though?
The Threadiverse has quite the reputation for having such solid products - whether written in Rust with custom front-end or in Python with flask front-end (and Postgresql back-end), or Mbin is in PHP, and nodeBB uses Node.js.
People have been using Threadiverse to refer to the link-aggregating community based Fediverse platforms with threaded discussion topics for way longer than Threads has existed as a website.
If you can come up with a catchier alternative then go for it. Link-aggregator-verse doesn’t really roll off the tongue.
But that isn’t really Threadiverse now, is it?
Given Thread itself is more akin to Twitter, so Threadiverse would rather be thr Mastodon style microblogging rather than the community-oriented approach of Lemmy/Piefed/mbin/kbin.
The Threadiverse is not named after Threads by Meta Platforms, Inc. The term “Threadiverse” is older than Threads by Meta Platforms, Inc.
It is named after Lemmy’s and /kbin’s and Mbin’s and PieFed’s “killer feature” of enclosed threaded conversations, with exactly one post followed any number of comments, where everyone always receives all of the comments. Something that was (and often still is) considered exclusive to these four applications.
In stark contrast to the de-facto Fediverse default, Mastodon. Where everything in a thread is a post. Where the concept of comments doesn’t exist. Where conversations are a filthy hack because it’s social media, and replies to replies aren’t part of the concept.
Where timelines always only consist of single posts with seemingly no context, and only a small variation in a small icon tells you that there is a context in the first place. Where seeing even only the branch of a conversation that any given post is in takes some effort, and seeing the whole conversation with all branches takes even more effort, not to mention the knowledge that this can be done in the first place, much less how it can be done.
Where you have to be mentioned to know that someone has replied to you. Like, where I would have to mention everyone in this branch of this conversation (@fonix232@fedia.io @speedythefirst@lemmy.zip @OpenStars@discuss.online @ceiphas@feddit.org) so that even only they receive my reply (everyone else in the conversation doesn’t). Where whoever will reply to me will automatically mention these four participants plus me.
The “Thread” in “Threadiverse” doesn’t stand for Meta Threads. It stands for “we can do proper threads, as in enclosed threaded conversations, something that Mastodon can’t, something that most Mastodon users believe the whole Fediverse can’t!”
I know it isn’t named after Threads, but your average person won’t. Especially when you capitalise it so it’s Threadiverse instead of threadiverse.
Well said.
I think nodeBB also is included as part of the Threadiverse, although it seems not a full-fledged member, and I am not well-versed enough to know why (perhaps connection via the ActivityPub Protocol is still being rolled out to all the instances?).
Meta’s Threads is indeed entirely irrelevant to any of this, except that they wanted to horn in on our fun, but they killed themselves before they could begin, though not before we had already preemptively blocked it all! 🤣
Oh, and also they stole our name. Or rather tried to, but fuck that noise - we took it right back!!
Having attempted to use Lemmy communities via NodeBB, it’s a pain. No surprise we rarely see posts or comments from NodeBB users.
Ah, thank you for sharing your experience there. So it’s possible but difficult, like Mastodon (where behavior is also inconsistent) - good to know! I should probably stop listing nodeBB as a major player in the Threadiverse then.
The inverse (using Lemmy to follow NodeBB boards) seems to work fine, but I haven’t been able to find any that interest me
Oh neat! Or… I guess not, as you said 🤣 - either way it’s good to know! 😉
Technically speaking, Friendica, Hubzilla, (streams) and Forte ought to be parts of the Threadiverse, too. They’ve always had enclosed threaded conversations and even discussion groups built in. Except for Friendica, they support FEP-171b “Conversation Containers”.
But look at how few people on Lemmy have even only heard of Mastodon. Friendica is much more unknown there. Those who know Hubzilla are a subset of those who know Friendica. And (streams) and Forte are next to completely unknown beyond Hubzilla’s actual users.
Tbf if you are interested in topics rather than people, then Mastodon is simply inferior to the Threadiverse - as you gave the best description I’ve ever seen on that point.
Friendica is inferior as well, but more on the technical side. It is struggling and instances shutting down due to lack of stability and efficiency, with costs rising far too high along with number of users. They’ve put out calls for programming aid to help fix those issues. As a non-user, I thought their main focus was on people rather than topics of conversation though?
The Threadiverse has quite the reputation for having such solid products - whether written in Rust with custom front-end or in Python with flask front-end (and Postgresql back-end), or Mbin is in PHP, and nodeBB uses Node.js.
It literally is called the Threadiverse. The terminology predates Threads as a platform.
People have been using Threadiverse to refer to the link-aggregating community based Fediverse platforms with threaded discussion topics for way longer than Threads has existed as a website.
If you can come up with a catchier alternative then go for it. Link-aggregator-verse doesn’t really roll off the tongue.
Feddiverse?
its also reductionist. its not like we are just hoarding links here for hoarding’s sake. discussions. and many non-link posts too.