892 karma · joined July 17, 2013
[ my public key: https://keybase.io/gimpf; my proof: https://keybase.io/gimpf/sigs/x1O5qTA0VFF1CiB4RO-m8o_NQJ23q_gO7Uz0LVRJpHw ]
For instance:
$ echo -e "\033]0;${USER} is an unfriendly person\007" > test-file.txt
Then, many days later: $ cat test-file.txt
will change your terminal title.With less, you _can_ interpret escape codes, but usually you don't, and I consider this the correct default.
> In November of 2019 we will stop allowing new account registrations through our ACMEv1 API endpoint. Existing accounts will continue to function normally.
> In June of 2020 we will stop allowing new domains to validate via ACMEv1.
Edit: I usually don't care for portability, and just use bash. Shell is so ugly already, I refuse to write my personal stuff in portability hell mode. Rather level up my Civilization skills instead.
Except for stories about total engineering fail or borderline fraud, nowadays I couldn't imagine any stories being told about about manufacturing in Germany, US or China.
But more to the point, good quality bread has been more ingrained in the culture of several (but not all) European countries than in the US, and while the wheels are turning, it seems to take some time.
About your situation: I've to admit that I don't know about keeping bread well in such bad conditions. I'd try a slightly more sealed container, or if that doesn't work, slice and freeze it fresh. Other than that, find uses for dry bread (works perfectly fine in soup, or if white bread, make breadcrumbs etc. etc.).
20% rel. humidity is so low that it is very uncomfortable for humans, even unhealthy for some people. Are you really sure that's your in-house humidity? Outside/inside are often very different, due washed clothes drying, cooking, plants, respiration, and also humidity from the cellars in some buildings.
If yes, and if possible, I'd recommend an air humidifier to get that up to 40% or so. Depending on volume, a $60 unit should be able to do this, even if it will take three weeks until the humidity slowly approaches sensible levels.
And you get that already for the cheap units.
So, it's a freezer, it freezes, and it doesn't send a post to Facebook. The only complaint I would have is their loudness. Modern extra-slow compressors are often (perceived) louder than previous-gen units.
Also: given that even DIY ovens usually start with "get a cheap PID controller from e-bay", I doubt that commercial ones use anything else.
also, tax-evasion and tax-reduction are two different things, equating them is an argument in bad faith
I don't have a dog, so didn't save the link, but for dog caretakers some literature review might do good (also, maybe consensus improved since then).
EDIT: obviously that doesn't necessarily translate to modern dry food.
As with most paradoxes, it's about how a seemingly innocuous question turns out to either be underspecified to have an answer, or tricks even the mind of mathematicians to assume too much.
Here it's about what it means to have a "random chord of a circle"; several simple ways to generate random chords lead to very different results, but true randomness should not be easy distinguishable from other true randomness...
E.T.J's solution to invoke the maximum ignorance principle to require any source of random chords to be size- and translation-invariant (because those dimensions are not specified in the problem) seems elegant.
Now, comparing to orbits, or to balls on a train, the thing here is: all these different viewpoints, although very different, do lead to the same result. Even if you calculate stuff; and if I'm not mistaken, that's because of relativity (Galilean relativity should be sufficient for the train example to work, the more modern ones for the rest).
Yes, nowadays we hook into React components themselves, or even if not we can use those frameworks to strongly simplify writing selectors, because testing libraries have some magic built into them to use the component hierarchy directly...
... but depending on the amount of legacy and old in the app (and there will be legacy, and old stuff), and how strongly E2E you want to go (like "survive adding stuff from our team in that other city"), a "nav ul li[id='something']" will work ok for the developer maintaining the code, even if it is not the shortest possible selector; whereas a "div[...] div[...] div div + div" will catch up with you, even if you think you abstracted it away.
After having been burned w.r.t. security updates by Samsung, then Motorola, and now Nokia, I'm more or less done with Android (once I have enough money to ignore the wasted Euros...).
It seems only people able and willing to spend 500+ Euros every year deserve basic security on Android.
not amused
Law is, after all, what gets executed, and debating whether it's right or wrong is a luxury you don't have when it's executed on you.
There was an article recently, describing a very important, and also very common, "exception":
If you want to schedule/synchronize real-world appointments/events, you need both the _local time_ and the political zone, like 2018-12-11 9am at Europe/London.
The reason is that between time of entry and time of event, the defined timezone for that area may change. As a result, your previously translated appointment would not match up the local time.
Which is bad, because humans, when meeting, or events, when being announced, announce the local time. Not UTC. And they stick to the local time.
as an example, many parties now feature some feminist points, even though it was originally against their ideology.