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.
Coelacanthus
joined 3 weeks ago
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.
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/2018/01/02/in-defence-of-swap.html
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)
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.
ESPHome has supported Thread since 2025.6.0b1. But Matter support still need more time.
If I go for SLAAC with privacy extensions and I keep paying for a static IP (v4 & v6) to my ISP then I can't implement any firewall rules for specific devices as devices will change their IP regularly. And its even worse if I don't pay for a static IPv6 prefix.
I don't know which firewall software you used. But if you use nftables, which support suffix match and conntrack for TCP/UDP, you can block all new (identified by conntrack) income (since privacy extension design for outcome) and allow income with specific suffix (for SLAAC with EUI-64, it will stable), needn't care about which prefix was used.
For example, something like epub is going to be hard because the format is really just a zip file with a specific internal file structure. So, it's not really the .epub file you want to grep, but one of the files within that zip file you want to grep through.
ePub is a zip file contains a batch of HTML file for contents and some XML files for metadata. So you can extract it and do grep as you do for HTML files.
So when they will change this horrible hardcode font fallback list with "normal" font fallback mechanism like Fontconfig?
https://github.com/pop-os/cosmic-text/blob/main/src/font/fallback/unix.rs
There are some code updates to refactor API call two months ago on Codeberg.