I tried installing Guix System maybe about a year ago, but had problems with LVM on LUKS with full-disk encryption and missing and outdated documentation. Has this situation changed?
I haven't done that setup but I know various people that use Guix (on the IRC channel) have an encrypted setup. I'm not sure their exact file structure, but it in general full disk encryption is supported; any issues should be bugs. You can always ask on the IRC channel to get a feel of what people have done and anything that might be tricky.
Question from a welfare country and complete ignorance: what exactly are the steps necessary to change this and why is it so difficult for the USA to take them?
Before I got my Happy Hacking I had both control and escape on caps lock, but with HH, I have no problem using the default escape, which is closer there than on regular keyboards.
The free option: use your smartphone's flashlight and try to spot unnaturally bright / colored reflection.
If you want to spend some money and don't mind carrying an extra device: probably any of the "hidden camera detectors" on the market will be at least somewhat useful. K18, CC308+, etc.
We're trying with our work to get better or at least equivalent results without having to use external devices.
I don't think this works, mainly because an extremely bright external source of 850 nm light looks incredibly suspicious through the sensor (as we expect the ToF sensor to be the only light source). We could add that check in explicitly.
I think the bright light is intended as a countermeasure to the hidden camera, not as a countermeasure to finding the hidden camera.
Basically, to keep position X unobservable through the hidden camera, ensure that there is an overwhelming source of photons between position X and the hidden camera.
Since we don't know where the hidden camera is, the best we cam do is to assume that the immediate vicinity of the bright light will accomplish this.
Oh, I must have misunderstand, since the root comment was talking about detection methods. But yes, jamming is a good option, and there have been papers to make areas "unrecordable". I don't have my citation manager on hand now, but I think it was an early ACM Sensys / Mobisys research work.
I tried Matrix a few months ago, but the clients were pretty horrible compared to irssi. The only functional one was the ugly GUI one with emojis and all that.
I've tried a lot of very functional clients. I suppose you think of Element? There's also Cinny, Hydrogen (both web), Fluffychat, Nheko, gomuks. Maybe quaternion is more to your taste? Not sure if it supports E2EE.
Weechat-matrix-rs[1] is the fix for that, but it's not currently usable (I tried it yesterday, hard crashes trying to log in to a local homeserver). Maybe in a few more years.........
I was assuming they have something equivalent to the Intel Management Engine. Do they not?
> Isn't any hardware a "potential" hardware backdoor?
I don't know. Is this true of open hardware? I mean, there could be a backdoor, but it would also be practically possible for qualified people to find it, right?
I think their main reason is that Apple is a hardware company. They think of new features, build hardware for them, and then tweak their software (OS and applications) to aggressively use that new hardware.
Supporting older hardware is extra work that doesn’t bring in extra money. Also, oftentimes, it isn’t possible to backport features in a performant way (a lot of the ML stuff would only crawl on 10 year old hardware, features such as Handoff and PowerNap require hardware features). End result would be a 20 year old machine that runs the OS, but doesn’t work with modern software.
That wouldn’t make customers happy, and would dilute the brand of their OS releases.
I have a macbook pro late 2013 with a retina display, i7 cpu, 16gb ram and 512gb ssd that doesn’t get monterrey. I am not very happy about it, it’s a waste
Apple always drops software support for hardware when they stop providing hardware repairs. They generally consider hardware “vintage” 7 years after its introduction, but sometimes make that longer. They drop support in new macos releases only but they keep shipping updates to the two older releases as well. This means in practice hardware gets about a decade of software support, and the last two years of that without new features. Since the reasons for dropping support usually aren’t hard technical limits the community makes patchers to put new macos releases on older hardware.
To my knowledge Linux has never worked well on intel macs with a T2 chip. Asahi linux is working on bringing good support to m1 macs, so it looks like for good linux support you either need a pre-T2 mac or a post-M1 mac.
Linux would also require drivers to be recompiled for a new kernel. This is not an option for most proprietary drivers for products long abandoned by the manufacturer.
For the more common and popular hardware there is a good chance that open source drivers can be maintained by the community but if your laptop relies on a somewhat obscure chipset or microcontroller then your mileage will vary...a lot. Look up "Intel GMA500 Linux driver" if you need an example of the pain.
Sometimes the decision could be entirely commercial. Most notably, OSX dropped support for all nVidia GPUs from Mojave onwards despite nVidia going on record saying they are happy to continue providing drivers but Apple won't sign them.
> Most notably, OSX dropped support for all nVidia GPUs from Mojave onwards
Not those shipped with Macs. The GeForce kexts to support the NVIDIA GPU gens that Apple shipped, Fermi and Kepler, are still present even on Monterey.
macOS sees quite a lot of change under the hood from release to release that can make bringing unmodified drivers forward impractical. For example, in recent releases there’s been a push to move drivers away from the kernel and into userspace, which is naturally going to break old drivers. 32-bit support was also dropped not too long ago, which broke old 32-bit drivers.
but I'd be delighted to see a happy-hacking style layout, where the arrow
keys are consigned to the fn layer (which should be configurable; the whole
keyboard could be configurable by qmk). It would also be nice to see an option
where the trackpad is replaced by a foldable joystick. Maybe this way
one could get rid of the split (arrow) key and the short f keys and the
short escape. Think of the vi users.
