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.

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.

Considering that reading source code can take a long time

You’ll get faster over time, until reading code is faster than reading documentation, as code will always represent what’s truly happening, while docs are frequently outdated.

In a language the user isn’t familiar with

If you’re not that familiar with the language, it’s likely you won’t be contributing to the project. Open source projects usually to have quite limited resources, so they tend to optimize docs and dev UX for people who are likely to contribute.

Hey, have you ever met Taylor Swift? I heard she gives great IT security advice over at https://infosec.exchange/@SwiftOnSecurity

If you’ve got 14 billion years, a theft takes a minute, then you need 53 recursion levels of binary search to find the moment of the theft. (14 billion years can be split into about 7.3e15 1-minute segments, 53 levels of binary search allow you to search through 9e15 segments)

That means OP assumed that it’d take 1 minute to decide whether at a certain still frame the theft had already occured or not, to compute the new offset to seek to, and the time it’d take to actually seek the tape to that point.

Not an unreasonable assumption, but a very conservative estimate. Assuming the footage is on an HDD and you’ve got an automated system for binary search, I’d actually assume it’d take 5 seconds for each step, meaning finding a 1min theft on 14 billion years of footage would take 5 minutes.

I don’t have that sense either. Food, no matter how much I’ve already eaten, still tastes so incredibly awesome that I just want to continue eating. I only stop once there’s nothing left, which is why I cook every meal myself to be able to control portion sizes.

He also uses his own http server that in turn queries the ldap server solely for the articles. The rest is compiled into the http server binary.

Ah, you met fefe.

Tbh, das meme hat mich auch ziemlich gestört.

Often enough, the old code is so badly intertwined that it’s impossible to actually test. Those are the moments where all you can do is nuke it from orbit.