463 karma · joined May 4, 2021
I still keep the images disabled, though. In most cases, you don't care about what's there in the images anyway.
Happy Thursday to you, too.
Argentinian fans during Qatar's FIFA World Cup 2022 using a shopping cart as a barbequeue grill.
A friend of mine had stolen one with his brothers back when we were in primary school. But stores here simply have a guard on their parking lots to prevent people from taking the carts away - haven't seen any tech for that.
I wanted to do the same for the two local newspapers I read, but I think they have Github Actions blocked so the script can't reach them. And I didn't bother to search for a workaround.
Making things slow again is a good anxiety countermeasure.
Also: I built the thing, so maybe I should fix it some time.
Next (good) thing they build will probably have greater adoption, due to less fear of "they'll kill this in two years anyway".
Source: https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6 (discussed here https://news.ycombinator.com/item?id=19798678 )
Encrypting YAML files' values may be handy for another project - will take note of it.
ejson2env sounds nice. Don't like the syntax of `eval $(...)`, but it does THE thing that most don't - it encrypts the secrets at rest!
Also, I have multiple logins for some services (company account vs company's client account), so separating concerns is cool. And having the "context" name in the PS1 helps avoid issuing the wrong command on the wrong account - you can even add emojis to the name for maximum discernability.
I never want to run the server's vi[m]/emacs/nano if I already have my own local one completely set up. I don't want to run the remote's bash - I have mine already customized! I want to open a new tab in my terminal - and have it connected to the remote, as if I opened a new tab on the server's terminal.
It's the remote's files and process tree and resources what I want to interact with - but I'd rather leverage my local settings as much as possible.
One day later, did you succeed in that?
That's even more true now than back when the article was relevant.
Respect, man.
Here are previous discussions for each part: I. https://news.ycombinator.com/item?id=37709284 (345 points, 188 comments) II. https://news.ycombinator.com/item?id=37728849 (55 points, 2 comments) III. https://news.ycombinator.com/item?id=37801150 (212 points, 106 comments) IV. https://news.ycombinator.com/item?id=37907482 (57 points, 11 comments)
I went that route since reading the CLI parameters was something I needed to do, but wasn't actually part of the issue I was trying to solve. I could have spent a few cycles of googling+testing+fixing/refactoring, but it was a trivial task (that I didn't remember how to do off the top of my head) and would have distracted me from the main task.