self.md radar — 2026-09-08
the bill arrives one browser request at a time
Fourteen CPU cores are busy turning public Git commits into HTML for scrapers. Elsewhere today: a local recorder fixes the name of its machines, and a secret tool states the part its own masking cannot solve.
1. git.kernel.org is spending 14 cores rendering commits for scrapers
Konstantin Ryabitsev says git.kernel.org now spends more CPU on commit pages for scrapers than on every legitimate access mode combined, git clones included. Across five geographically distributed nodes, 14 cores sit on HTML rendering.
The history is already there to clone. That is the irritating part. The costly route is one commit page at a time, then parsing the page back into data. Blocking was simple when bots announced themselves; now the traffic arrives through residential and mobile IPs, posing as ordinary browsers for four or five requests before vanishing.
The bill is literal: a public code host keeps cores assigned to work that a repository clone would avoid.
reading: “Creepy crawlies”
2. Screenpipe fixes the identity underneath its local recorder
Screenpipe App v2.7.26 assigns stable device IDs to new installations and adopts them for existing enterprise ones, with record collisions named as the failure it is addressing. It also stops presenting a self-healed database quarantine as unresolved.
The release notes will not change a demo. They decide whether a machine’s past stays legible after an update. A local capture system has to know which device made a record before it can sound clever about anything else.
reading: v2.7.26 release notes
3. Keyclasp keeps the key out of the prompt, not out of the process
Keyclasp gives a coding agent a credential name while a chosen command receives the actual value at runtime. Its documentation describes per-command injection and masking of exact secret values in output.
Then it gives the necessary bad news. The child process still has the credential. It can send it over the network, write it to disk, or pass it to another same-user process. The project does not call that a sandbox, and it should not.
That leaves a cleaner boundary around prompts and logs, plus the old question of whether this command deserves the key at all.