Hi HN, After roughly 8 years of silently rolling 1.1 nightlies, we finally tagged a proper stable 2.0 release. We built this because wrist-sized Linux is genuinely fun to hack on, and because a handful of us think it's worth keeping capable hardware alive long after manufacturers move on. Smartwatches don't really get old — the silicon is basically the same as it was a decade ago. We just keep making it useful for us. No usage stats, no tracking, no illusions of mass adoption. The only real signal we get is the occasional person who appears in our Matrix chat going "hey, it booted on my watch from 2014 and now it's usable again" — and that's plenty. Privacy is non-negotiable: zero telemetry, no cloud, full local control. Longevity is the other half: we refuse to let good hardware become e-waste just because support ended. On the learning side, it's been one of the best playgrounds: instant feedback on your wrist makes QML/Qt, JavaScript watchfaces and embedded Linux feel tangible. The community is small and kind — perfect for people who want to learn open-source dev without gatekeeping. Technically we're still pragmatic: libhybris + older kernels on most devices since it just works, but we've already mainlined rinato (Samsung Gear 2) and sparrow (ASUS ZenWatch 2) — rinato even boots with a usable UI. That's the direction we're pushing toward. Repo: https://github.com/AsteroidOS Install images & docs: https://asteroidos.org 2.0 demo video : https://www.youtube.com/watch?v=U6FiQz0yACc Announcement post: https://asteroidos.org/news/2-0-release/ Questions, port requests, mentoring offers, criticism, weird ideas — all welcome. We do this because shaping a tiny, open wearable UX and infrastructure is oddly satisfying, and because Linux on the wrist still feels like a playground worth playing in. Cheers, the AsteroidOS Team
This data seems very incomplete and potentially misleading. >The new crashes include [...] a crash with a bus while the Tesla was stationary Doesn't this imply that the bus driver hit the stationary Tesla, which would make the human bus driver at fault and the party responsible for causing the accident? Why should a human driver hitting a Tesla be counted against Tesla's safety record? It's possible that the Tesla could've been stopped in a place where it shouldn't have, like in the middle of an intersection (like all the Waymos did during the SF power outage), but there aren't details being shared about each of these incidents by Electrek. >The new crashes include [...] a collision with a heavy truck at 4 mph The chart shows only that the Tesla was driving straight at 4mph when this happened, not whether the Tesla hit the truck or the truck hit the Tesla. Again, it's entirely possible that the Tesla hit the truck, but why aren't these details being shared? This seems like important data to consider when evaluating the safety of autonomous systems - whether the autonomous system or human error was to blame for the accident. I appreciate that Electrek at least gives a mention of this dynamic: >Tesla fans and shareholders hold on to the thought that the company’s robotaxis are not responsible for some of these crashes, which is true, even though that’s much harder to determine with Tesla redacting the crash narrative on all crashes, but the problem is that even Tesla’s own benchmark shows humans have fewer crashes. Aren't these crash details / "crash narrative" a matter of public record and investigations? By e.g. either NHTSA, or by local law enforcement? If not, shouldn't it be? Why should we, as a society, rely on the automaker as the sole source of information about what caused accidents with experimental new driverless vehicles? That seems like a poor public policy choice.
↙ time adjusted for second-chance
Don't pass on small block ciphers (00f.net)
We're seeing with Mamdani, who was elected with a massive mandate, that he can get things done despite a hostile state government that clearly didn't want him to get elected. Obama had a mandate, yet he didn't use it. Looking back, we should have seen this coming when he was mentored by people like Joe Liberman, and we immediately saw the results when he was tested in one of his first goals (healthcare). He dropped the public option immediately and implemented a Heritage Foundation plan(Yeah the Project2025 heritage foundation). You can do a lot when you have a mandate and you are determined to get things done. How to determine if a candidate is like this? After many cycles of election in my experience there is only one reliable barometer. The only determining factor seems to be money in politics. If your candidate has corporate contributions, you can pretty much guarantee that nothing is going to get done. On the other side, we've seen non‑corporate‑backed candidates actually try, at the very least. Now, talking about the actual specifics of how you get past a gridlocked Congress and a hostile Supreme Court: with the advantage of being at the top of the party, you have the ability to whip your party into falling in line. We saw this with FDR. He wasn't pulling any punches. If someone got in his way, including the Supreme Court, he made their lives miserable. One of the reasons bernie people feel fond of him. A lot of these politicians are only there for the corporate donations and in hopes of a job afterwards. So a very low‑hanging fruit is to go after the corporations that are donating to the politician who is holding things up. Make the public aware that this SOB is the one holding up plans that are very popular. Do what Trump did: go into that person's district and get his voters to realize that this is the person that's holding everything up. For example, paid family‑leave polls show ~71% overall support, including Republicans, Independents, and Democrats. Yet when Biden campaigned on it and then immediately dropped it at the first sign, it showed that he didn't even try. A lot can be done if the candidate actually tries.
 Top