rimu@piefed.social needs to stop developing so fast so the rest of us can catch up. That is all ๐
NodeBB too :blush:
Very few things in humanity are completely novel. We're iterative beings by nature.
Lots of businesses (not just decentralized FOSS stuff) is X but Y... just watch any episode of Dragon's Den or Shark Tank...
- It's Uber... for dogs!
- It's Hello Fresh... but flowers!
- It's Reddit... but decentralized!
Underrated comment.
Everyone's hilariously ragging on OP for setting up a federated instance with dubious uptime, and I'm sittin' here thinking that it just reminds me of me when I was a young kid hacking around with software.
Back then I set up a mediawiki server with very dubious uptime. Was fun ๐
Sure, although those terms are buzzwords only, not marketing speak. Like blogiverse, definitely not marketing.
The marketing term the Social Web Foundation wants to put forward is "Open Social Web", but that encompasses more than the threaded softwares (includes Mastodon, Peertube, etc.)
Threadiverse ftw
Hey suff@piefed.social let me share what I've been working on here at ActivityPub.Space
We're running NodeBB, which is a federated forum software that interacts with the threadiverse/forumverse natively, but also interacts with microblogs.
Anything coming from microblogs has no community attached, so we throw it all into a single "uncategorized" bucket.
This forum I am posting from is about ActivityPub, so I set up an auto-categorization rule so that posts using #ActivityPub get slotted into general โ sounds good, right? Except that tag has a fairly low SNR. Every day I have to remove 4 or 5 posts that are at most tangential to ActivityPub at all.
I ran into similar issues with #climbing for a rock climbing forum. People use #climbing when they climb rocks... but also trees, fences, buildings, etc...
So it can work, it just needs some ongoing curation. Essentially what I am trying to say is... hashtags are fine, but its usage is nowhere near consistent enough to use in a global context like you are saying.
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.
otter@lemmy.ca perhaps the quote posts are not related but some other changes bundled in that version release are?
Can you share the instance that user was on? It's worth checking out how their instance sees your post.
Mastodon did improve some non-Note handling characteristics, so it could be related!