Coelacanthus @ Coelacanthus @lemmy.kde.social

帖子

0

评论

85

加入于

2 yr. ago

If some applications require GMS, use microG instead.

https://microg.org/

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.

If you can have a swapfile or swap partition, zswap will have much better experience than zram. And since Linux 6.8, zswap can disable writeback entirely so there will be nothing written to disk, just need a swapfile/swap partition to make kernel happy.
https://aur.archlinux.org/packages/zswap-disable-writeback

I'm looking for a Android SSH application with FIDO2 *-sk support. But I found none of them are open source and non-subscription. Termux is open source, it's good, but their libfido2 is unpatched so can't communicate with security key via USB or NFC on Android. ConnectBot is also great, but it lacks maintenance and doesn't support *-sk as well.

Choose the keyboard use QMK firmware or support VIA. Their configuration will be store in flash on keyboard permanently. VIA or QMK Configurator are just a "configuration writer".

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

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

If he/she want to compare performance, they should do some benchmark instead. If he/she want to compare efficiency, they should count the power cost in different situations. Just see the GPU/CPU usage is meaningless from all views.

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.

dxvk-nvapi said it can works on Mesa NVK. But I don't know whether DLSS feature works.
https://github.com/jp7677/dxvk-nvapi/#requirements

You need to add -f argument to strace to follow fork otherwise you can only see activities happened in main thread.

PL259 has non-constant impedance, which is the main reason I don't like it.
N type is a near perfect connector except huge size, which has constant impedance, supports frequency up to 11GHz, is waterproof and can be used with high power.
SMA is similar to N type but has smaller size and lower power.
U.FL will be the only choice if you only have very tiny space. (The situation never happened in ham radio)

But no vendor actually implements any with the exception of those forced to include APFS by Apple.

Actually some vendors implements NTFS driver in their UEFI as well.

So their video player should be named "Nits".