Exactly, remote attestation is only acceptable on your own devices with remote attestation servers that you control.
For example, it would be completely fine to implement remote attestation where devices issued by companies to employees verify their TPM values with company's servers when connecting via VPN.
All other such activities directly infringe on ownership rights.
Am I the exception? When thinking I don't conceptualize things in words - the compression would be too lossy. Maybe because I'm fluent in three languages (one germanic, one romance, one slavic)?
How exactly is this "reducing the security level to those of passwords"? For example: you can't use a passkey on attacker's web site even if you have a plaintext copy of the private key.
And especially not run the script while it's downloading. The remote server can detect timing difference (let's say the script has "sleep 30" and the buffer fills) and send a different response (really easy if using chunked encoding or HTTP2 data frames).
Subpixel rendering works completely fine on Linux. I'm using it right now, using "full" hinting and "RGB" subpixel rendering. It even works completely fine with "non-integer" scaling in KDE, even in firefox when "widget.wayland.fractional-scale.enabled" is enabled.
I had the same experience: no one knew of my mentors what "dynamic programming" was and our country-level competition (that had created problems inspired by IOI) required dynamic programming for 2 out of 5 problems. And of course I failed the first time (2004). Then I learned what it was about and aced the next time (2005).
The two parts of your statement don't go together. A list of potential output tokens and their probabilities are generated deterministically but the actual token returned is then chosen at random (weighted based on the "temperature" parameter and the probability value).
KDE is that. The two things I don't like about it are: KIO integration with GTK apps even with kio-fuse installed, and not having dbus based configuration system like gsettings/dconf.
IMO, to be a good programmer, you need to have basic understanding of what a compiler does, what a build system does, what a normal processor does, what a SIMD process does, what your runtime's concurrency model does, what your runtime's garbage collector does and when, and more (what your deployment orchestrator does, how your development environment differ from the production...).
You don't need to have any understanding on how it works in any detail or how to build such a system yourself, but you need to know the basics.
WiFi 6E works fine on OpenWrt, it's just that there are only two routers supported in ToH SmartRG SDG-8733 and SDG-8734. It works out of the box (I tried just as a test) on my MT7922 (RZ616) card in my PC.
Nitpick: it can be if you redefine numbers and/or operations. Math is not science (but is used as a basis for science) and you can yourself redefine what 2, 5, + and = mean, and use that new set accordingly. Just like you can make "Sky is green" true if your redefine what either "Sky", "is", or "green" mean - language is also not science so it can be redefined.
The worst thing with their store was the 3rd party review and signing process. For a time you also had to pay (a lot more than $99) to receive a developer certificate.
To saturate 2.5Gbps in a single direction with WiFi 6/7 modulations with 2x2 MIMO (most phones, tables, laptops have 2 antennas), you need a (total) channel width of 200MHz, and that's for devices in the same room as the AP. If you want to saturate it with devices in the next room, you need closer to 240-300MHz, for example: using say you use MLO with 160MHz on 6GHz, 80MHz on 5GHz and 20MHz on 2.4GHz), totaling 260MHz.
This is a great story. Hopefully it encourages others do the same. I have done a similar thing a few years back for another cheap router that had a new revision.
And it's not correct. Resulting frequency due to random noise is also changed, but in FM, noise is less perceivable. There is no such thing as "affecting amplitude" and "affecting frequency" - they are not separate concepts.
No, that's the most inconvenience you can cause. There are worse things you can do: target specific people with spurious orders, cancel everything they order, or if you want add random items to every order, making the entire system useless.
Intel sells two versions of their WiFi cards: ones ending in 1 use CNVI protocol and work only with Intel chips. These are sold really cheap to OEMs; ones ending in 0 use standard PCIe and are sold to OEMs for ~$10 more.
AMD decided to brand Mediatek's MT7921 and MT7922 as RZ608 and RZ616 to have something to sell to OEMs at the same price point as Intel's xx1 chips.
As a contributor to OpenWrt it makes me wonder why don't people differentiate between OpenWrt and various proprietary vendor SDKs. No one would have referenced Fedora if there was a bug in Nobara.
You are not "simply using" an internet browser. You are using an entire (browser) OS in itself on a 4x pixel count display with antialiased text, transparency, blur, scaling, video compositing... The OS itself is using additional compositing for windows using indirect rendering - all the things that add latency. Additionally, you are using a remote application that has it's own latency when talking to the remote server and even locally executing JS is doing everything in a single thread, plus V8 JIT only works for hotspots in the code.
Fibre cables are not expensive, they are even cheaper than Cat6. Transceivers are a bit expensive, but got a lot cheaper than they used to be, still they are really cheap compared to other house build/remodel costs. The only issue is that you can't do power over fibre so it's inconvenient for putting wifi APs, cameras, and other powered devices.