No, unlock as in: You can install whatever operating system you want. No need for “jailbreaking” on Google phones. They officially support unlocking the bootloader (and re-locking it later as well!). There are many things not to like about Google, but how they handle their phones when it comes to openness is certainly not one of them. Pretty much all other phone vendors are much worse than that (except for maybe a few small ones like Fairphone).
How about not letting Google have exclusive rights to the drivers for all the phone hardware?
What exactly do you mean by that? Google is one of the few companies that let you easily unlock their phones so you can do whatever you want with them.
It’s on April 1st, but nobody takes it seriously.
There is also AMD and they are doing pretty well. I wouldn’t write off x86 just yet. But less competition is never a good thing, and Broadcom buying another company has never resulted in anything good, as far as I can tell. For anyone except Broadcom themselves.
It is, but Signal and Matrix aren’t really all that similar. Matrix’s privacy is pretty atrocious. It stores tons of meta data about users all over the place. That’s the exact opposite of what Signal does.
Ugh, Broadcom buying Intel would be terrible.
Sure, if you have exactly one client that can access the server and you can ensure physical security of the actual network, I suppose it is fine. Still, those are some severe limitations and show how limited the ancient NFS protocol is, even in version 4.
You need sampling at twice the frequency as a minimum to extract a time domain signal into the frequency domain. It says nothing about “perfect” especially when you’re listening in the time domain.
Yes it does. You can use a higher frequency, but that does not change anything except increase the maxiumum frequency possible. Even with perfect ears and the best equipment, there is no audible (and mathematical) difference to be had.
Everyone who claims otherwise should watch Monty’s explainer videos. I know they are quite old at this point, but everything he explains is still perfectly valid. If that does not convince you, nothing will.
It turns out that dynamic range is limited by the audio sampling rate and the human ear can easily detect a far greater range CD audio supports.
Dynamic range isn’t limited by the sampling rate. It is limited by the resolution, which is 16 bits for the audio CD. With that resolution you get a dynamic range of 96 dB when not using any dithering and even more than that when using dithering. Even with “only” 96 dB that dynamic range is so vast, that there is no practical use of a higher resolution when it comes to playback. I know that the human ear is supposed to be able to handle 130 dB or even more of dynamic range. The thing is, you can only experience such a dynamic range once, afterwards you are deaf. So not much point in such a dynamic range there.
There are good reasons to use a higher resolution when recording and mixing audio, but for playback and storage of the finished audio 16 bits of resolution is just fine.
NFS is bulletproof.
For it to be bulletproof, it would help if it came with security built in. Kerberos is a complex mess.
If someone compromises the host system you are in trouble.
Not only the host. You have to trust every client to behave, as @forbiddenlake already mentioned, NFS relies on IDs that clients can easily fake to pretend they are someone else. Without rolling out all the Kerberos stuff, there really is no security when it comes to NFS.
archival strength USB NVME drive,
Does such a thing exist? Ordinary flash storage is pretty bad at keeping its content when powered off for a long time, due to how flash memory works. I’d be curious about such drives.
Thanks, I think the risk here is that there may not be hardware to read it.
M-Disc DVDs are readable by ordinary DVD drives. So you could simply put a USB DVD drive alongside those backup M-Discs on the shelf.
The script appears to be missing the #! line. Without that, it is unclear which interpreter should be used for executing the script.
or a domain with a random string of characters so no one could reasonably guess it? Does it matter?
That does not work. As soon as you get SSL certificates, expect the domain name to be public knowledge, especially with Let’s Encrypt and all other certificate authorities with transparency logs. As a general rule, don’t rely on something to be hidden from others as a security measure.
When hosting this locally, I don’t see how 200 GB is much of an issue. Storage is so cheap these days, if you want to host it locally, just buy a 256 GB SSD just for that data for $20. Anyway, you were asking for a mirror, to which I replied with the information about the ZIM files. I don’t really understand the issue. Stackoverflow just isn’t that small, there is not much you can do about that.
I think it’d take a few hours to setup even a smaller copy of SO, which isn’t ideal for answering a quick question.
The download? Maybe, depends on your Internet connection’s speed. Actually serving it as a website certainly doesn’t take hours. It is rather a matter of seconds.
Then I don’t understand what your point is. A CPU on its own without a system isn’t of any use. Since there were no motherboards allowing you to use that much RAM, the point about the CPU supporting it is moot as far as I am concerned.
Of course they aren’t small, but they are probably as small as it gets, since they are pretty efficiently compressed. I am not sure what you mean by
it’s not a straightforward operation for even the average developer or systems engineer to restore these into a working format
since it is really trivial to use them. Just load them with Kiwix and serve them as a website. It doesn’t get much easier than that.
That’s not what you were saying. You were explicitly talking about Google. Also, implying it is Google’s fault that other manufacturers don’t let you install other operating systems easily is pretty bizarre. If you want to complain about that, at least complain about the right companies. Those are usually the phone manufacturers and/or the SoC manufacturers. The SoC manufacturers often times are particularily problematic, since they often do not publish open source drivers at all or in a very limited fashion.