2026-11-02 10:59:42
More images I save from sites thesedays don’t end up showing thumbnails in file browsers. For example, Dolphin on KDE:
And the Finder on macOS:
Why is that? I assumed maybe the embedded thumbnails were getting corrupted somehow, or there was a resource fork issue saving images on my OpenZFS volumes over Samba.
No, turns out it’s much simpler than that. Browsers are getting the file extension wrong, as is the case with this tea photo:
$ file floejt-black-tea.jpg
==> floejt-black-tea.jpg: ISO Media, AVIF Image
Another common one is webp:
$ file ipmi.jpg
==> ipmi.jpg: RIFF (little-endian) data, Web/P image, VP8 encoding
What I suspect is happening is web servers and browsers are negotiating supported file formats, and the server is delivering an alternative format to save bandwidth, but the browser is still saving the file with the original JPEG extension. Hence the mismatch.
Interestingly, it doesn’t happen all the time. Some images I download are saved with the correct extension, even if the image in the page source is listed as JPEG. Maybe it’s a race condition?
By Ruben Schade in Sydney, 2026-11-02.
2026-11-02 05:49:12
I can’t remember if I told the story before, but in the Before Times™ I opened a trading account with CommSec, the public brokerage associated with Australia’s largest bank. Or I tried to, at least. After registering, I got an email welcoming me to CommSec, in which they referred to me by my full name. Except, it had a problem:
Welcome, Ruben Middle Schade.
Just in case it’s unclear, my middle name is not “middle”!
I thought it might have been a mail merge issue, but I logged in and confirmed my name was listed as “Middle” everywhere. Likewise, every piece of correspondence in print and email referred to me as such.
How did this happen? I had a few theories:
I absent-mindedly wrote my name as “middle” on the signup form, which slipped through.
A system internal to CommSec transcribed my name incorrectly. I have family and friends who work in finance, and it’s surprising how many manual processes are still involved.
Cocaine’s a hell of a drug.
Number (1) seemed more likely at first, so I was ready to blame myself. Except, there are systems that are supposed to catch such mistakes. Signing up to a new financial account in Australia requires 100 points of ID. These documents clearly, and unambiguously, refer to you by name. If I did write my name wrong, how did CommSec’s systems not flag this obvious discrepancy between that mistake and my real name, and immediately fail to activate the account?
To be crystal clear, “Middle” wasn’t listed as my middle name on any of my provided documentation, yet their identity verification erroneously matched them, and proceeded to create the account. That’s… more than a bit worrying. I’d blame people using “AI” for this mistake in 2026, but they didn’t even have that as an excuse back then.
So what about option (2)? How likely was it that I failed verification, but that my account was created in their system anyway? Or was it a transcription error? Again, I find both of these difficult to understand.
As for option (3), I wouldn’t dare cast stereotypes about people who work in a specific industry. This was merely a joke, like listing someone’s middle name as “Middle”, then verifying it against documents where the person’s name isn’t “Middle”. That’d be funny.
What proceeded felt like a comedy of errors. I enquired to CommSec asking if I could change my middle name to… my middle name. I expected this to be easy, because it was such an obvious mistake. That was on me.
Their support team rejected my initial request, telling me I’d need to request a “change of name form”. I objected, because I wasn’t “changing” my name, I was correcting a mistake with my real name. But fine, I downloaded the form, completed it, and returned it with a cover letter explaining the bizarre situation. CommSec’s system denied the request, citing insufficient evidence for my name change.
I wasn’t changing my name, I was fixing my name! GAH!
I’ll admit at that point I lost interest, and went with another broker. This turned out to be a fateful decision, because I ended up paying much lower fees, and I got access to some foreign markets. The capital gains from these investments were instrumental in Clara and I buying our first home. So, thanks CommSec! I think?
Every month or so since, I’d receive a newsletter from CommSec advising me of market conditions, and new features I couldn’t use. This was quite funny. But it wasn’t to last:
Dear Ruben,
We are writing to let you know that your account(s) will be closed, as they have no holdings or balances and have not been used to transact for an extended period of time. These accounts may have been opened directly with CommSec, CommBank, or with one of the brokers CommSec has acquired. Please note that your account may be suspended prior to closure.
As part of this account closure process and in accordance with ASX Settlement Operating Rule 7.1.11(a) and CommSec’s Terms and Conditions, we are also formally notifying you of the termination of your CHESS sponsorship agreement.
Goodbye, Mr Middle, we hardly knew ye.
By Ruben Schade in Sydney, 2026-11-02.
2026-11-01 05:20:50
Last Wednesday I asked if it was time to get into domestic LTO. I reasoned that with the growth in slop-fuelled demand for hard drives and silicon, enterprise tape backups were interesting and potentially viable again, even in a residential or homelab setting. I also not so subtly implied that even if this wasn’t true, I like tinkering with different tech.
The response on Mastodon and in email was surprisingly supportive of the idea, acknowledging that its trade-offs were offset by having airgapped backups on a dependable medium that hasn’t seen prices skyrocket; at least to the extent other storage mediums have.
(Usually when I talk about any tech at all, a loud chorus will approach me telling me why it’s terrible and Here Be Dragons. I also had two people explain to me what LTO was, despite the fact I explained I had commercial experience with it. I guess some people like explaining things).
Less than a week after I posted that, Nick Indge over on Ars Technica caught this Fujifilm press release:
TOKYO, October 29, 2026 - FUJIFILM Corporation has decided to invest approximately 10 billion yen at its Kanagawa Factory, Odawara Site to increase its production capacity for data storage magnetic tape by approximately five times. The investment will strengthen Fujifilm’s stable supply system for magnetic tape in response to growing data archiving demand accompanying the spread of generative AI.
Magnetic tape can store large volumes of data over long periods at low cost and can also be physically isolated from networks.
As an aside, Odawara? One of my favourite cities in Japan!? I wonder if they do tours of their tape facilities, and/or give out free samples (cough)?
That’s decided then, Clara and I are going to give it a shot. Watch this space.
By Ruben Schade in Sydney, 2026-11-01.
2026-11-01 05:16:29
Writing this post was a journey. It was turning into one of the longest I’d ever written. In the end, the process of writing it lead me to conclude that the entire exercise was a bad idea, so I’ve reduced it to the stub you’re reading now.
NFS is sufficiently broken on the Mac that it’s not worth using. Stick with Samba.
I’ll be adding more notes onto our family wiki if you really want to try, but I can’t recommend it.
By Ruben Schade in Sydney, 2026-11-01.
2026-10-31 20:04:30
I don’t think I’ve ever talked about this before, but there was a time in the 2000s where I used a Swedish keyboard. Apple used to offer a range of different keyboard options at checkout (at least in Singapore), and I chose Swedish. It had dedicated diacritic keys, and it was easy with the right Option key (known as Alt Graph elsewhere) to type accented letters. I thought it was awesome.
Thesedays I’d sooner reach for a Japanese layout if I were to ditch ANSI, but I’m also intruded by the Finnish layout. It seems to be a superset of every variation of Latin letter I could conceive of using. Well, other than Vietnamese, which I’m increasingly wanting to write too. Hmm!
The other question would be what mechanical keyboard PCBs and keycaps would support such layouts. I benefit from ANSI being the “defualt” in most keeb stores, but I’d need to build some variation of ISO board if I were to build my dream superset Latin layout.
By Ruben Schade in Sydney, 2026-10-31.
2026-10-31 07:05:42
Cryptocurrency exchange Binance has suffered the largest hack in the sector’s history, with attackers attempting to steal $US6.3 billion ($8.9 billion) in digital funds this morning.
Remember when we were told crypto-“currency” would solve fraud? It’s an immutable ledger, folks!
By Ruben Schade in Sydney, 2026-10-31.
