Hey, thanks for the new release. I should definitely fix my wristband and start wearing my AsteroisOS watch again (LG Lenok).
You have probably addressed that somewhere, but would it be possible to run your UI stack somewhere else? (PostmarketOS).
My other wish for AsteroidOS would be for it to leverage Wi-Fi better. Not sure how much more energy it would use, but having a longer range for my notifications would be nice (at least on LAN). Being able to perform a few other actions independently of my phone would be great: weather % time updates, e-mail notifications, home assistant control, etc. I get that it may affect battery life as well.
While I'm at it: tiny bug report, but I adjusted the time while the stopwatch was running, and this affected the stopwatch result.
We have implemented a wifi toggle in the quickpanel with 2.0. But the wifi credentials still need to be entered into connmanctl on the cli. As soon as you got wifi set up and connected, you can already now sync weather data usin asteroid-weatherfetch. But right, wifi usually uses up to 30% more power and should be enabled selectively.
For the postmarket question, yes, it is our longterm goal to mainline watches, which we are sort of doing in coorperation with the postmarket guys. But thats a humongous task and part of the idea of this 2.0 release is to interest capable contributors to push things further ;)
Their data is not perfect as they rely on public sources, and some governments are more transparent than others, but the reality is that US funding all but vanished in 2025.
Back to the topic, there is also a pattern of promising European startups being bought by wealthy USA incumbent companies. This is also happening to established compagnies: see ARM, Alstom Power, etc.
As Europe de-couples from the USA in the current context, I suspect (and hope) that such acquisitions will come under more regulatory scrutiny.
I personally agree with the more elaborate response:
1. It lays down the policy explicitly, making it seem fair, not arbitrary and capricious, both to human observers (including the mastermind) and the agent.
2. It can be linked to / quoted as a reference in this project or from other projects.
3. It is inevitably going to get absorbed in the training dataset of future models.
Ugh, this is part of the reason why I left them, but https://free.fr still does this AFAIR. They were deploying IPv6 to all their consumers well before the other ISPs (more than 15 tears ago), but they have stagnated since.
IPv6 firewall disabled by default. There is only one config for the firewall: on / off. Accept all inbound or reject all inbounding.
To think that they used to brand themselves as "for the geeks", with reverse DNS customization, built-in user-configurable server on the router (all of their routers offer a Wireguard VPN, torrent client, audio output with DLNA & others), a m3u for IPTV, etc. I wouldn't advise anyone to use them due to this issue.
Their basic firewall dates back to 2019: https://dev.freebox.fr/bugs/task/27268 (a lot of spam in the replies there). There was none before, and it is still off by default.
This is no small ISP either, they have more than 50 millions clients (including mobile), and are in the top 10 ISPs in Europe. Baffling.
The PCI bus has nothing to do with the instruction set. Usually it is just a block a designer can add to a chip, and connect to an internal bus like AXI, give or take a few other adjustments on the chip.
You can have PCIe buses without proper CPUs, even: it's quite common to find them paired with FPGAs.
For instance, Rasberry Pis have had a PCI bus for a few generations now, at first used for USB3. The Pi 5 breaks it out on a dedicated connector, making it easy to plug external devices: https://raspberrytips.com/pcie-raspberry-pi5/ (random link).
Of course, discrete GPUs are less ideal from a power efficiency perspective (duplicated memory controller, buses, and power circuits), so they wouldn't fit the Steam Deck. But write a big enough check, and I'm sure that AMD or Intel would be willing to share their iGPU designs. NVidia also makes Tegras.
If you want to be pedantic, the original (and revised) law are definitely about cost. The original formulation was that the number of features (i.e. transistors) on an integrated circuit doubled every two years for the best-priced chips (smallest cost per feature).
> The complexity for minimum component costs has increased at a rate of roughly a factor of two per year (see graph on next page).
And it is formulated in a section aptly titled "Costs and curves". This law has always been an economic law first, some kind of roadmap for fans to follow. But that roadmap drove almost-exponential investment costs as well.
I concede that density still rises, especially if you count " advanced packaging". But the densest and most recent is not the cheapest anymore.
> or even putting thermal mass around the existing oscillator
I was thinking along these lines as well. Put a metal block on the CPU and oscillator for thermal mass (not sure if separate blocks would be better).
Ideally, with a large enough thermal capacity, the block should reach an average temperature and remain there.
Inertia is also good even if the temperature is not constant: clock drift can be measured and compensated. If the temperature rises slowly, the clock speed will increase slowly: the rate can be measured and compensated for. Jitter is the issue here, and thermal inertia should dampen it.
It may also be worth preventing convection from happening on the board. Putting the Pi in a wool sock may not be the best idea depending on its temperature, but an electrically insulating thermal conductor (or an electrical insulation layer + steel wool may do it).
Heatsinks may also be counter-productive (if they have a small thermal capacity), as their temperature depends on room temperature, which changes during the day.
It may have happened. There are already many users saying their "created in" locations were incorrect. Thus the rest of my comment: trust is binary. We can either be 100% certain the data is correct, or we must assume it is never correct.
You have probably addressed that somewhere, but would it be possible to run your UI stack somewhere else? (PostmarketOS).
My other wish for AsteroidOS would be for it to leverage Wi-Fi better. Not sure how much more energy it would use, but having a longer range for my notifications would be nice (at least on LAN). Being able to perform a few other actions independently of my phone would be great: weather % time updates, e-mail notifications, home assistant control, etc. I get that it may affect battery life as well.
While I'm at it: tiny bug report, but I adjusted the time while the stopwatch was running, and this affected the stopwatch result.
reply