Coelacanthus

For forecast, you can selfhost a Open-Meteo. But note this need a lot of RAM and storage to run the weather model.

https://github.com/open-meteo/open-meteo

HM-SMR works better than normal DM-SMR, but it’s rare and limit the filesystem choice: none on Windows and f2fs or btrfs on Linux.

Suggest use fsfreeze --freeze to block all access operation to create a stable image without unmount the SD card. (And release it later using fsfreeze --unfreeze.)

BTW, this feature was created by XFS and was moved to VFS in Linux 2.6.29 so all filesystems supported by Linux gained this feature.

1. Thread and Zigbee use the same physical layer and MAC layer (IEEE 802.15.4), so in most case it can use the same hardware and just with different firmware (if manufacturer want).
   There is even a project to run both Zigbee coordinator and Thread border router on the same chip. It works! Although it causes some issue so Home Assistant no longer recommand this “multiprotocol” way, but this is a strong demonstration of the interchangeability between Zigbee and Thread.
2. Thread Group members is almost the same companies who found Connectivity Standards Alliance (former Zigbee Alliance). When Connected Home over IP (CHIP) project was renamd to Matter at 2019, they create Thread Group to unify the home connectivity: Only use one network layer named IPv6 and one application layer named Matter. Zigbee can’t reach this target since it use its own network layer and application layer. So they invent Thread, which still based on IEEE 802.15.4, but with IPv6 as network layer and can transport Matter on it.

Iosevka, of course.

Yeah. Because 2.5GbE was invented far later than 10GbE (from 2002 to 2016), and never popular in data center.

Oh. It’s great. But it seems there is only armv7a build on IzzyOnDroid repo while upstream has four architecture builds. cc @IzzyOnDroid@floss.social Is it a misconfiguration on IzzyOnDroid side?