You do need HTTPS to protect mundane content: Saying otherwise is very short sighted...
You might not care about the content, but the way someone, somewhere, is accessing it, does offer a lot of "value".
It can allow a watchful eye to either accuse the reader of being outside the norm, criminal, not respectful and whatnot (reason why librarians fought hard for the right to lend books without giving the list to the state!) or allow them to caracterise, profile, target a person over time for many different reasons.
Thus everyone should have the to right to read anonymously and willingly.
Witholding this right from others is being complicit with opressors.
Encryption has a cost, it isn't free. It increases CPU utilisation and power consumption. It interferes with caching and reduces network efficiency.
This is a dumb idea. A very dumb idea.
Yeah, not so much for permeation, maybe, but they still quote this as one of the things that help. Could maybe do some for actual leaks - but getting air in would be sad too. The big reason for lower pressure is the lower resistance though - I like paying less in power&cooling thanks to lower power use to keep the platters spinning.
Clever materials choices and lower pressure than on the outside (~40% IIRC). Luckily leakage is easily measured in the product design and testing phase, as well as ongoing QA. So not nearly as much risk to your data as stupid firmware bugs that only turn up under some circumstances after lots of usage. And no, they won't be refillable.
By FOSS do they mean dump the source after release... like Android?
I don't think that's the spirit, even though the licence says so.
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson