For more commentary on the relation:
Dateline NBC - The Real Soup Nazi (Seinfeld episode content included)
https://www.youtube.com/watch?v=YXgI7XsY0WQ
It's hilarious he actually raised the price of bread.
9,457 karma · joined January 16, 2026
SimpleX: https://smp17.simplex.im/a#GFPITRU-oDdr_NvxpeptnC9ldhlSQnrEvoggS7dQNFs
Fed count: 1
cider9986@protonmail.com
Spam count: 6
For more commentary on the relation:
Dateline NBC - The Real Soup Nazi (Seinfeld episode content included)
https://www.youtube.com/watch?v=YXgI7XsY0WQ
It's hilarious he actually raised the price of bread.
My 9 has had no hardware issues besides the designed ones.
A warrant requirement is not a reasonable bandaid to consider allowing mass surveillance. There should be no mass surveillance, only targeted surveillance.
A warrant requirement makes sense for something like the locations of customers on cellular networks, because, although it should be improved, it's been built into the tech.
When you make the optional choice to create mass surveillance, safeguards do not make it acceptable.
Plenty of places have very low crime without mass surveillance.
https://www.reddit.com/r/GrapheneOS/comments/1qv8y7d/what_do...
> Despite all the nonsense that's posted about UK on the internet
How is it nonsense? I'm not debating the warrant thing, but it's very reasonable to assume the UK has terrible protections for these sorts of things.
https://en.wikipedia.org/wiki/Key_disclosure_law#:~:text=Uni...
GrapheneOS allows using a passphrase with more convenience because of the fingerprint plus second factor pin (I don't think you can just have a pin as a secondary unlock). You don't need to enter the passphrase every time you unlock with this setup, only when first starting up.
The official opinion: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
Yes this is of course safer. What evidence do you have that it doesn't work on GrapheneOS, though?
https://www.computerweekly.com/feature/Journalist-Richard-Me...
This goes to show for all the people that want GrapheneOS to implement a feature like hidden profiles–flawed features give people a false sense of security and should not be implemented (that's not to mention deniability may not even be a good feature if it was technically possible to implement it well).
Me:
>What about a duress timer working as the reboot timer but it wipes if you don't unlock within the time period. Would that have any advantages for destruction of evidence or deniability?
HybridStatAnim8:
>That would not be viable because the hardware does not support it. It cannot be implemented in the OS because the OS can be turned off or exploited endlessly. For GOS to consider it, it would likely need to be backed by the secure element.
>Duress PIN is deemed acceptable to implement in the OS because it is expected that the user is the one to enter it, so it has not fallen into the hands of attackers who may bypass it. Once attackers have it, you are effectively gambling. Account for that in your threat model and do not let it get to that point.
>Even if that device doesn't have the ability to turn on Airplane Mode or to turn off the transmitters through the Control Center of iOS.
IIRC, the default on iOS is that anyone with your locked device can enable airplane mode which is concerning simply for thieves. But I suppose they have to use faraday bags anyway because of the Find My network.
>As I understand it this encryption is a significant additional barrier to technical or legal access to those files. If someone knows otherwise, please let me know. Being wrong could cost me my home and life savings.
Yes, it seems that way in the US: https://news.ycombinator.com/item?id=49922513
If your threat model includes someone using violence to coerce you, an option could be to use a cloud storage account entirely over Tor from the browser (preferably download the app because of web cryptography risks) with the login memorized. That way you can access it on any computer even if yours is lost and you can remove traces of it from your phone.
GrapheneOS's default is 18 hours and it can be set to between 10 minutes and 72 hours. iPhones and Stock pixels have it non customizable at 72 hours.
On GrapheneOS, for privacy and convenience, it's best to use a long random passphrase [1] for your primary unlock and then a fingerprint with a second factor pin as the secondary unlock. You enter the passphrase every time the device restarts.
If you're encountering someone that's going to seize your phone, try to restart/shut it down yourself so you don't have to trust the AFU protections.
[1] https://strongphrase.net give memorable ones which is cool.
For US citizens entering the US: If you're concerned about protecting your data from this threat, you should use GrapheneOS (or less good would be a latest iPhone in lockdown mode and BFU) and not talk to the police. The 5th amendment does not seem to have an exception at the border, so you can't legally be compelled to hand over your password by border agents (there's not strong case law here). They can lie, they can detain you, search you, they can seize your stuff. You shouldn't be the one arguing with them, you should be silent (besides identification) and ask for an attorney (you don't have a right to an attorney at a routine search). As a US citizen, you can refuse and still enter.
GrapheneOS has demonstrated to be robust against physical access even in AFU [1]. It's still a good idea to shut down / restart because BFU is much more secure. To maintain convenience while avoiding reliance on the rate limiting of the secure element, you can use a long random passphrase as your primary unlock (you enter it every time the device is in BFU) and a fingerprint with a second factor pin as the secondary unlock.
Even if you factory reset your phone and backed up data (to an E2EE cloud provider, over Tor and memorized the credentials), you should still not disclose your password because it could allow evidence to be planted or your device to be compromised. Nothing you say to the border agents can help you in court, it can only be used against you.
The duress pin is generally not how you should handle a situation like this. You do not need the duress pin to prevent access, its purpose is if you're being physically coerced as well as to give the attacker the dillema of whether to enter a coerced password (it even gives this benefit for people that don't use the duress password).
Sure, if police are behaving illegally and the information that would be disclosed is worth the possible punishment, then that's a personal decision.
[1] Based on leaked Cellebrite documentation, GrapheneOS was the best performing device against AFU attacks. It also has a customizable reboot timer to bring the device back to BFU after a set time of not unlocking. The options are between 10 minutes and 72 hours of unlocking and 18 hours is the default iirc. Apple and Google added this to their phones after GrapheneOS without the option to customize. Theirs are set at 72 hours.
You make the government powerful while the people you like are in charge, then when the people you don't like are in charge you're gonna get fucked.
Actually you're getting fucked all the time, unless you take a bipartisan approach to safeguarding privacy.
https://www.reddit.com/r/wallstreetbets/comments/8aiz67/how_...
Here's a similar discussion from a few weeks ago: https://news.ycombinator.com/item?id=49622042
https://grapheneos.org/faq#device-lifetime
It doesn't seem like they are ending support for updated software on these devices before 10 years, it will just be different software.
Also, what?? https://america.gov/privacy
At least realfood.gov was decent [1].
Shouldn't the government websites work on very slow internet connections?
Where's the source code for these websites? First of all, if they are vibe coded by government employees they have to be open source, and secondly, if they are vibe coded (even by a contractor), then they can't be copyrighted.
[1] https://fedtechmagazine.com/article/2026/04/national-design-...
Edit: it says this one is made by the National design studio at the bottom.