<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: bonkusbingus</title><link>https://news.ycombinator.com/user?id=bonkusbingus</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 27 Jul 2026 21:41:10 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=bonkusbingus" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by bonkusbingus in "US Government targets Cop City protester over phone operating system"]]></title><description><![CDATA[
<p>This is a good article, and it brings much-needed attention to this case, which so far has not received the level of public awareness that is consummate with seriousness with which the federal government intends to weaken or undermine the First, Fourth, and Fifth Amendment rights of every American in prosecuting these bogus charges against Sam.<p>However, it makes an erroneous equivocation that, I believe, has profound technical and legal implications. In the article's first paragraph, it claims that GrapheneOS "enables users to enter a passcode and wipe a phone clean". What the author of the article is referring to is GrapheneOS's duress password/PIN feature[1], which does not (contrary to what it may seem on first glance) delete or modify the data on the persistent flash storage phone in any way. What it does is zero the key slots in the phone's Secure Element, which stores the disk encryption keys necessary to decrypt the data on persistent storage (technically, these disk encryption keys are not themselves stored in the secure element, but are first encrypted with a key encryption key/KEK derived from a user-entered passcode/PIN and then stored in the secure element[2]. If an adversary were able to break the secure element and extract the contents of the key slots, they would still need to brute-force the KEK in order to obtain the actual disk encryption keys).<p>To my knowledge, US law does not explicitly say whether deleting the key necessary to decrypt a given ciphertext is equivalent to deleting the ciphertext itself. Technically speaking, they are not equivalent, even if it would take an exorbitant amount of time to recover a deleted key using a brute-force search or some forensic method. If the federal government wants to claim, using this case to set a legal precedent, that it is equivalent, then I would argue that this in effect <i>makes encryption as a concept illegal</i> (as encryption is nothing without the ability of the person using encryption to control access to the encryption key(s)). Reading about the recent Prairieland trial, in which (among other blatant injustices) an activist was convicted by a kangaroo court of "destroying evidence" because they merely removed someone from a Signal group[3], it's clear to me that Prairieland along with Sam's case is part of a coordinated strategy under the NSPM-7 "Antifa Memorandum"[4]: the federal government is using lawfare to establish that it has a right to arbitrarily access the data of its citizens in order to crush political dissent.<p>[1] <a href="https://grapheneos.org/features#duress" rel="nofollow">https://grapheneos.org/features#duress</a><p>[2] <a href="https://grapheneos.org/faq#encryption" rel="nofollow">https://grapheneos.org/faq#encryption</a><p>[3] <a href="https://www.theguardian.com/us-news/ng-interactive/2026/jun/24/prairieland-texas-ice-protests-zines" rel="nofollow">https://www.theguardian.com/us-news/ng-interactive/2026/jun/...</a><p>[4] <a href="https://en.wikipedia.org/wiki/NSPM-7" rel="nofollow">https://en.wikipedia.org/wiki/NSPM-7</a></p>
]]></description><pubDate>Thu, 23 Jul 2026 22:38:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=49029004</link><dc:creator>bonkusbingus</dc:creator><comments>https://news.ycombinator.com/item?id=49029004</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49029004</guid></item><item><title><![CDATA[New comment by bonkusbingus in "Show HN: I used Claude Code to discover connections between 100 books"]]></title><description><![CDATA[
<p>"There are, you see, two ways of reading a book: you either see it as a box with something inside and start looking for what it signifies, and then if you're even more perverse or depraved you set off after signifiers. And you treat the next book like a box contained in the first or containing it. And you annotate and interpret and question, and write a book about the book, and so on and on. Or there's the other way: you see the book as a little non-signifying machine, and the only question is "Does it work, and how does it work?" How does it work for you? If it doesn't work, if nothing comes through, you try another book. This second way of reading's intensive: something comes through or it doesn't. There's nothing to explain, nothing to understand, nothing to interpret."
— Gilles Deleuze</p>
]]></description><pubDate>Sat, 10 Jan 2026 22:43:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=46570681</link><dc:creator>bonkusbingus</dc:creator><comments>https://news.ycombinator.com/item?id=46570681</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46570681</guid></item></channel></rss>