It’s the next evolution of planned obsolescence - it just doesn’t work as soon as you start to use it.

A lot of those issues of ‘multiple primaries’ can be resolved with intelligent data types and actions. That is, if we have a notion of how the data is organized, a lot of decisions can be made a priori. Ones that can’t can be read-only during a split.

Comment groups are mergeable sets. Any unique comment is a valid comment.

For any individual comment, any tombstone causes a comment to be unseeable (and ideally be deleted). Any edits are latest-wins.

A lot can be sorted out that way - enough to be usable. Some databases even support that on a db level.

If you do try Linux:

• buy hardware that’s supported. For some things (storage) virtually everything works. For others, (video cards, latest-gen wifi) you need to make sure it’s supported out-of-the-box. It’s not worth the headache of trying to get it to work unless you just like geeking out.
• if some piece if software or hardware doesn’t work, it doesn’t work. If you spend more than a half hour (or whatever your limit is) trying to get it to work, just say to yourself ‘not available on Linux right now’ and move on. Linix has way more access to beta and alpha-level stuff, and that can make it tempting to try to fix whatever problem. Just don’t bother.

That said, most of the systems I use Linux on, it just works.

Meh. Most of the top comments are pretty reasonable.

fwiw, I’m now pretty darn happy with Linux and gaming. Granted, I use Steam, so there’s that.

There are issues sometimes, but I just keep a copy of windows around for windows-only things. Generally, Linux “just works” for me, but I’ve also learned to just skip it when something requires too much involvement to get working.

I think this might be interesting:

• permit separate, low-traffic, highly rate-limited, auth-only servers. They would be strictly rate-limited and only accept connections from whitelisted partner servers, because they only handle auth.
• any partner server can authenticate a user and handle content for the server/auth-server pair, but only does so under certain conditions (determined by the partner - all the time, when ping api call > n seconds, or manually, for example)
• user@lemmy.world can’t log in, so the client tries the list of partnered servers. user succeeds at lemmy.partner.net.
• user@lemmy.world@partner.net says… ‘…something’ and all other servers accept it as being from user@lemmy.world
• lemmy.world recovers, and claims all of the @lemmy.world@partner.net posts. Partners then forget the extra stuff they’ve been hosting.

Be careful not to cross that line of request vs desperation.

Like on YouTube - A tasteful “don’t forget to like and subscribe” is fine, but mentioning it multiple times during a video is just increasingly demanding or cringe.

Proper instruction.

Likewise.

Is liftoff homegrown?

Stellaris. Extremely long games, a lot to learn… …and they change it. Mechanics that worked before stop working. The bad parts are added to same become a DLC, the good parts disappear or are algal paved in DLC. Overall, it just doesn’t feel worth it.

I use xonsh, which has decent history - start your command, and up arrow cycles through commands stating with what you typed.

There’s good stuff and bad stuff about xonsh.

It’s still a self-replicating thought. …although the meaning has gotten broader in some areas, narrower in others, and much shallower overall.