After using Void Linux I switched to `aurutils` to get a similar separation on Arch. I can easily maintain a local AUR repo by compiling/making my own binaries and can use `pacman` to install and manage them which improves the upgrade process overall.

Edit: I take it back. Just a 200 in a trenchcoat.

With HIPAA, is it not possible to simply encrypt the message? The "forgot password" flow for their message center is probably email anyway.

I can upload my public key to SourceHut and all email from them becomes signed and encrypted. It's a one-time process to generate long-lived keys and another to set up with SourceHut and that's all I need to do.

I appreciate your commitment to correctness but like [XKCD 1172](https://xkcd.com/1172/) ... the user is clearly in the wrong at this point.

> refactor(core): Update webmcp support to use document.modelContext

As the author points out, the line between a fix, an improvement, and general clean-up is blurry and dividing each semantic change into its own commit (and possibly squashed later anyway) is just creating work for no one's benefit.

I think Conventional Commits are just an artifact of trying to automate SemVer rather than solving any of the other problems directly. I don't think changelogs should be automated anyway - I can `git log` that if I want a list. A changelog is an opportunity to communicate to a wider audience what is actually going on under the hood.

There is still a tendency within some parts of aviation (safety auditing) to look for root causes and use tools like "fish bone diagrams" despite the more holistic approach used after an actual crash or incident.

I'm curious about the physics involved to cause such an obvious and singular failure.

Other features I've just noticed: - configurable prompt injection protection using OWASP regex (https://cheatsheetseries.owasp.org/cheatsheets/LLM_Prompt_In...) - configurable PIM protection for outbound prompts - input/output logging - "JSON healing" to auto-correct minor hallucinations

Lots of other stuff too. The business model seems pretty simple and the value-add features don't look particularly expensive or difficult to copy.

For example, `git remote -v` would show: `secure-s3 /mnt/fuse/rclone/secure-s3/git/$REPO.git`

I think concurrency is a problem with file-based remotes but for one person keeping a desktop and laptop in sync it is much simpler than running a VPS.

Fish scripting is limited to functions/aliases and this works out well since they're easy to read and tweak over time.

I've been reading up on them (https://www.kernel.org/doc/html/latest/filesystems/idmapping...) seeing some of the notation for user IDs (e.g. `u20000`) reminded me that my Hetzner ZFS storage was accessed using a similar UID format for the username.

I'm not sure I agree/understand. If you've somehow bypassed AppArmor and cgroup mechanisms then any UID/GID remapping is irrelevant. At this point you're in a position to directly manage memory.

What do you mean by "kernel escape"?

From Ward Cunningham himself:

"A wiki invites all users—not just experts—to edit any page or to create new pages within the wiki website, using only a standard 'plain-vanilla' Web browser without any extra add-ons."

"A wiki is not a carefully crafted site created by experts and professional writers and designed for casual visitors. Instead, it seeks to involve the typical visitor/user in an ongoing process of creation and collaboration that constantly changes the website landscape."

---

Wikipedia is effectively a crafted site that is maintained by experts (or at the very least very knowledgeable amateurs who 'own' certain domains) designed for casual visitors. The idea of a Wiki is great but in practice I'm less confident it exists as envisioned.

In fact, the only area I've been struggling with are "Concepts" because they have less clear boundaries for the right amount of detail.

Here is what I've been working on: https://github.com/super-productivity/super-productivity/wik...

I'm also reminded that "Obsessive-Compulsive Disorder" and "Obsessive-Compulsive Personality Disorder" are different in kind but necessarily in magnitude.

The former comcerns more localized obsessions and the latter is more of a global "default state of perfectionism".

Your threat model is the same as my use of a laptop: regular LUKS with a password is enough on its own. Add TPM if you want to know that you're entering your password in a secure boot environment (ie. protect against a fake LUKS screen that steals your password).