minor nitpick, but it's not ownership so much as location. Sometimes the ISP will own the equipment, but it will be located on the customer premises rather than the ISP premises. It's an important distinction as you can't just rock up and do stuff to it.
Estimating entropy is challenging because it's a reverse process from how it ought to work. I created https://phrase.shop, which generates passphrases with a known quantity of entropy. Hover over any of the three action buttons to see exactly how many bits of entropy will be used to generate the passphrase.
Not sure how much I like this. With this algorithm, the user would never see 100% displayed, because at that point the UI would change to remove the progress bar entirely. Whereas seeing 100% feels oddly satisfying, even if inaccurate.
Many TUIs (text user interface) with multiple operations will show one bar reach 100% and move onto the next process (or show multiple in parallel).
If the UI automatically transitions to a totally new screen after completion, I'm never going to see 100% anyways, unless the app does the exact infuriating thing in TFA, which is render 100% (at 99.whatever) and then do some fsync/cleanup and actually be frozen showing 100% which is the contrapositive of oddly satisfying, it's unsurprisingly unsatisfying.
This is great in that it creates a grammatically correct sentence, which really helps with memorization, and which is lacking in many other "passphrase generators" that are simply sets of disconnected words.
Though password managers are useful, they don't obsolete memorization! At the very least, you need to memorize your password manager's master password. I also don't put extra-sensitive passwords in my password manager, such as for my email account, laptop OS, SSH key, employer enterprise account, etc. I probably have about ten passwords / passphrases memorized, and I don't think this'll ever reduce.
To scratch my own itch, I created https://phrase.shop, which also generates grammatically correct phrases (not full sentences though), minus the insults. Hopefully you find it useful too!
It's similar to a multitude of languages targeting the Java Virtual Runtime (JVM) -- functional, imperative, object-oriented, actor-based -- whatever you want, but they all produce interoperable bytecode.
I am not the OP, but I believe he's referring to the ability to be logged in to different AWS accounts simultaneously. Without containers, logging in to AWS account B would invalidate the tabs where you're already logged in to account A.
It’s a Neoverse N1 architecture, whereas the new Gravitron is Neoverse N2.
It is an E-ATX form factor, and I can’t tell whether the price makes it a good value for someone who simply wants a powerful desktop rather than ARM-specific testing and validation.
> The way the US does it (especially detecting if a train has not been separated along the way by using a caboose/end-of-train beacon) may cost less money, but would be viable to such issues.
Detecting separation doesn't rely on the end-of-train device. The EOTD only helps with this by 1/ helping activate the brakes twice as fast by detecting loss of pressure on its end and opening the brake valve, and 2/ sending periodic status indication via radio signal to the locomotive so the crew has more visibility into what the pressure is and whether the tail of the train is moving.
