I was assuming that was supposed to be a cassowary.
So strongly, in fact, that I missed the platypus tail entirely 😄
I was assuming that was supposed to be a cassowary.
So strongly, in fact, that I missed the platypus tail entirely 😄


I keep trying, but the clock only displays 4:29.
What do?


A great thought on the thumbnails, but the behavior exhibits even when using command-line tools.
Indexing is off for the entire drive, I can’t even begin to imagine what kind of mess that would make if it was on.


“Fun” fact: if you think it’s slow normally (and to be fair, it is), NTFS seems to have a pathological performance regression when a directory contains more than 10,000 children, any operations on files in that directory slow down by around 95%.
I discovered this on our CCTV system at work (that runs on Windows Server 2022), which creates an inordinate number of small files (each containing at most a few seconds of video). It was causing some of its periodic maintenance tasks to fail, as they’d take longer to run than than the configured interval between them.
Windows also really doesn’t like dealing with half-petabyte filesystems, just like… at all.


Using the phone as a touchpad has come in handy on a few occasions for me. Also just niceties like having your music on the PC pause automatically if you receive a call.
It should further be pointed out that it’s not even required that one end is a phone. You can connect your laptop to your desktop and share content between them just as easily.
Honestly, I’d consider it.
If I was in the middle of a job and was about to run out of something, I’m looking at downing tools for a minimum hour round trip to the nearest (decent) hardware store.
There’s a good chance someone starting closer to the store can get that down to 35-40 minutes, and I can carry on working in the meantime.
Now “normal”, perhaps not, but unreasonable also perhaps not?