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.
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…
this is what happens when lemmy tries to handle microblog content not specifically tailored to it’s exact quirks
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
…and I thought of a web game you can make with this, if anyone’s bored and looking for something to do: https://brain.d.on-t.work/notes/9on0iba4evg40hic
- pick a random page
- find all pages nearby
- make the player guess the random page from the nearby pages
- if they haven’t guessed the exact page, compare the coordinates and score based on distance to the correct page
I have just been informed you can also see pages nearby other pages with a special URL query (apparently no interface exists for this yet)
yeah same here unfortunately. but then I am currently somewhere I’d consider middle of nowhere
actually there was one plane crash but that’s not necessarily an article I’m interested in
(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
considering most Minecraft mods directly mess with the Minecraft code as opposed to going through a well defined API (forge and fabric only provide so much) you can’t really make that work without outright stealing Minecraft code
the best you can make would be resourcepack and datapack compatibility. maybe whatever molang stuff bedrock’s up to
so, are you paying for it?
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
.world is a newer gTLD whereas .ml is a more well known country code TLD. whatever auto linking code the lemmy UI uses likely just isn’t up to date with all these comparatively recent TLDs
I’m just saying the “steamlib proxy” concept you mentioned is not only possible but has at least one implementation. The fact that Wine isn’t true isolation doesn’t really change anything (maybe other than the exact details of the underlying IPC channel, which could use some kind of optimized shared memory magic) unless I’m misunderstanding something.
Some games will probably actually rely on Steam, like for achievements or something. For those…If there are a substantial number of Mac games that won’t work in a 64-bit environment, I am wondering if it is possible to make a “steamlib proxy” – basically, have a 32-Mac VM, run the game in a VM, but have Steam running in a 64-bit host environment, and just relay calls to a process launched under the host environment that uses the host steamlib to talk to Steam. Valve presumably isn’t gonna set that up as a supported environment, but I wonder if that might be a viable open-source project.
I think Proton has something of that nature, so games running inside Wine talk to the native Linux Steam binary.
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