JustEnoughDucks

I think the exception to this might be excel. It was so much better than most if not all similar software at the time.

Also the android Microsoft lens app has been amazing for years, better, much faster, and often clearer than all open source alternatives and most closed source alternatives while requiring no account, bad permissions, etc... It was almost like they made it well and forgot about it for years. However Microsoft just did a big UI update on it recently so I am expecting it to be enshittified soon...

I use Code OSS with clangd and the nvim extension (because Microsoft disabled their c/c++ tools) because i want access to the nrfconnect extension pack as a beginner. I don't have to go searching in the documentation and compiling, then recompiling 10 times to self-discover the required devicetree parameters and figure out what drivers are available vs mainline zephyr.

Plus the debug interface works well.

For everything else possible it is vim/neovim, but I haven't been able to find good neovim setup for nrfconnect.

No, ssds have a ton of wear leveling where data is shifted around and not deleted. Deleting data wears out the SSD, so it is held as much as possible with the controller. SSDs are like 10% bigger than advertised just to prolong the life.

Even if you write the whole thing with random data then zeros, it will still have blocks in unaccessible (to normal users) places that contain old data.

Always best to use disk encryption or keep any sensitive data in filesystem encryption like plasma vaults or fscrypt.

Not really self-hosted, but I set up obsidian with syncthing and am going to transfer all of my notes from book stack to it and let bookstack be more organized documentation and obsidian to be a big scattering of notes and tags and such. I tried it with bookstack, but the flow was too much of a barrier for me to use it consistantly

I am going to plug my own project that I will complete in another revision when I can unpack my 3D printer when our 1st floor is completed in the renovation 😅

DIY HOTAS

https://github.com/JustEnoughDucks/LibreMiG-S

Other peoples' that I like!

A VESA to microscope adapter for mounting a lighter microscope (I use a digital one) to a monitor arm to save space compared to the normal boom: https://www.printables.com/model/803413-amscope-eakins-microscope-vesamonitor-mount

A shaker siphon to empty standing water: https://www.printables.com/model/833171-shaker-siphon-for-garden-hose

All of Chris Borge's stuff where he 3d prints useful simple machining tools and reinforces them with concrete (only a few on printables): https://www.printables.com/model/1237272-rock-solid-milling-machine-v09

The steam controller bumper repair. The brittle ABS they used broke 3 times for me (2 I sent back to steam and got a replacement), and I printed this in PETG and got my bumper back since the SC got discontinued and it has held up because petg is much lore flexible: https://www.printables.com/model/133723-steam-controller-bumper-repair

Yeah I got MX Linus running on one of those old Intel sticks that are meant to be conference room computers and such. It's the same age as the Asus and it runs well (admittedly I don't use it much)

I am doing something similar. I use OIDC for everything possible.

Authelia is quite picky about everything being correctly populated, but if I remember right, the documentation doesn't do a great job of explaining different variables for someone outside of the security industry (similar with traefik). I found a good tutorial via search that got all of the defaults set up, then playing with the options to my liking and now it is just copy pasting the condiguration per app that I want to enable, generating an key and hashing it.

If you want, I can sanitize my config and share it?

Hmmm, I used littlefs for SD card writing at work with an STM32F0 chip. It was hell working with files when tons of essential functions like appending and seeking simply didn't work in the STM HAL... Plus dealing with opening and closing files and appending files and having to seek in them to find what you want, parsing results, cleaning old files, etc... compared to simple circular buffer and a start and end address of relevant data that can be erased once every day or week depending on use. Even with a daily erase of the NOR chip, they are rated for 100k program/erase cycles which would be over 250 years before degradation starts. I am not dealing with a ton of data nor the flexibility of a full UI/ app storage where I would definitely just use littlefs.

Thanks for taking a look!

Intuitively for me, steps + bpm should be next to each other because the compiler will use bpm as the padding for the 24 bit steps. I intentionally did it that way. At least when I checked the memory addresses when testing it that was the case (there was no padding added). Wouldn't it be potentially more problematic to have a bit field with a weird bit number, 24, followed by a 16 bit member that can't be "fit" into the 32 bits that the compiler wants to assign? or is that not how it works.

I'm not quite sure what you mean by your last point. The flow would go: acquire data -> add to structure -> fill up a page worth of data (or a sector) -> write to memory. Then pulling it out would be: read from memory -> put in structure -> process -> send data via bluetooth. If I change the layout of anything, that would require a reflash of the MCU and previous data would already have been transferred over bluetooth (assuming end-user OTA flashing or just being in a vicinity of a phone and not out and about where memory saving is necessary) and would no longer be needed to be stored/pulled from memory. Or is there another case that I am totally missing?

I think nobody has ever cared enough to do it. Plus they pay so much money to the organizers, that no action will every be taken against them.

However Isreal went on after that to claim that because they got so many "audience votes" from all of Europe, that Europe supports their genocide of Palestinians.

Yes but the problem in all of Europe and the US has almost never in history been too much power. Power requirements go up and up and up and every country wants more and more every year.

Peak loads are always the worry and cause blackouts and brownouts. Low loads almost never happen, even at night because of businesses that constantly leave everything running.

Also code development programs.

Code OSS (VSCode) in distrobox with clangd language server and NCS for embedded development sucks up like 8GB of my 32 just having 6 or so files open once you start building because it keeps builds in RAM or something. It balloons fast at least lol