Administrative account for activitypub.space. Follow @[email protected] as well if you like :)
Do you have occasion to talk about the threadiverse to people who do not use threadiverse software?
I usually find the conversation is much more elementary (i.e. “what are open networks”, “what is the fediverse”) and I’d never get into discussions about what the subset of the fediverse known as the threadiverse, is.
[email protected] there’s nothing specifically precluding Lemmy and Piefed from following users.
You can follow users on NodeBB, and in fact because I did worked on Mastodon microblog interop first, the software only gained the ability to follow a category relatively recently.
So [email protected] has a point about it all being the fediverse, because some of what separates Lemmy/Piefed/mbin and Mastodon are artificial.
Eh we all have our opinions although I feel Threadiverse rolls off the tongue better than forumiverse (or foriverse which I also dislike.)
Also the term predates Threads by a full year, but I refuse to let the term die because of that association.
> is that an issue for the Threadiverse? I thought all replies are collected by the host instance of the community.
You’re not wrong about that. Threadiverse software (Lemmy, Piefed, and NodeBB too) use something called 1b12 to synchronize content between instances.
If you follow a community, you set up the synchronization from your server to that community from that point forwards.
This is similar, but not quite backfill, which is what happens if you follow a community mid-way and don’t have any of that stuff from before.
Also you can’t 1b12 synchronize with Mastodon, so that unfortunately is a dead-end, but you would hopefully be able to backfill from Mastodon.
Thanks for the link back, I appreciate it!
One neat side effect of this is that if the microblogiverse backfills from the threadiverse, and vice versa, then you have in effect built a bridge connecting the two disparate 'verses.
We’re not there yet — this step only exposes conversational contexts so that consumers (like NodeBB) can backfill from them. Neither Lemmy nor Piefed have signalled intent to consume contexts yet, but as it is a relatively new extension, there is no telling what may happen in a week, a month, a year… :)
Also [email protected] is pretty darn responsive and if you as (very) nicely that would go a long way.
Those are all very good questions, and exactly the sort of things that would be discussed at the ForumWG.
Backfill is just one of the things (the main thing, currently) we touch on, but one of the more important ones, because the potential to ensure you have the entire conversation is important from a data completeness standpoint.
The thing to remember is that there’s no one “owner” of a conversation. Right now it’s a pretty loose association… individual posts and notes can declare that they are part of a context, even if that isn’t the case. This beats the current system where there is no association at all.
The difference here is that as a consumer of backfill, I can actually go to the context and verify this. We can extend this later on with context ownership, and defer responsibilities like moderation, interaction policies, forking/merging, etc.
The long view of this is we intend to increasingly solidify the association between context and object over time.
Combining notification streams is precisely the mission statement of UnifiedPush.
Pinging [email protected] about this as this is his site I believe
The fact that you name dropped NodeBB (a good example), Flarum (which has no working federation), but did not mention Discourse (which has only partially working federation and limited threadiverse support) gives me the warm and fuzzies 🤣
Okay that’s fair.
I still think that shying away from the term would just be letting Meta win.
Might be we have to add qualifiers every time we say “threadiverse”…
Then again I suppose if you have to do that then that defeats the purpose doesn’t it,