First 6 months of marriage (first one, late 2010), we found an open wifi connection in our apartment complex and used that to our hearts content. This was when some people still didn't understand why securing your wifi was necessary.

Agreed. Graphene is a fantastic product, but the devs are absolutely insufferable.

And you'd be correct. I don't need or want any of that crap on my personal machine.

Another vote for FUTO keyboard.

Except, the swipe feature really likes to autocorrect to the most outlandish words that have never entered into my vocabulary at any point in my nearly 40 years on this godforsaken planet.

AI.

This is just a list of "but I'm not winning so it's not fairrrrrrrrrr" whining (whinging?)

"CRUD", "Sham" coin, and yesterday's date...

🤨

I think you might be misunderstanding here, Dockge doesn't really work like that. You don't import "into" Dockge - it works alongside Docker, and all you need to do is point it to where your compose files are located. Which, like I said, is normally set to /opt/stacks/ - but that's not set in stone and can be changed to another location via the DOCKGE_STACKS_DIR= env variable within Dockge's own compose file (located in /opt/dockge/).

For example: Say I create the directory /opt/stacks/docker_container/, drop in my "docker_container" compose.yml file, and fire it up in the terminal with docker compose up -d, all via CLI without touching Dockge at all. Dockge will still automatically see the compose file and the stack status. Or, say I have a previously-established Docker host with all the compose files in a location such as /home/username/docker_stacks/, and I really don't want to move them - so long as Dockge is configured to point at that directory, and the directory contains a labeled folder for each compose file (just like you would do normally), again, Dockge will automatically see the compose files and stack status. I've configured multiple hosts to use Dockge, and it's really that simple.

Also, something I just remembered - the directory structure for your compose files, wherever it's located, needs to be all lowercase. Otherwise Dockge won't see it.

Systemd is fine. This sounds like an old sysadmin who refuses to learn because "new thing bad" with zero logic to back it up.

Cinnamon by and far.

I've used so many distros and DEs I don't even know where to begin, but Cinnamon got me hooked for the long run. It's legitimately the most polished and "ready to run" DE I've ever used, yet still allowing for far more customization than Windows ever offered.

Does Lemmy have a "Thanks I'm cured" community yet?

Microsoft's requirements for Windows 11 include a 1GHz or faster CPU with at least two cores, 4GB of RAM, 64GB of storage,

All of this is no problem and essentially any computer manufactured in the last couple decades can meet these requirements. They're effectively irrelevant for this discussion.

IDK about you, but the Pentium 4 is not an ideal CPU for modern workloads. The absolute oldest hardware I would use today for anything is the Core2Duo with 8GB RAM. I know this because we have an A1276 MacBook Pro with the P8600 C2D, and it's barely sufficient. You look at it and the cooling fan begins a launch sequence 😅 and that's running Linux Mint. Windows 10/11 would grind it to a halt trying to run multiple tasks.

I have a childhood friend who was very recently diagnosed with autism. We talked a little while ago and he brought it up. My first thought was "ah, yep, that explains a lot".

He's still a great friend. It didn't change anything about him, rather it helped make sense of his behaviors that we all just saw as "that's just how [friend] is".