Lemmy is an open, federated platform. You cannot realistically hide who voted, because there is no trusted server that would secretly count up votes and provide a total.

They probably already set it up to not happen in Europe

Oh screw that, that's an emotional post from somebody sharing their reaction, and I'm fucking STOKED to hear about it, can't believe I missed the news!

I don't think that's a good point, since they make their own immutable images, so they can use whatever versions of software they want, and you don't normally get to update them with the rolling release

Yes, do as I say!

By the way, for editing server files consider nano. It's also widely available, has simpler shortcuts and displays them on the screen. It's obviously not powerful like vim, but a good match when you just need to edit a config file.

You need to beat the level to upload it, and I suspect it's a clear check upload - however, separately, the game tracks first clear and world record after a level is uploaded.

My understanding is that the goal is to clear every beatable level that doesn't have a first clear (and some that have been cleared by known hackers, but I think those are all cleared legitimately already)

Terraria is a truly extreme case, the developers truly just can't stop making updates.

Factorio isn't amazing in this way, but the developers have a lot of integrity - they delivered their plans for 1.0, released some good extra updates, continue fixing bugs, and went to work developing paid DLC. I do suppose the DLC will come with a major update to the base game, but that's also because they found they needed to make changes and additions for the expansion.

Isn't that clickhole? AFAIK NotTheOnion is for non-satirical media reporting real news that sound like they came straight from the onion.

Sounds like what you want basically is not Lemmy.

It also raises some pretty big issues, like who gets to moderate communities? Right now you make a community on a specific instance, you follow that instance's rules, so the instance host has authority over the community. If you disagree with the instance's rules, or with the way the community is ran, you can make a community on another instance, or even make your own instance with your own rules.

And from the other side, there need to be people with the authority to remove communities, and remove people/posts across different communities. Right now that's the responsibility of the instance hosts, to my understanding - content is hosted on a primary instance, and stored through federating instances, so the primary instance has a responsibility to keep it clean of illegal material. Who would have this power and responsibility if instances aren't differentiated? Sounds like the best case is giving trustworthy people an excessive amount of power, and the worst case is the entire network being shut down due to distributing illegal content and being effectively impossible to moderate.

You also didn't address the issue of passwords - currently it's a pretty big deal when hashed+salted passwords leak, considering those passwords compromised... The comparison with AWS is flawed - when using AWS, you're trusting them, because it's a big company with a reputation to keep. The situation seems very different when it's random enthusiasts with highly differing views, and without a central authority to verify them (though there are probably too many to verify anyways)

And you propose that anybody can join the network and receive users' passwords? On top of that, you're proposing that you need to also know the "server" your data is stored on and supply that with logging in? Sounds like a really annoying friction point for the user.

I really feel like you're approaching this from the wrong direction, suggesting Lemmy should abolish the very structure it's built on for one you'd like more, but I think it could be possible to make the experience nicer without going to those extremes.

Maybe it'd be possible to let multiple instances have authority over an account, without changing its home instance, so that if your original instance goes down, you can keep the same account. And to reduce friction from communities being made across multiple instances, some way for communities themselves to federate/combine would be nice, and is probably being considered by people smarter than me.

I don't think that'd work, with Lemmy being a federated model, not a fully decentralized one.

How do you handle the actual login? Does that mean every server has access to your password hash? Or do you overhaul the account system to use something like a private and public key, with the user needing to store and transfer the private key to every device they use?

And what happens if two people register with the same username on two instances that aren't federating? Do they somehow need to still communicate with all other instances in the network they operate in, to prevent that from happening? Because the alternative I see is the login being random in some way or tied to the instance, in which case you still lose the impression of a single service.

If I'm not mistaken, right now anybody could host a non-federating Lemmy instance, if they just wanted a small private community in this style. To my understanding, that's the idea behind federation, and a founding concept of Lemmy - it's not a giant service distributed across trusted servers, but a network of smaller communities that communicate with limited trust.

It is pretty well optimized. I think it might not be, like, genius-level amazing, but the devs care about performance and worked to improve it.

In the end though, it's a game where the entire map (as generated so far) is simulated - I think there's cases where chunks go to sleep, but it's not Minecraft's "stop simulating anything not next to a player". When combined with players building lots of machines moving many, many items around, you'll inevitably end up with some serious CPU usage. Not a problem on a decent computer, but I have had friends struggle on weak laptops, even getting dropped as they literally couldn't keep up with the server.