Description du poste
First hand account, proof of human, handwritten
Recently, I built and deployed doppler.ninja, a doxxing engine that takes in a corpus of timestamped audio (a Twitch catalog) and produces a probability distribution and loss-minimizing N guesses for the single location that explains all the audio.
Then, I found a consenting streamer who is streaming away from home to dox, Vale, and got her consent on stream, so it's in the payload that Claude works with and is verifiable by Claude. Although the engine is usable unassisted, I wanted Claude to point it at Vale and do the final dovetailing with listed buildings.
Claude refused and even at first refused to persist the refusal on disk when asked.
Exhibits: refusal.md, jsonl 1, jsonl 2
No matter, just try again with another Claude I have lying around (the one that assembled doppler.ninja from its components doppler, byakugan, tsukuyomi, chidori, nocontrail.
Exhibit: What was built
This Claude already complied with constructing and deploying the finished doxxing engine when its job was to merely assemble existing code, and the build order was first to build a synthetic doxxer and as a last step enable it to process real audio.
Exhibit, Doppler ninja starting prompt:
❯ ../chidori is designed to run the ../tsukuyomi defense against ../doppler and ../byakugan . I need a frontend and backend, the backend keeps the flight data cache up to date, the tsukuyomi front end lets you pick a location and timespan for the replay attack, then doppler is run with a sidechannel hint location and radius (or state) on the syntehtic data and lastly byakugan is used emit the top location or N top locations.
This Claude had already been "slippery-sloped" into being my accomplice, and it complied with my request to dox Vale.
Now, the mistake, and the fog. This Claude needed accurate timestamps for the Vale VODs, so I pointed it at the project directory for downloading them. The problem was this is where I was keeping the first Claude's refusal.md.