You're absolutely right on that count. If you switch fast enough, everything has a capacitance. That's why with CMOS designs once you go above a few kHz you start worrying about fan out.
It's also why, once the ceiling is reached, everything starts using modulation tricks previously used in RF. Ethernet started with 1GbE, USB with 3.0, DSL did it from the start, with PCIe even gamers have probably seen eye diagrams in riser tests, and coax is the very definition of pushing RF over a wire.
Yes, of course there is error correction. Also, while the SSD is on power, it'll constantly go through all data and fix the areas that are starting to deteriorate.
But this does mean an SSD left without power will slowly lose data over months and years.
This also means that writing data is much slower and the SSD can handle far fewer writes. But the tradeoff is that TLC and QLC SSDs can handle 2× and 4× more data than MLC SSDs for the same price.
That's why MLC SSDs are primarily used for professional use and TLC and QLC is primarily used for gamers.
Some TLC and QLC SSDs even allow you to choose how much of the SSD should be used as SLC/MLC space (4× less data, 4× faster writes, 4× more endurance) and which part should be used as TLC/QLC (4× more data, 4× slower changes, 4× less endurance).
SSDs aren't just that simple. All of them have at least some SLC area, usually as cache, that's in base 2. But the rest of the SSD can be SLC base 2, MLC base 4, TLC base 8 or even QLC base 16.
And overall it's still base 2 because each SSDs pretend one block of base 4 is just two blocks of base 2, and accordingly they pretend a block of base 16 is just 8 blocks of base 2 storage.
ESS is a product built on top of a precisely tuned synapse with custom additions, but it's still synapse underneath.
Fdroid only gained the ability to auto update apps a while ago, so that's why you got that prompt.
Also, if the permissions an app requests change, fdroid can't always auto-update it.
In timekeeping, there are so called stratums to describe how correct a clock is.
Stratum 0 is a physical process, an inherent property of the universe. An atomic clock would be stratum 0.
Stratum 1 is a clock defined based on a stratum 0 clock. For example, GPS clocks are usually stratum 1, so are timeservers at universities with atomic clocks.
Stratum 2 is a clock defined based on a stratum 1 clock, for example, your router's ntp server if it syncs its time based on gps or a university's timeserver.
So if we adopt this jargon for units:
Meter is a stratum 1 unit, defined based on the stratum 0 properties of lightspeed and cesium resonance.
Inch is a stratum 2 unit, defined based on the stratum 1 meter.
You need to be able to have multiple nodes in one LAN access ports on each others' containers without exposing those to the world and without using additional firewalls in front of the nodes.
That's why kubernetes ended up removing docker support and instead recommends podman or using containerd natively.
There's no alternative for 0.0.0.0 and a firewall if you're e.g. using kubernetes.
That assumes you're on some VPS with a hardware firewall in front.
Often enough you're on a dedicated server that's directly exposed to the internet, with those iptables rules being the only thing standing between your services and the internet.
No. You can fix the dehydration relatively easily by just giving the person liquid intravenously.
But the primary way rabies kills you is liquifying your brain, which is independent of how hydrated you are.
It's not just office, SH and many other parts of the German government have been slowly replacing the entire O365 suite with OpenDesk, which is an open source product based on Matrix, Jitsi, LibreOffice, and a few other tools.
The goal is to have a fully integrated solution for calender, chat, calls, documents, cloud storage, etc.
My employer is developing parts of that solution and we recently switched our internal communication over to it, and tbh, it's working really well.
Now is the perfect point in time to do it, with the GDPR ruling regarding O365 and Microsoft fumbling the migration between old teams and new teams.