moonpiedumplings

When on God's green earth would someone want to delete the partition table and not immediately create a new partition?

counterpoint: https://wiki.archlinux.org/title/Btrfs#Partitionless_Btrfs_disk

Btrfs can occupy an entire data storage device, replacing the MBR or GPT partitioning schemes,

I really like this take on it: https://forgejo.org/docs/latest/user/actions/github-actions/#familiarity-instead-of-compatibility

For all of these reasons, Forgejo Actions strives for familiarity instead of compatibility. We want users of GitHub actions to feel familiar using Forgejo Actions, even if there are some small changes here and there. Workflows should work with some minimal changes.

I think the same thing applies to Linux DE's. Linux is not and never will be a 1 for 1 to windows workflows. If we chase perfect compatibility, we will be perpetually behind on a wild goose chase.

But, doing things like what KDE does, where most of the common keyboard shortcuts are the same, and things like virtual desktops allow for similar workflows with very little adaptation, is very reasonable.

The chess com engine analysis sucks. It's too focused on glazing you and not enough on being honest. It certainly feels better than the lichess engine, but it doesn't actually share more information.

For example, it used to be that a "brilliant move" was any move that you spotted but that the engine didn't. But now, it's been changed so that any sacrifice is a "brilliant move".

Further, the LLM based analysis is also pretty bad. It only seems to explain moves, but like most LLM's, it actually hallucinates and recommends nonsensical stuff, or incorrectly makes other claims about the position. If you search on r/chess you can find plenty of examples of this:

• https://www.reddit.com/r/Chesscom/comments/1p7n8js/can_something_new_explain_why_chesscom_ai_thinks/
• https://www.reddit.com/r/chessbeginners/comments/1ko6snm/is_chesscom_ai_useless/
• https://www.reddit.com/r/Chesscom/comments/1o2j3rg/is_the_ai_text_in_the_game_analysis_just_plainly/

etc etc.

As an alternative, if you really want that type of UI, you can also use Lichess' server based engine analysis (you get 40 free per day unlike chess com's paid stuff):

But it doesn't tell you why a move is bad. If you really want to learn why a move is bad, the local analysis lets you play your moves against stockfish and experiment and see why they are lacking.

Just learn to use the Lichess local analysis. It's designed to actually facilitate improvement instead of glazing users and getting them to keep paying.

Switch to lichess.org (open source, has all of chess com's paid features available for free, plus no ads or trackers).

Start with the chess basics set: https://lichess.org/learn

Then the basic tactics set: https://lichess.org/practice

And then do puzzles: https://lichess.org/training (chess com makes you pay for more than a few per day). Do a lot of them.

Then, you can also analyze your games on lichess using it's analysis engines (which chess com makes you pay for). Uh I can't find a good guide how to do this right now, check back later.

Unfortunately, the browser extension is proprietary. They used to have an open source one but they stopped maintaining it.

Proprietary was a dealbreaker for me. There is no way to verify that it isn't selling everything I type even if I do have it configured to point at a local server.

I'm also concerned that the extension may eventually no longer work against local servers as well.

https://github.com/languagetool-org/languagetool-browser-addon/issues/247

As an alternative, there is harper by wordpress: https://github.com/Automattic/harper

It is webassembly and runs entirely in your browser.

EDIT:

I will add that the rest of the languagetool ecosystem continues to work fine. Libreoffice now has a built in client, which you can point at your own hosted server. VSCode [1] also has their own languagetool extension. I use those and those work great. But in the browser I use ~~harper~~ nothing. I should probably install harper.

[1] Well, technically I use [code-oss]https://wiki.archlinux.org/title/Visual_Studio_Code), which gets the extension from https://open-vsx.org/

On kubernetes it's pretty much the same amount of work. Every possible storage option exposes a generalized, abstracted "storageclass", from which storage can be provisioned and mounted into containers.

https://kubernetes.io/docs/concepts/storage/storage-classes/

Well, I run a one node cluster...

But yes, I did use ceph via rook-ceph, because Openstack (a locally hosted AWS alternative), at least the Kubernetes version, wanted a ceph "cluster" to store stuff on.

Longhorn is much easier. Although again, my "cluster" was one node. I deployed it because I wanted snapshots.

I like to use more uncommon tools (it often bites me afterward but it’s funnier this way

I know the feeling.

How about this: https://docs.xcp-ng.org/installation/install-xcp-ng/#9-networking

Try setting a static ip address on xcp-ng itself, during the install phase. (this was how devices got onto networks before dhcp). You'll have to make sure it doesn't conflict with anything else on the network.

Kubernetes makes distributed storage easy.

Basically, all the components get deployed for you, since that's part of what kubernetes is good at.

And then, services/containers can provision storage by requesting storage via making a "claim" and whatever distributed storage providee you have gives it to you.

https://sso.tax/

It's unfortunately common, even though it probably shouldn't be.

They don't have to support it. It's more that the database they are connecting to supports HA, and/or both are using shared storage. So when one container dies, kubernetes restarts another container on another node with the same shared storage attached.

Docker is often configured to automatically restart containers when a container dies, just in case it's a one off bug or something like that, and kubernetes is like a more resilient version of that.

You can do oidc with the proxmox ui itself.

I use oidc with Incus, which is a fork of lxd and a similar software to proxmox, it can run vm's and lxd containers.