Kaxo

24 ms·

1.
by Kaxo 3mo ago
The seccomp-BPF rules seem almost unusably strict. What is this even designed to be used to run?
2.
by Kaxo 4mo ago
In chrome at least asm.js is(/was?) handled by the wasm engine anyway. They essentially did that transpiling at load time.
3.
by Kaxo 10mo ago
Yeah, doing it with OpenWRT and PBR is definately much simpler than this approach. However by using hard-coded IP addresses you are at risk of breakage if they change in the future. Also fastly-hosted services are a bit awkard to configure
4.
by Kaxo 3y ago
In 2018 NTSB issued a report ( https://www.ntsb.gov/investigations/AccidentReports/Reports/... ) listing 17 incidents where CVR was lost due to the recording not being turned off after the incident. And it als
5.
by Kaxo 3y ago
I found Mercusys AX6000 (aka mr90x) to be a great choice. https://openwrt.org/toh/mercusys/mr90x_v1 Anything with the MT7986B chipset is a good choice, they support Wifi6, have a 2.5G ethernet port, have decent am
6.
by Kaxo 3y ago
Not only that, since 2019 Google have required apps published on play store to have 64bit variants, this should not be a problem. However I suspect that the Xiaomi has to contend with the Chinese app ecosystem which may not be as strictly c
7.
by Kaxo 3y ago
Non-replacable battery is the no1 cause. Its amazing that the general public have accepted that as another other than a deliberate ploy to sell more new phones more regularly. Regulators need to start enforcing repairability if they actuall
8.
by Kaxo 3y ago
To save others having to read through the thread, this appears to be caused by this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=148880... Roughly, as you type the omnibox has various heuristics
9.
by Kaxo 3y ago
I feel the exact opposite. I've recently been experimenting with ipv6 only via NAT64/DNS64 and run into the same problem (with steam trying to connect out to hard-coded ipv4 addresses). I started to look into CLAT and really didn&