I worry what this will do to human communication if it becomes commonplace. Will everyone learn to be a forceful speaker, speaking over anyone they want to stop speaking?
As someone also not happy with my bike computer (some truly horrific UI/UX decisions), could you share or explain what you made? I like your web server.
I wanted a phone app rather than yet another electronic device. Phones do not have great screens in bright sunlight, and they run hot, so it's not ideal for a bike computer in the first place. But I can't deny the convenience of the multipurpose tool that is my phone.
This app will have a few UI/UX modes. The default is the futuristic-looking HUD, but it has a low-power mode that's mostly monochrome on black, and an even lower-power "Cruise mode" that removes the map entirely and just shows you speed, approximate heading, and nav directions. Still very WIP and mostly for my own amusement!
But in the write up it says: "Luckily, NGINX uses a multi process architecture where worker processes fork from a single master process. Because of this design, the memory space is duplicated exactly for every child worker. This means the heap layout remains entirely deterministic across different workers. If our exploit fails and crashes a worker, the master process simply spawns a new one with the exact same memory layout. This allows us to safely try multiple times until we succeed without worrying about the worker crashing and changing the memory layout. Theoretically, we could leverage this design to leak ASLR by progressively overwriting pointers byte by byte."
I wrote a script that takes two git commits and opens all changed files in vimdiff tabs side by side. I find lots of things too hard to see in github gui. It depends one [tpope's vim-fugitive].
I personally find vimdiff a bit harder to navigate for my usecase. The reason is that I am context unaware of the file often in larger projects and wanted something that allows me to check all lines in a touched file. However, I have to admit vimdiff comes quite close to what I need and is a great tool!
I ran in to a couple problems when trying that script (details below), but I'm really happy that you shared it, because I had not seen ':windo diffthis' before, and that method of scripting diffs. I'll definitely be customising it!
(I found that my mac machine doesn't support the '-printf' option, and also I was attempting to run 'git bvd main' on a branch but it seems it does a recursive directory diff, so I'll use 'git diff --name-only' as the input to the awk command).
Edit: worked nicely! I haven't used tabs much in vim so is a slightly new workflow but otherwise very handy
if its not in Rust or browser-based or a "cloud" service or the result of multi-GWH of LLM "training" or a VSCode plugin or ideally all of the prior then the HN kids wont be interested :-)
We'd love to have GiveWell evaluate Watsi. They often recommend global health interventions because every dollar goes incredibly far in saving lives. In the meantime, here's what a few (independent) experts have said about investing in access to surgery:
• A review across 23 LMICs found that low-complexity surgeries (e.g., appendectomy, hernia repair) cost as little as $17 per Disability-Adjusted Life Year (DALY) averted (Mengistie et al., 2025). Overall, 89% of surgical procedures studied were cost-effective, and 76% were “very cost-effective” based on GDP thresholds (Ifeanyichi et al., 2024).
• Essential surgery often achieves costs per DALY well below standard willingness-to-pay thresholds and can be more valuable than essential drugs or vaccines on a per-DALY basis (Mengistie et al., 2025). Low-complexity surgical interventions compare favorably to—and are sometimes more cost-effective than—interventions such as HIV antiretroviral therapy, family planning, and TB vaccinations (Ifeanyichi et al., 2024).