"Energy insecurity" transforms the problem from lack of "energy" into an emotional problem. The problem isn't feelings of insecurity, it's lacking electricity. But now we can feel all self-righteous that we're making people feel better because we don't call them homeless and hungry and in the dark. Now they "have housing insecurity" and "have food insecurity" and are suffering from "energy insecurity".
I lived for a month in a dorm in China quite a few years ago, where they had running water for an hour every other day. Hot water for tea was delivered in a thermos every morning. Nobody had "heated water insecurity". Everyone knew exactly how it worked, and they all showered two or three to a shower. I couldn't bring myself to do that, so I showered after they were all done, usually in cold water. The problem was very clearly lack of hot water, not "insecurity".
I mentored a kid for a few years whose family occasionally couldn't afford meals, so they had "fend for yourself night", where he had to figure out how to get a meal on his own. His problem was not "food insecurity", his problem was that he was hungry. Any "food insecurity" he might have had was distinctly downstream from his lack of food, and would have been entirely eliminated with regular meals.
Right, for the OpenAI case to be analogous, they would have to switch to a system where your chats are homomorphically encrypted -- i.e. OpenAI does all its operations without knowing either the input or output plaintext. In that case, they'd only have encrypted chats to begin with, and would have to somehow get your key to comply with a warrant for the plaintext.
And note: the above scenario is not likely anywhere in the near future, because homomorphic encryption has something like a million times overhead, and requires you to hit the entire database on every request, when state-of-the-art LLM systems are already pushing the limits of computation.
That picture just feels like a case study in why Apple drug their feet on features like that for so long. If you let people set a background and change the font, you're going to have unreadable purple comic sans over kittens within minutes.
If you want to go minimal on the backcountry device as well, PLBs are nice as a barebones alternative that only require a battery change every few years and don't need a subscription.
I've used exercise as a catch all for continuous monitoring of the heart. Point being, to get more utility out of a sensor, you'd have to wear it more with less interruption. 30 days without taking off a device is... Unheard of (and wicked cool!). So comfort will be more appreciated in the long term, I suspect
I've mentioned this in the above reply but I'll repeat here: It is not common to wear watches for more than a few days at a time simply because there are not many whose battery will last that long. The effects of fatigue/pressure point from the sensor bump are less observed but not missing. Majority of consumers wear Apple/Android watches that need to be recharged every day. With 30 days on wrist, I can extrapolate that fatigue will be more pronounced - so I am calling it out.
I can't help but feel echoes of the 2015-era Pebble trying to compete with the Apple Watch, and the lessons learned from that. I have an Apple Watch, I've been wearing one for ten years at this point. All I use it for is notifications, time, weather, and music control. I'm more than happy to buy a tinker-friendly smartwatch that does just that, and I don't think I'm alone. I hope these guys don't kill themselves trying to feature-match, and just lean into the inherent advantages of their platform.
I agree completely about the difficulty of a hardware startup, but being "good" means knowing in advance what kind of challenges you'll face, or at least knowing who to consult about it, and when to listen to their advice. I guarantee that at several points in the development of their product, someone pointed out the high BOM cost and the math required to become profitable. At this point Kickstarter has been around for long enough that even people without direct experience in hardware development should have enough case studies to know what they're wading into.
