I assumed it was intentional.

Git is something that is very comfortable to use after a year or two, but when you initially start using it, it is just so easy to mess things up in ways that are unrecoverable. I remember the silly days when I’d back up all my changes first before using git since I would so regularly lose everything through a combination of git commands.

It’s easy for me now, but the initial stages punish mistakes severely. It’s the dark souls of source control, except it’s not really fun. It’s just a very beginner unfriendly tool.

Every instance just needs to store the communities they use, just like now. But once cached, any other instance could grab those messages from any of those instances. It’d be a peer to peer sort of organization.

I can think of lots of caveats regarding freshness of content and trust and ensuring the tree of instances is auto organized to minimize depth. Maybe for trust you could have signatures for all content signed using keys that every instance could pull from the original instance just once every now and then.

Upvotes and responses would just travel up the tree in the reverse trip from the way content came down.

But, I think it’s similar to other things that already exist. These problems seem solvable.

If it worked like torrenting where you have seeds, etc, it’d scale almost infinitely. I don’t think we should change to fit the algorithm. We should change the algorithm to make it scale.

Just checked. I haven’t played for a few months. Didn’t even know about update 8. Love that parachutes aren’t consumed on use now!

I can’t remember dust storms in that game. When do they happen? Or maybe they happen somewhere away from where I built my bases.

That’s obviously someone making a joking point about karma.

I did a bit of searching and the initial size you mention seems to be the initial size to which extrapolation is possible given information we have and that past that point it’s unknowable?

I think it’s a lemmy.world issue. Happens in Connect too.