Coelacanthus

I want an open source mouse with electromagnetic resistance wheel like one in Logitech MX Master 3S.

And snapshot can benefit backup. Since some software need to be shudown to do backup, minimize the down time is important. The snapshot can make down time is almost stop and restart time, and the software can be online again and we can do backup on snapshot in background.

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.

1. IPP Everywhere also include full autodiscovery stuff (mDNS and DNS-SD, of course, Apple call this combination as Bonjour). So I said raster is the only difference.
2. Raster is unimportant in Linux situation because CUPS support both PWG Raster (It’s actually a subset of original CUPS Raster) and Apple Raster. Whichever one your device supports, CUPS will work fine.

I think network printer made by big manufacturer recent years should be fine with IPP driverless. They found Printer Working Group of IEEE, this organization maintains IPP standard and IPP Everywhere™ Certification. AirPrint can be treated as Apple version of IPP Everywhere, the difference between them is AirPrint requires Apple Raster but IPP Everywhere requires PWG Raster (and JPEG JFIF file format if color printer).

https://www.pwg.org/ipp/everywhere.html

I use digiKam and do sync manually.

https://www.digikam.org/

Will it work well with existed IME like Fcitx5? Or I can choose only one of them?

I see Qt Virtual Keyboard has their own InputMethod implementations, but I think it’s not a good idea to re-invent a new IME when there is no obvious advantage, because InputMethod is not a simple thing in some languages like Chinese and Japanese.

For example, libime, the core algorithm library of fcitx5-chinese-addons uses 47k SLOC to implement a good pinyin input method algorithm, even not count the Trigram language model, which is around 30MiB.

As a comparison, the pinyin algorithm of Qt Virtual Keyboard (it seems come from deprecated AOSP’s PinyinIME) uses only 8k SLOC. And PinyinIME was give up by AOSP since 2014, it never updates since that time (and no algorithm update since 2009). At 2018, Qt pull it into Qt Virtual Keyboard and never do actual algorithm optimization. So it has fallen away from the time.

Iosevka, of course.

and even without it, you’ll get 150mA @ 5V by default out of the USB 3 host upstream and up to 900mA with some pretty basic USB negotiation in a protocol that dates from USB 1.0

That’s wrong. With USB Type-C, you can get the power up to 3A @ 5V with just two 5.1kΩ resistor on CC pins.

It should be possible to switch to NCM by just flip a switch fron 0 (RNDIS) to 1 (NCM) via RRO (Runtime Resource Overlay), but adding new overlay require you have right to modify system image.

https://cs.android.com/android/platform/superproject/main/+/main:packages/modules/Connectivity/Tethering/res/values/overlayable.xml;l=27

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?

NVS 3100M has codename NV50 (Tesla), so you can see the feature matrix.
https://nouveau.freedesktop.org/FeatureMatrix.html
https://nouveau.freedesktop.org/PowerManagement.html
So you can see almost other things has been done but the power management especially Automatic Reclocking still unfinished. So the feature set and stability should be fine and the performance will be bad.