A duress pin is useful if the cost of the government getting mad at you because you wiped your data is less than the cost of letting the government have your data. Whether that holds depends on your situation—for example, whether your phone's data could implicate other people that you want to protect
When talking about costs we should remember who is paying. Maybe overall the cost of the government getting that data is higher than the cost of them getting mad at you, but when a single individual is paying for all of it the equation might change.
ultimately everyone is paying the price of reduced rights and freedoms when the government starts wanting to check your phone for wrong-think and harass unofficial enemies of the state
Since you brought it up...
The population of Gaza has been going up since 1948.
Before Hamas attacked, tens of thousands of Gazans had work permits in Israel, and many Gazans were treated in Israeli hospitals.
After Hamas started a war, Israel provided food, power, water, fuel, and medicine with intermittent interruptions. They had ceasefires to provide vaccines for children.
Israel warned civilians of imminent attacks, and generally gave them time to move. That rarely happens in a war, never mind a genocide.
It is absolutely true that tens of thousands of civilians were killed, although it is difficult to quantify because Hamas soldiers do not wear uniforms and has 100% of its military capabilities around and below hospitals, mosques, schools, and apartments. Also, Gazan authorities have never distinguished military and civilian casualties in their reporting. And despite having the world's largest bomb shelter, i.e. 500 km of tunnels, Hamas did not allow a single civilian into them during the war.
But stipulating tens of thousands of civilian deaths during an intense urban fighting, there is a name for that. The name for that is "war". Genocide is an entirely different phenomenon. You seem to conflate the two.
About my use of the word "genocide": genocide is defined not primarily by the scale of the killing, but most importantly by the intent behind it. The intent of the war on Gaza, as expressed repeatedly by the people prosecuting it, is to destroy the Palestinian people as a people. That's what makes it a genocide, not just the raw number of dead. https://www.un.org/sites/un2.un.org/files/doc.1_convention_o...
(In the interest of keeping things on topic for HN, I won't respond to your other points)
The "that happened" term seems a supremely important part of the title given the "is science fiction" term before it, as it clarifies the cyberattack isn't a made-up story. In contrast, the target, Hugging Face, is merely a detail that can be left for discovery upon reading the article. It's less important who was attacked than that the attack actually happened.
Without knowing the exact character limit for titles and without having the motivation this late at night to count the current title length, you may also be able to drop the "accidental" to fit in "that happened", but I worry that leaves too much of a door open for someone to interpret the attack as deliberate. As such, I strongly prefer my first option.
A good introduction to SoA (for anyone curious) are the two most famous Data-Oriented Design talks by Mike Acton (game engine dev) [1] and Andrew Kelley (Zig lead dev) [2] respectively.
I read a book book about DoD [3] really which confused me at first with all its talk about database table design (in a book about a high-performance C++ game engine?), but when it finally clicked it was amazing. The point is that you want to think hard about your access patterns and what could constitute good "primary keys", then model it accordingly. SoA ends up being useful a lot of the time, because having your data in homogeneous arrays/vectors is great for cache locality and branch elimination. Even without SIMD you can get huge speedups from that, but that's also where your compiler (or you as a programmer) can get incredible SIMD gains.
SoA is not a silver bullet as it may not align well with your access patterns, but it can great to add to your toolkit.
You can partially protect yourself from these attacks by disabling 2G on your device. This won't prevent location tracking, but will stop the attacker from intercepting calls or texts.
reply