Knots and construction with poles and rope lashing was always my favourite part of scouts. The sketches of the knot looks cool on the surface but don't tell me much about how they are tied or what other lashings they are similar to. Not much detail and the second image has three running ends?
Much less data to back up so it can be stored in a way that is replicated for redundancy but still mutable. Separating the key and data is what allows for sending data to tape backup etc
The specifics of how the keys are backed against different failure modes/attacks is orthogonal to the splitting of data/key.
Yes you would need to carefully design the system that allows deletion of keys while minimizing chances of data loss, but it can be done, and it's going to be cheaper and less complex to do so on a tiny subset of the data.
Latency considerations are also down to design, it's not a given that there will be significant overhead imposed.
One simple way is to keep only a few days / weeks of (immutable) keys backups.
You can always stop the deletion of you have a big issue.
If the law says you have 14 days to delete all data, you keep only that much backups.
I wanted to try something different when I reset my self host set up several years ago, and went with openSUSE MicroOS. Ultimately it has led to podman containers running under systemd/quadlet and I'm quite happy with the current set up.
Containers auto update with built in podman tooling, getting at logs and monitoring is through the usual systemd tools. When I need to change something, it's easy to work out where the config files are if I have forgotten and they are easy to read and change. Rootless and daemonless is nice too.
I tried a few things along the way, podman compose felt clunky so I'm glad it is deprecated and it's clear quadlets are the way to go.
There was a learning curve and there's less information out there than with docker, so keep that in mind. I would still lean towards docker and docker compose for local dev to bring a stack of services up and down.
I'm using fedora coreos to run nextcloud on a cheap old workstation. It took some work to get the configuration right, but I'm very impressed by how little maintenance I need to do (so far none at all).
The quadlet + MicroOS (or any other Atomic distro i.e. Fedora CoreOS) is a very powerful combo; I've been on the slow process of migrating all my nodes over to MicroOS and pushing for it or something similar at work. The combo of automatic rollbacks for base OS and declarative container configs+auto-updates feels lock they just slot together.
A split kb with integrated trackball would help alleviate the awkward mousing situations, e.g. the charybdis [1]. I'm in a similar position having gone down the ergo split keyboard rabbit hole and vim everywhere, now building a charybdis myself
Heh, I do 2hrs of z2 4x a week (8hr total) with a Charybdis and inclined treadmill. I use two wrist rests rubberbanded together though; the height of the Charybdis is significant and I don't hover my hands. I'm usually programming, though when I run into more complex problems I usually switch to less cognitively burdensome tasks. Or I just stare out the window and let my gut sit on the problem... which is surprisingly effective in coming up with solutions.
I clamped a piece of wood to the desk's edge to have something to push against, as having a point of stability is nice. You can see the back of the treadmill's control panel - I took a regular treadmill, dismantled it, and mounted the panel to my adjustable desk. The treadmill is propped up on blocks to get a ~12% incline; my usual pace is around 3.1-3.4mph, depending on the season/humidity. Sweat... is significant. I usually have a towel under my wrists to uh... collect the arm-runnage >_>
I'm using ball transfer units for the trackball. They're nice, but (as with all trackballs) you should clean the BTUs if you want to keep the smooth flicking. I use a 4k tv as my monitor, so flicking from one corner of the screen to the laptop screen all the way on the other side is really nice.
It's great, I mostly get by with Tridactyl on the browser but there's the odd website that doesn't work well with it. Warpd does better than anything else at this job. I do have a keymap to get the pointer out of the way, warpd is quite scriptable.
> Apple VPs Greg Jozwiak and John Ternus explained in an interview to a Chinese content creator on Billibilli (spotted and machine-translated by ITHome) that the main reason the power button is on the bottom of the 2024 Mac Mini is because of the computer’s size. Since it was nearly half the size of the previous generation, the underside was “kind of the optimal stop” for a power button. They also say most users “never use the power button” on a Mac, anyway.
> Apple isn’t wrong here. The Mac mini measures 5 x 5 x 2 inches, compared to 7.75 x 7.75 x 1.4 inches from the last generation; it takes up much less space on your desk, which is great. The trade-off is that you run out of space for some important things, like a power button.
That explanation makes no sense. There are many mini PCs of the same size that have their power button in an accessible location.
The excuse that most users never use the power button is the "you're holding it wrong" of 2024. Stop telling me how to use your devices, Apple.
The explanation mentioned on several forums that it's a cost cutting measure to avoid extruding yet another hole in the aluminum case, or routing the power cable, makes no sense either. This is a state-of-the-art machine, yet they're cutting costs on such trivialities? Give me a break.
This is unequivocally poor design. Yet Apple will never publicly admit that, and will gaslight everyone to think it's actually good, as they usually do.
They've managed to get people to accept things they'll never accept in Intel or Android ecosystem. Like no SD card, no memory expansion, no dual SIM etc. That gives the confidence.
I guess once system shuts down you can switch off the power at the mains or adapter socket.
In my experience with jj when resolving a conflict, as long as I do it in the earliest change, I will only have to do it once.
Git has the rerere setting [0] which reduces the need to resolve the same conflict over and over
0: https://git-scm.com/book/en/v2/Git-Tools-Rerere
reply