I recall those things used to be tied into pocket. I’d look into it, they are probably still curated by the pocket team.

That info is a mess, and doesn’t really apply to the topic. It’s also misleading.

The root of the word afaik is found in exactly one word each of the three relevant languages: “deutsch”, “duits”, “dutch”.

“deutsch” is german and means german.
“duits” is dutch and means german.
“dutch” is english and means dutch.

So if you literally translate “dutch land” using their closest equivalents based on word history into any germanic language, you will obtain “german land” i.e. germany.
No idea what english was doing here, but every germanic language can agree the word-family of dutch should have it mean german.
Maybe the netherlands were the only relevant country to england so they just called those particular duitsmen the only duits and then had to replace the original meaning of the word with german when duits was changed.

Either way, the etymology of the word “þiudiskaz” is definitely not the reason the dutch are called that in english, the reason for that must be in english itself probably in the last 500 years somewhere. It is a uniquely english and relatively modern phenomenon, forming the meme of this post since it neither makes sense nor matches and of the actual nations or native languages involved.

I’m talking about persistent outages, that can remain for minutes or hours if you don’t move out of the affected area.
The setups shouldn’t cgange channels, both because they are a large commercial setup and because there is no other interference in some spots.
The dead zones are persistent over years in some spots.

If you have anything larger than a home installation you easily get some horribly mistuned antennae that let phones receive wifi but don’t catch the response at the same dbm, leading to phones hanging in their now broken wifi when walking out, or repeating connection attempts when walking in.
I had to block the wifi of my university for that, as it would regularly drop my internet if I went past any of their buildings. Also made me disable wifi calls

Diminutive denomination?

Already did, sry op.

I could do a script if I knew what I was gonna do ahead of time, or would write one later if I was gonna do it more often.

A variable in the shell is fine, but I still have to skip over it to change the first command, it still breaks up the flow a bit more than not having that "$file" in there at all.
Also if I interrupt the work (or in this case have to let it run for a while), or if I wanna share this with others for whatever reason, I don’t have to hunt for the variable definition, and don’t run any risk of fetching the wrong one if I changed it. Getting by without variables makes the command self-contained.

And it still maintains the flow of left to right, it’s simply easier to take the tiny well-known packet of cat file and from that point pipe the information ever rightwards, than to see a tail, then read the options, and only then see the far more important start of where the information comes from, to the continue on with the next processing step.
Any procedural language is always as left to right as possible.

If you really want to avoid the cat, I have yet another different option for you:
< /dev/nvme0n1 strings | grep -n "text I remember"
< /dev/nvme0n1 tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
< /dev/nvme0n1 tail -c -123456789012 | head -c 3000 > filerec

This ofc you can again extend with ${infile} and ${recfile} if the context makes it appropriate.

It makes the command easier to edit here. Put the various forms across my use next to each other and it becomes apparent:

cat /dev/nvme0n1 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec

compare that to

strings /dev/nvme0n1 | grep -n "text I remember"
tail /dev/nvme0n1 -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
tail /dev/nvme0n1 -c -123456789012 | head -c 3000 > filerec

where I have to weave the long and visually distracting partition name between the active parts of the command.
The cat here is a result of experiencing what happens when not using it.

Worse, some commands take input file arguments in weird ways or only allow them after the options, so when taking that into account the generic style people use becomes

strings /dev/nvme0n1 | grep -n "text I remember"
tail -c -100000000000 /dev/nvme0n1 | head -c 50000000000 | strings | grep -n "text I remember"
tail -c -123456789012 /dev/nvme0n1 | head -c 3000 > filerec

This is what I’d expect to run across in the wild, and also for example what ai spits out when asked how to do this. You’ll take my stylistic cats over my dead body

Oh right I misunderstood.
I didn’t do that because I was planning to switch out strings in that line. First inserting the tail and head before it to hone in on the position, then removing it entirely to not delete “non-string” parts of my file like empty newlines.

cat /dev/nvme0n1 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec

This would be the loose chain of commands I went through, editing one into the next. It’s nice keeping the “constants” like the drive device that are hard to type static. That way mentally for me the command starts only after the first pipe.

I don’t like to use < in combination with pipes, I find it harder to read. One is left to right the other right to left, and < is also just plain weird in its specifics.
cat is a stylistic choice avoiding needless notational complexity

Last time I deleted a plaintext file I just grepped for it.
cat /dev/nvme0n1 | strings | grep -n "text I remember"

Had to hone in on the location with head -c and tail -c after I found it, then simply did a cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec and trimmed the last filesystem garbage from the ends manually.

They’re copying spacex

It is likely some endless loop pinning a thread of the app at 100%. I’ve seen it happen in the past, though not for a long time.

Do you have the device rooted? That’d let you run an htop in termux in split app mode together with summit, so you could see exactly when the load starts.

Efi spec states it must be safe to delete all variables. It’s only motherboards not adhering to the spec that are affected, effectively faulty hardware.
If you do this on a mb from that era chances are nothing will happen, and if something does happen chances are it is recoverable. You’d have to have some truly bad luck on your choice of mb to have it be permanently bricked by that.

Isn’t that usually done with time difference objects? Either you subtract two datetimes, or you take one datetime and one length of time.

What does iso notation offer here?

Good thing is that iso8601 is so monstrously complex with so many obscure formats you probably don’t want anyway, that you’re better off following another standard.
HTML has a set of allowed formats for example that includes parts of rfc3339 and of iso8601, but also stuff like the ‘most basic’ “yyyy-mm-dd hh:mm:ss”, which is neither in rfc (which requires a trailing Z) nor in iso (which needs the T).

You can modify your system date format to iso, then it works.

Either by modifying your locale files, or by using one of the few locales that use iso, like en_SE. You can set this only for time strings by using LC_TIME (kde supports this in its settings graphically).

Allowing both T and space

I think those require a “vor” and “nach” respectively.
“viertel zwölf” seems to reliably mean 11:15 unless maybe it’s a casual shortening both sides are aware of. If you go to a random person and tell them viertel zwölf they probably won’t understand, but if they do they should think 11:15.

“viertel zwölf” (quarter twelve) = 11:15
“viertel vor zwölf” (quarter to twelve) = 11:45
“viertel nach zwölf” (quarter past twelve) = 12:15

Online geht gegen (viel) Geld, die wissen schon was sie tun.
Offline kostet die zwar mehr, erhält schnelle Auskunft aber als Einkommensquelle und wimmelt die meisten von der kostenlosen Auskunft ab.