The US has been doing that for years already. There's plenty of stories of people (US citizens included) being detained by border agents in US airports for refusal to provide said agents with access to their devices.
They can detain you and take your device, but they cannot compel you to give up your password, to be clear. As a US Citizen you have a right to re-enter the country.
The letter of the law says you are correct. Reality however disagrees. People who are most definitely US citizens have in fact been put in jail for the simple not-crime of refusing to provide passwords to their devices to law enforcement.
So if a company uses as part of its marketing for a product the phrase "advanced security, privacy, and connectivity for homes of every shape and size" and then is later found to have lied about the "advanced security" and "privacy" part of their marketing by shipping firmware with security bugs, does that not now fall under the "deceptive" category of the "unfair, deceptive and fraudulent business practices" part of the FTC's mission?
Sounds like it does to me. Also you're forgetting the part where the FTC under a prior administration either banned DLINK from selling in the US or heavily fined them for selling routers in the US that they knew were running insecure, buggy firmware.
(both quotes were taken verbatim from first, Netgear's US website, and secondly the Bureau of Consumer Protections' section of the FTC's website)
OS makers should not be in the business of enforcing censorship. If you want to shield your children from the "horrors" of the internet either use proper parental control software, or don't allow access at all like you said until your kids are mature to understand what's going on
The onus is on the parent to the be parent. Not the tech industry, and especially not the government.
If the solution is parental control software, that also puts onus on operating systems to present the means for such software to work properly.
This does not mean the OS should censor, it might mean the OS offers a censorship interface.
At least we seem to agree the solution lies with better tools for parents.
Okay, but 6.1 is still from December 2022. Like... it's an improvement, but as my desktop sits at 6.19 and 7.0 is impending, I have to question why they lag so much.
OP was talking about that they now have and pursue the intention of upgrading the kernel during the lifetime of the device.
Instead of device launching with LTS kernel, which is supported for many years upstream, and always using it, instead LTS kernels are supported for 2 years (or extended like here), and the devices keep moving on to the next lts branch during their lifetime (usually not immediately, but after the regressions fixed for next branch, tested well before that in avf VMS etc)
I'd wager that's more likely due to Windows than the hardware. Like sure the hardware does play a part in that but its not the whole story or even most of it.
My C++ projects have a python heavy build system attached where the main script that runs to prepare everything and kick off the build, takes significantly longer to run on Windows than Linux on the same hardware.
Afaik a lot of it is ntfs. It’s just so slow with lots of small files. Compare unzipping moderately large source repos on windows vs. POSIX, it’s day and night.
A big part of it is that NT has to check with the security manager service every time it does a file operation.
The original WSL for instance was a very NT answer to the problem of Linux compatibility: NT already had a personality that looked like Windows 95, just make one that looks like Linux. It worked great with the exception of the slow file operations which I think was seen as a crisis over Redmond because many software developers couldn’t or wouldn’t use WSL because of the slow file operations affecting many build systems. So we got the rather ugly WSL2 which uses a real Linux filesystem so the files perform like files on Linux.
I don't know about ugly. Virtualization seems like a more elegant solution to the problem, as I see it. Though it also makes WSL pointless; I don't get why people use it instead of just using Hyper-V.
Honestly, just cause it's easier if you've never done any kind of container or virtual os stuff before. It comes out of the box with windows, it's like a 3 click install and it usually "just works". Most people just want to run Linux things and don't care too much about the rest of the process
reply