> So you should be safe, apart from some kind of rubber-hose cryptanalysis.
There are vendors that sell the technology to adversarially access phone data, the "Before First Unlock" is the safest state a phone can be, but it's not infallible. The safest option is to have a burner or factory-reset phone with nothing on it, even if the hack succeeds.
I've worked with Cellebrite, the industry standard in IT forensics for unlocking and imaging phones. It just runs a series of known exploits. PIN lock, data encryption and regular updates will beat it most of the time.
Before First Unlock with recent hardware and an up to date OS is probably sufficiently infallible for an average person. I wouldn't want to rely on it if I was engaged in espionage, but for someone who won't get the NSA pulled into the case, I'd be pretty confident. This leaked Cellebrite support matrix shows that BFU was secure against them for iPhones that were nearly four years old at the time, and I doubt it's become significantly worse since then: https://ia800405.us.archive.org/32/items/inseyets-offline-uf...
It's the lack of personhood rather than inability to produce copyrightable material. However, the companies controlling the AI systems have legal personhood and should absolutely be charged for criminality that transpires under their watch or at their behest.
An actual jury nullification cannot be appealed, and the accused gets to go scot-free forever in that jurisdiction, even to prosecutor's chagrin. In this case, the prosecutor could gather another grand jury and try again, at any time, without restriction, if they so choose.
Buried lede is that this is someone's chance to coin a new term for "something that feels like jury nullification but isn't because it's a grand jury and the internet lawyers are being pedantic because they really don't like the idea of people being able to point at an honest-to-god case of jury nullification."
> Certainly having a larger stdlib helps Go projects keep their deps down, but I don't think it's the real reason
I disagree: having a big stdlib that encompasses a huge chunk of common functionality (logging, a plethora of network server/client protocols, etc) means that for basic needs, the question of 3rd party libs never arise, whereas for other language, the question is not if you need a dep, but which one. Making gorilla easier to find won't undo the cultural reluctance of adding a 3rd party dep when using the (very pragmatic, IMO) stdlib server is adequate to the task.
If everyone could convince management to care about security over "productivity" (read as number of marketable features squeezed out of organizational orifices per unit time), and maybe wire-up open-weight agents to do security critiques, we'd all be in a much better place, but Altman won't like that.
> It’s just not really a flagship phone in terms of processor performance.
I'm curious to know which apps/use-cases you feel are hobbled by the non-flagship processors on Pixels. It feels like most peoples top 3 activities on phones are infinite scrolling inside apps or a browser, taking pictures, and playing games, which Pixels seem to be great at. It's been many years since I felt that a phone that is slow enough to notice - even the midrange ones, and I (used to) write and debug code on my phone.
Sure, 4 years later anything can run Genshin, but the point is that the next new hit game is just around the corner and gamers appreciate the extra performance.
My understanding is also that the pixel’s tensor chip series is not very “flagship” in terms of battery stamina/efficiency when you’re doing heavy tasks such as gaming.
So it’s not always about having the faster processor, you can also benefit by your processor being the most efficient on the market and making the most use of the battery in your chassis.
Video comparison of last year’s phones head to head where the Samsung phone lasts nearly 8 hours longer on video playback:
> But just trying to say this isn't data center specific. A steel mill with 36MW of electric arc furnaces is going to release the same 36MW of heat into the general environment
The subtext is broken social contracts[1]. A 36MW steel mill is loud, hot and polluting, but it is tolerated because it makes up for the ills by employing a lot of locals and positively contributing to the local economy (housing, retail, food and beverage), etc.
The AI CEOs thought it'd be a good idea to hype their products by promising to take people's jobs away, and people remember that when a new data center proposal pops up in their town/county.
Circling back to your generalization: if an equivalent 36MW steel mill flew in workers from Canada/Mexico for each shift - or somehow implemented 99.5% tele-operation by Ghanaian workers, locals would grouse about the pollution and noise because they can identify a raw deal.
1. Americans have been fed up with powerful people getting away with violating social norms for 2 decades - if not longer, sometimes with a partisan tinge, oft-times without. It's the common thread linking the Tea party, Occupy Wall Street, Bernie Bros, Trump I, BLM protests, the Epstein files legislation and release, cutting down of Flock cameras and the ire against AI and AI data centers.
It's not darkest Africa, or Haiti, but it is sufficiently outside the normal trade routes to not have routine, inexpensive access to components that most of us here take for granted.
I totally agree. Trinidad & Tobago isn't a poor country. It is a petro state (oil and gas) in the Caribbean. GDP per capita is 20K USD. That is middle income.
In the article, he addresses the issue of clones vs 1st party RISC chips on AliExpress. As a mere dabbler, I have been bit by undisclosed errata on an STM-compatible/bootleg/clone/counterfeit Arm chip while using the official STM SDK.
Maybe. There's less wiggle room though. You can't make a clone of a WCH, ESP32, GD32V, or RP2040 at a low enough price point to really profit from the gap.
If Quintauris successfully makes a RISC-V range for automotive use, there'd probably be margin to clone those and sell at a profit, but skirting automotive certification regulations is a high-risk game that (hopefully!) doesn't have many buyers.
If they make an IoT line, again, there might be margin in it, but you'd be trying to fit in between buyers willing and able to engage with Chinese sellers but for some reason unwilling or unable to engage with existing Chinese sellers of existing IoT RISC-V parts. Quintauris is a very, very long way away from being a "household name" along the lines of STM32 or FTDI.
I think the parent's point is, cheap MCU will have quirk no matter it's ARM clone mcu or RISC V MCU. Most of the time, the quirk exists in peripheral, not cpu core
> Sure, but that problem should exist for both ARM and RISC-V.
I don't know why you'd take that as a given when marquee RISC-V microcontrollers are almost universally low-cost, but Arm has pricier marquee parts, thus a bigger opportunity for undercutting the market leader on price with a cloned product.
There are vendors that sell the technology to adversarially access phone data, the "Before First Unlock" is the safest state a phone can be, but it's not infallible. The safest option is to have a burner or factory-reset phone with nothing on it, even if the hack succeeds.
reply