Legit thought it was just going to be a wall of text editors and nothing else

Well, that’s the last excuse I needed. Time to finally buy Witchfire.

Glances at the one occasionally unclimbable ladder

https://grapheneos.org/faq#future-devices

I suppose I could have phrased that better. The registers themselves correspond to particular applications/stages, but the values store in those registers should change based on how the application/stage was loaded. Switch the order or inject a new binary and the hash from that stage on should change.

Any changes in the boot process should change various PCR registers. https://wiki.archlinux.org/title/Trusted_Platform_Module#Accessing_PCR_registers

Yeah, that’s it. I normally recommended going through the main readme https://github.com/SteamDeckHomebrew/decky-loader?tab=readme-ov-file#-installation

If I resort to using a Mac I want someone to put me out of my misery.

There was a rather famous piece of software at my last job. Guy writing it wanted job security. A lot of the core variables of the application were named based on the sounds a helicopter made. God damn onomatopoeia variables. Pretty sure that shit is still in use somewhere.

Yeah, not sure how much he’s distancing himself from FUTO related things though. He brought up grayjay recently, but only specifically to talk about the devs comments on recent Texas app store legislation. Kind of a wash.

Given he is playing politician now, I don’t think he’s going to make a public statement about it. Not only would it hurt his influence but it would probably stall out any ongoing negotiations regarding right to repair. Shit sucks in general.

I’m a little disappointed in the amount of time spent on the XZ attack. The title and it starting off with some good history made me think this was going to be more of a retrospective, looking into the issues that created the solutions used today.

It seems to be just calling out the solutions and how they would interfere or did interfere with a given attack, where XZ is most commonly used as an example.

I’m pretty sure the mirror was setup before that was an option. No reason to turn it off now that it’s a source of entertainment.

Do the opposite of all this, assuming you ran this script some time between 2024 and now:

https://github.com/denis-g/steam-deck-optimization-guide/blob/072642922f86214ed9a4507ec8b93e0a9a86fb12/scripts/steamos_optimization.sh

https://wiki.archlinux.org/title/Wayland#Automation

Honestly, I was running into the limits of stow. Want to unstow some configs on a bare machine? I hope you wanted that entire directory to be a symlink. Then I saw that someone had actually fixed that many years ago but the maintainer at the time was caught up in some personal crypto related projects and did not appear to be looking at the mailing list.

Chezmoi fixed that, applied a templating engine and added a data mechanism. In moving my stow configs I realized that application specific config file deployments are nice but shouldn’t be necessary. Templates fill that gap, and meshing them with scripts allows you to do some cool things only when variables change.

Plus I was beginning to play around with go at the time, so it just seemed like a good idea to use something I could contribute to if I needed.

I still don’t think I’m using chezmoi to it’s full potential, but I am fairly proud of the script I use to determine data sources for my waybar config on all of my machines.

All public and I regularly link people to my bash functions. Started with git bare repos, moved to stow, now on chezmoi. If I need anything more complex than chezmoi for these I’ll probably give up syncing them altogether.

https://github.com/StaticRocket/dotfiles

I use them all the time, but that’s just because of Yocto and the need to keep at least the 3 major LTS builds hot in the event something breaks.

Asynchronous trim is interesting to see in a performance optimized config. I remember it actually being slower at deleting files and causing more ware on SSDs that periodic trim.

Usual tracking and fingerprinting issues. Would need to sandbox it to make it secure, but that then makes the fake traffic easier to identify. Not worth it in the end.

That defeats the privacy and bandwidth reasons you’d want to use uBlock but that’s close to the operating idea of AdNauseam.