Legacy clients force APs to accomodate them. Be it by using slower speeds with worse airtime consumption or by just disabling features that (can) make old clients misbehave.
The blocking is being done by linuxiac.com, not by the government or by your ISP. (If it were done by them, you’d get TLS connection errors over https:, and a message over http: something like “The website has been blocked as per order of the Ministry of Electronics and Information Technology under IT Act, 2000.”)
Their source is StatCounter. I would trust the trends but not their absolute values. This month, Steam reported an increase to 4.01% while Cloudflare's human activity reports ~6%.
Even the trends should be taken with caution. By the very nature of their collection methodology and Firefox’s user base, they massively undercount Firefox (almost certainly by more than 30%, from the last estimates I remember; and possibly significantly more). I would expect them to heavily undercount Linux for similar reasons.
As the poster is saying "certain keys weren't detecting presses less than a month later" it's almost certainly a manufacturing defect, rather than a wear-out issue.
Keychron say their mechanical switches last '50 million clicks' so to wear out after a month you'd have to be pressing the key 19 times a second, 24 hours a day.
And all of us have owned multiple keyboards that have lasted for years of daily heavy use without a single key failing. Even the $30 membranes you could buy at $local_retailer didn't fail in a month.
reply