The best way to reduce driving fatalities is probably to reduce the amount of driving that people do. Excellent public transit, denser cities, better pedestrian / bike infrastructure, mixed-use zoning, etc.

My (simple, naive, etc.) solution is to ban young males from driving until they're 25. Immediate drop in the accident rate plus a clamour for better public transport / bike infrastructure that even the dumbest government couldn't ignore.

(Yes, I know this is completely unworkable, sadly.)

I think the application layer is the wrong layer for encryption for immich anyways, I just encrypt the whole disk on my server. When _self_ hosting, there's no need to prevent access to files from the operator.

I thought this too, but inspecting the HTML source could have shown that a nodal would be shown next.

> I don't have any other marketable skills. My coding skills were barely marketable to begin with.

Hot take: moving is more about interview skills than coding skills. Whether you leave or not, start interviewing now. You might end up finding a better place sooner than you hoped.

Yes, it's about how you think about yourself. Identity matters just as much as experience, sometimes moreso.

Very happy to have mostly de-Googled, I don't miss the AI-forward product decisions. I only use Google now for occasional searches and interacting with other Google users (e.g. Docs).

agents + EXA has replaced almost all of my search now, except when I muscle memory it

I've been thinking of making an event platform like Partiful, but only for personal use because it's also the perfect platform for spam (send emails and texts to people with attacker-controller content).

Wax-style earplugs like you describe are the only kind that a friend of mine uses. The foam ones never fit them.

Even though it's a meaningless comparison, I'd be interested to see how performance compares (max requests per second?) for this compared to fully-featured web servers.

Honestly haven't benchmarked it, but I would imagine ymawky would be considerably slower than most fully-featured web servers. ymawky uses fork-per-connection, which is fundamentally slower than what production servers like nginx or Apache use. nginx uses event-driven IO (kqueue/epoll), which can handle thousands of concurrent connections without the overhead of forking the process on each request. Apache uses pools of threads which handle multiple connections without needing to be spawned per-request. A head-to-head against any other web server would mostly measure "fork-per-connection vs event loop/thread pools", which assembly has nothing to do with.

In a comparison between a similar fork-per-connection server written in C and this, I would imagine the throughput would be about the same, because the bottleneck in this model is fork() itself rather than the actual code. It probably matters more for binary size and startup time than requests/sec. Would be fun to actually benchmark, though.

Should i ask my Claude to benchmark it against nginx or will you ask yours

> This does nothing since the drive is still unencrypted.

Even though the data is unencrypted in memory, an attacker would still need either a local privilege escalation (from the login window?), or some sort of side-channel attack if they're still not able to get the password.

Love it