Although the imagery is spot on the date should be more like 1200 BCE. The Trojan war was a Bronze Age affair which was a long time before the Classical Greek period, which is where 350 BCE falls.
Yes, this is what I think of when I think of a "dead man's switch". It relates to the concept of a physical device that deactivates or activates if you let go of a switch, like a light saber for example.
I think an interval of weeks would be more convenient than hours to avoid false positives. But I think Patrick Stewart's character did daily check-ins in the movie Safe House. The dead man's switch was actually the central plot point in that movie.
I would install a systemd user service with the setting Restart=always. If your window manager is started with systemd, or defines a systemd target you can configure the waybar service to start and stop automatically with the window manager.
Yeah, the first thing I do when I log in is restore my Firefox session, which includes several windows with quite a lot of tabs. I also use the Auto Tab Discard extension so I can keep lots of tabs in my workspace without having all of them loaded all the time.
Yeah, I'd like to be able to set my kids up with Bedrock because that's the version most other kids play, and it would be great for them to be able to play on servers together. I have run the Android version on Linux in the past using a community launcher, and it worked flawlessly with a mouse and keyboard. But I think there was an authentication change that prevents that from working anymore. It's very frustrating that they have a Linux version, but they just won't let us use it.
Yes, I use passphrases for stuff like my password manager, my computer login, and my disk encryption. For my login (which I type a lot) it's four words; for occasional stuff like disk encryption it's six. I'm sold on the argument that a passphrase is way easier to memorize compared to a comparably-secure random password.
The number of possible passphrases is the number of words in the dictionary you use to generate passphrases raised to the power of the number of words in your passphrase (assuming a small chance of reusing the same word in a passphrase). I use this command to generate a random phrase using my stock OS word list:
grep -v '[^a-z]' $WORDLIST filters out words with apostrophes or other weirdness. On my system the filtered list is 77,866 words.
For four words, 77,866 ^ 4 ≈ 3.7 × 10^19 possible passphrases.
Compare that to randomly-generated passwords. I'll assume that random lowercase & uppercase letters, numbers, and symbols add up to 46 characters. The number of combinations is 46n where n is the length of the password. A four-word passphrase is the same order of magnitude as secure as a 12-character password, which has about 9 × 1019 possible combinations.
I'm sure that if you make up your own passphrases instead of randomly generating them then the security is much lower.
I find ngrok useful enough to pay for. When I want to demo some software I can run it locally and set up a temporary tunnel. When I used to have a VPS I would do this with SSH port forwarding, but I'm told that tunneling TCP in TCP can lead to some weirdness.
I used to have a dyndns subscription to get a stable domain name for my home router. It's kind of another way to do the same thing - instead of a tunnel I could forward a part.
That's great, but yours is not the universal experience since different tasks have different RAM requirements, even within the realm of programming. I had RAM shortages when I was running the Haskell LSP server and compiler at the same time on a largish project. Haskell's type checker does a lot more than other mainstream languages' which is how it delivers such strong correctness guarantees. You trade RAM for scrutiny. Then the LSP server has to be fast so it has to do a lot of caching, and you get an additional trade of yet more RAM for speed.
I've been using the newer commands like
switch
andrestore
for a while. But I learned a few things here that will indeed make my work easier.