There are some code updates to refactor API call two months ago on Codeberg.

• You can use imapsync to sync all you mails from GMail to your new email provider if you still use email.
• If you no longer use email, Piler is a bit heavy but well-working solution.
• Notmuch is much lightweight but has no web UI, but if it require you install a (may be TUI) software, why not just install a mail client like Thunderbird and then just use its local mail feature to index the mbox?

The green PCB on left-bottom corner breaks the consistence of design...

Maybe mark it a compose of 2G/3G/LTE/NR, such as LTE only/3G+LTE/LTE+NR.
But there is another issue: the cell tower is belong to different MNO, so for some MNO you get 3G+LTE but for another MNO you get LTE.

I suppose displayport over thunderbolt plus embedded USB hubs in computer monitors gets close, but the display settings controllers usually require proprietary drivers and are vendor specific.

DisplayPort have DDC to control display settings. But I don't know how much settings was standardized and implemented by vendor. But at least, the backlight was implement by most vendors, many users use it.

It's difficult to have. The members of HDMI Forum are almost the TV manufacturers and the members of VESA (the maintainer of DisplayPort) are PC and GPU munafacturers. So TV almost uses HDMI and monitor almost uses DisplayPort.

OpenWiFi implemented a WiFi 6 (802.11ax) network card with FPGA, and its driver. Currently only available for subscription, but will be open source in future.

Unfortunately, IIRC, some feed readers only support RSS, not Atom. Those users may see some warning like "invalid format".

They are totally different format: different structure, different keyword, different time date format, different escape way, different language specifying way...
Their common parts are only both used for feed and both use XML.
And even more, interoperability of RSS 2.0 itself is horrible, RSS 2.0 standard left too many details in not specified situation, such as how to deal with relative URL...
For more infomation, you can read https://www.intertwingly.net/...

Actually it's simple than "NAT", technically. Normally when we said "NAT", it's not just NAT (Network Address Translate), but a NAT plus a stateful firewall (see documents below). The conntrack here is a stateful firewall as in "NAT". And compare to create a map from (paddr, pport) to (iaddr, iport) and match the later, it's more simple to just match suffix of address.

https://datatracker.ietf.org/doc/html/rfc4787

https://tailscale.com/blog/how-nat-traversal-works

No. It's not random. SLAAC uses EUI-64 by default, it generate fixed /64 suffix from MAC. And with suffix match of nftables you can still do device specific income firewall rules. For random privacy address, it's only used for outcome so just block all other income of IPv6 addresses except EUI-64 is enough.

I think that most of usefulness of swap has passed now that we have systems with noodles of ram.

Please read this article authored by maintainer of Linux kernel memory management subsystem and cgroup subsystem, Chris Down.

https://chrisdown.name/...

And there is another article with some additional informations about swap authored by @farseerfc@sn.angry.im who tranlated the article above to Chinese.

https://farseerfc.me/followup-about-swap.html (only Chinese version available)

Because not all language and all users requirements is simple.

For example in CJK, we have too many characters (over 97k) to packed in one font. And we have many font style. So when put them together, we need to modify the font fallback list by user so users can make font at the right place to avoid some characters are sans-serif (Heiti), some are serif (Songti/Mingti), some are Kaiti and some are Fangsong. And in CJK, for same characters, it have different glyph in zh-CN, zh-TW, zh-HK, ko and ja. So we need different fallback list for different locale.

In Arabic and Urdu, the situation is worse. They use almost same characters, Arabic alphabet, but use different style: Arabic use Naskh, Urdu use Nastaliq. These two styles are very different if you only learned one it's hard to read another. So you must specify different font fallback list for different locale.

And it's not the end. Persian use Persian alphebet which is basically Arabic alphabet but plus 4 new alphabets. Unlike Arabic and Urdu only use one style, they use Nasteliq for poetry and Naskh for others. So just depends on locale is not enough for Persian, users need a way to customize font fallback list per UI elements, like CSS in HTML. Of course, it's so difficult to implement that only a few application support it. I write here here just to tell you the font fallback is a complex thing and it's impossible just using a simple per script list.

And the last issue is for all language users: it's hardcode, so you can't choose your favorite one. They said it's TODO to implement configurable default, but there is still no code, and I can't image the deal time of the configurable fallback list, and of further font fallback mechanism with font replacement features and font OpenType control features and so on. If they choose use wide-used Fontconfig instead of re-invent a square wheel, they can gain all these features with only a few code.

https://github.com/...

RTL8159 is great. It's almost the only USB 3.2 (not USB4, not Thunderbolt) to 10GbE network card. RJ45 instead of SFP+ is a bit frustrating, but at least we can reach 10GbE without requirement for more PCI-E slot or USB4/Thunderbolt support.

Actually, Celeste is originally a 8-bit game. It was developed on PICO-8, and then was ported to PC.

Ok. Mark it as Open/OWE/WPA/WPA2/WPA3/802.1X. The main reason prevent old phone connect is WPA version. The newer WPA version require newer hardware and software.

If you want to use microG as GMS replacement, it's impossible to do it without rooting. When application access GMS API, it will check the signature of GMS, so microG need some patch (Some ROM include it, like Lineage OS) or hook (e.g. via Xposed, like FakeGapps module) on system framework to return a fake signature for such a query.

The keycaps look like lots of Want Want Milk Candy.

What ever DisplayPort do, HDMI do more badly. HDMI also requires Annual Fee to get document now (since 2021, before that the document was public available). And this is not the worst thing, the worst thing is the HDMI forum disallow anyone open source a driver which support HDMI 2.1 or higher.

https://gitlab.freedesktop.org/...