There’s no real reason to. Your own instance (in this case, lemmy.world) has the real view of the thread by the virtue of being the instance starting the thread. lemmy.ml only has it’s own copy of this thread that’s likely reasonably accurate (compared to any other random instance out there, considering it hosts the community), but it’s not the original version, which is what the fediverse link points to.
Which instances did you try? I want to check if it was the background radiation of USpol inherent to most online communities you’re sick of (which there really isn’t a solution beyond keeping up with the newest buzzwords to add to your filters for from what I can tell) or the dot-social/kolektiva/twitter-like “my political happenings are too important for a content warning and must be boosted to everyone’s eyes 24/7” variety of USpol (which there is a ton of in Lemmy as well but i don’t think most people are ready for that debate yet)
The second one can be ameliorated a little by picking a smaller, sillier instance (hint: the weirder the domain, the better) and not following The Same Large Accounts Everyone Does.
In fact, I would advise against Mastodon the software altogether and instead point you towards instances of Akkoma or one of the not-Japanese Misskey forks such as Sharkey, Firefish, or Iceshrimp. The vibes of most instances I’ve seen seem to be cozier, and the Bubble timeline (called Recommended Timeline by some software) helps with discovering people to follow beyond the said Large Accounts.
The Pleroma family of ActivityPub servers are on Elixir and their bottleneck seems to be their awful database schema where everything is JSONB, and even then they’re known to be quite lightweight, so I assume with a proper DB schema it’d work quite well…
I would absolutely boost this to the microblog-verse if Lemmy federation with Misskey wasn’t broken
mastodon doesn’t “discover” akkoma content and won’t show anything unless you’re following a user from there, which kinda sucks.
I mean – that’s how all of them work. Even Lemmy. Unless your instance administrator joins relays (which have tradeoffs between privacy / effectiveness of blocking) your instance is only ever aware of posts from followed people (and reply threads followed people are involved in)
(also MUCH lighter on server resources, compared to most other twitter-like alternatives)
Mastodon is just unusually heavy, really. Even Misskey & forks are lighter than Masto on the server side (preferring being bloated on the client instead)
Mastodon feels like a fucking funeral.
You’re clearly nowhere near the good parts, then.
In my experience, once when you find your way into the correct circles the microblog-verse makes the “shitposting” of Lemmy look like r/memes. I do agree that discoverability could be better though, it took me 4-5 months before I got the hang of it. And now I barely check Lemmy despite my Lemmy account being older than my earliest microblog account (under this name, anyway).
One important thing is that your instance matters quite a bit more than here. Starting on a large general purpose instance (especially if it’s mastodon.social) and just following Large Accounts and Nobody Else like most people recommend for some reason is just setting yourself up for disappointment. Instead, get on a smaller interest-specific instance (rule of thumb: the weirder the domain the better your experience will be!) and follow the local timeline (and on good software, the bubble/recommended timelines). And post stuff/interact with people. Don’t be that one person that does nothing but boost news bots and occasionally butt into replies of people asking rhetorical questions they already know the answer for.
(Perhaps Lemmy is better at news or whatever, I wouldn’t know as I block all news communities I can find – I just don’t see the point as all the discussion around most news ends up predictable, unproductive (not that internet communities necessarily need to be “productive”), and unnecessarily angry)
Also in a world with usable™ Misskey forks and Akkoma I think the limitations of Mastodon the software are really starting to show, and I urge anyone who’s been disappointed in Mastodon to try other microblog software. (Quotes are already a thing if you know where to look! So are emoji reactions, because people have more emotions than :star:)
the 0.19 implementation is so half-assed I genuinely think the Lemmy devs just don’t want that functionality but expected quite a lot of backlash if they outright said as much, so they decided to implement something that ticks the box in the “wanted features” list without having any effect
afaik it only blocks communities and explicitly lets users from blocked instances through
(talking about microblog fedi here, Lemmy/threadiverse is it’s own thing)
don’t do hashtags. hashtags (especially common ones like #memes) are overrun by repost bots and low quality garbage.
the trick is to be on a small-to-medium instance you vibe with (1k active users seems to be the sweet spot. anything larger than 2k I’d avoid. do NOT join any flagship instances like mastodon.social), follow fun people from your local timeline, and see who they boost. and follow up the boost chain until your timeline is sufficiently fun.
the little eye in the top right corner can be used to toggle all of them in one go. this is such a massive qol improvement it’s genuinely baffling how mastodon and the 2 misskey forks I implemented it in are the only fedi software that have that button
I’m not entirely sure if such an instance exists, but just letting you know that in case you can’t find any, a reasonable compromise would be to join an instance that’s enforcing authorized fetch (and is blocking threads)
this will make it harder for facebook to read your data through federation alone (i.e. even if a post of yours get boosted by someone with followers from threads, it won’t “leak” there)
there are ways to bypass this of course but if facebook is found to do something of that sort they would out themselves as actively malicious which would definitely get a reaction even from the “wait and see” crew
if you were to focus this on just Lemmy itself as opposed to the wider fedi (“Especially given that there was just an update allowing for individuals to block instances they don’t like” implies that’s the case) you already have nothing to worry about as you encountering a threads user here will be even slimmer than encountering a mastodon user.
threads is primarily targeting the microblog/personal side of fedi. the incentives and privacy expectations are quite different compared to this side of fedi
re active users: they’re a large open registration instance, they likely have a fair chunk of twitter people who joined during one of the many migrations and decided not to stick around.
so, are you paying for it?
git commit -m $(date)
I’m mildly worried I know (as in, am aware of their existence, thankfully not having interacted with them) who you’re talking about
well I just checked and while “sync contacts” did not turn itself on, “allow contacts to add me” did. there’s definitely something going on
They aren’t forced to do anything. Manifest v3 is just a part of the WebExtensions API (which is not a standard and is really just “whatever Chrome does except we find/replace’d the word chrome to browser”) which both Safari and Firefox chose to implement in order to make porting of Chrome extensions easier.
Before that, Firefox had a much more powerful extension system that allowed extensions quite a lot of access to browser internals, but that turned out to be a maintenance nightmare so they walled those APIs off (not a coincidence that Firefox started getting massive performance improvements after that, and extensions stopped breaking every other release) and decided to go the WebExtensions route. I have no clue what Safari was up to but I think they implemented it after.
If they don’t implement Manifest v3, extensions that want to work across multiple browsers need to support both the older Manifest v2 and the later Manifest v3, which would be a burden not many extension authors would want to bother with, which would make them just say “yeah we’re not supporting anything outside Chrome”. Firefox avoids this problem by extending the v3 API to allow for the functionality necessary for powerful ad blocking Google removed in v3 (webRequestBlocking) while also implementing the new thing (declarativeNetRequest) side by side, so extensions that want to take advantage of the powerful features on Firefox can do so, while Chrome extensions that are fine with the less powerful alternative can still be ported over relatively easily.
Firefox does have it’s fair share of extensions on top of the WebExtension API already (sidebar support for one), so adding one more isn’t too big of a deal.
i’m pretty excited for fedify since i’m unsure if there has been any other activitypub abstraction that feels as comprehensive as it seems right now (from a brief skim, anyway).
one thing i had in mind ever since i first skimmed the docs some time ago is this:
i would really recommend you to NOT tell people to use handles here. i assume this is just naming and the framework doesn’t actually require a handle there, but documentation matters and if you follow on the footsteps of mastodon, pleroma, lemmy, and friends everyone who follows your docs will lose the ability to change usernames down the line without more pain than it’s worth (and yes, there are software out there that allow it right now! please do not build fedi software assuming usernames are immutable jsut because mastodon doesn’t let people do it)
just like how you wouldn’t use a natural key in a database, you should tell people to use a surrogate key like an autoincrement id or a uuid on the actor IDs, as they’re effectively permanent. while it may be probably fine for a quickstart thing like this to omit that, a lot of permanent codebases do start up by following these kinds of guides, and nudging people to do the correct thing when it’s not that hard is always a good idea IMO