Category: Computers/Internet

Posted on
by

Sure, I like electronic gadgets. But I dislike planned obsolescence more.

It’s one thing when the newer model really is that much better. “All About the Pentiums” exaggerated it, but computer hardware in the 1990s really was improving by leaps and bounds. (And the software was devouring those performance gains, both in demanding more resources, and being less efficient as programmers were told to optimize for their own time, not for disk space or RAM.) That eventually settled out around the time smartphones and cloud computing started taking off, which is why I was able to run a 2012 model CPU all the way through 2024. A faster PC would have been nice, but I didn’t need one yet.

As I recall the tech industry freaked out when demand for new PCs dropped. There was probably a rash of “Millennials are killing computers!” articles.

But smartphones were going through the same kind of rapid improvement. You could easily justify buying a new phone after only two years: it was a lot faster, had a better display, had a better camera and more storage, and so on. And the carriers were happy to hand you a “free” new device to keep you on their service. Heck, if you really wanted (and could afford) to buy a new phone every year, you could make a case for it.

In that environment, you could kind of accept a company only offering 2-3 years of support for their phones.

Eventually that settled out too, and it takes longer for new phones to really be worth the upgrade. Of course the industry has tried to keep the pace going. If the hardware still works, and it’s still able to run the apps people want to use, there’s no good reason for the company to stop supporting it after only three. Especially with something whose main purpose is to be constantly connected to the Internet.

I have an Android phone from 2020 and a tablet from 2019. The tablet still works fine. (It’s great for digital comics, or PDFs that are pre-formatted for 8.5×11″ pages.) The phone worked until two days ago. (Technically it still does, but I don’t want to overload the already-swollen battery.) But they’re both unsupported. Not because the hardware has failed (up until Monday). Not, like the Poke3, because they can’t handle today’s apps. Simply because Google and Samsung don’t want to provide updates anymore. Not even bugfixes. Not even security fixes.

It’s maddening.

Especially with prices on new electronics skyrocketing due to the AI datacenter-driven RAMpocalypse.

There are many things I dislike about Microsoft, but I appreciate that they finally realized that a large chunk of their customer base can’t or won’t upgrade their hardware just to install Windows 11, no matter how they try to convince us, and has extended Windows 10 support twice with minimal hoops to jump through.

The Fairphone 4 (2021) that I pressed into service to replace the dying Pixel 5 (2020) is more or less comparable in terms of speed. I still need to experiment with the camera. But it’s still supported through 2028, meaning it’s safer to use online. Which, again, is what cell phones are for.

Blaugust 2026: My Posts

Posted on
by

I had a migraine this morning that really threw me for a loop. Then I spent the afternoon and evening dealing with a different kind of headache: getting my phone number transferred to a new(ish) phone.

We picked up a Fairphone 4 a few years ago as sort of a hedge in case the electronics industry and/or tariffs and/or international trade went bonkers and one of our phones died. (We weren’t expecting all three.) The teenager used it for a bit before we bought him a phone that was closer to what he actually wanted to use. So the Fairphone returned to the back bench, so to speak.

A cell phone held in a hand, showing the California DMV website. A bright magenta line is running vertically down the entire screen, including the status bar at the top and the onscreen buttons at the bottom.Today, a bright vertical magenta line appeared on my Pixel 5’s screen. I’d noticed it was running hot lately, and when I pulled it out of the case, sure enough it had started bulging.

I know it’s old. I’ve been trying to get as much use out of it as I can, which, well, I guess I have.

(Edit: added photo)

I do not like spicy pillows, Sam I Am.

So I reset the Fairphone and started setting up the most important apps: authenticator, password manager, stuff like that. And I set about unlocking the SIM protection on my phone number and got ready to call customer service.

I knew from experience that the Fairphone 4 works fine on T-Mobile’s US network, but their apps don’t know how to activate the e-sim. So I was prepared to talk someone through.

But because we’d been swapping back and forth between phones, the sim was still registered as attached to the teen’s number, even though the number is actually pointing to his current phone. It took over two hours (at least 45 minutes of that on hold) and three levels of escalation to first figure out that’s what the problem was, and then find someone with the access to fix it.

They did finally get it all sorted out, but it was not the way I wanted to spend my afternoon.

(And when I let the old phone cool off, the screen went back to normal, though it’s still bulging.)

Edge-on view of the phone showing that the glass screen is splitting away from the plastic case.

And to top it off, Nextcloud’s photo uploading has stopped working reliably, so I have to go through the last couple months of photos and make sure I have everything copied over. I went through some of them tonight, and need to get the rest…soon.

For now, I’ve turned the old phone off completely overnight.

Once I’ve got the photos transferred, I should figure out whether it’s worth repurposing the device with a new battery or just running it without one. And then dispose of the fire hazard.

Blaugust 2026: My Posts

Posted on
by

I host most of my websites on a DreamHost VPS*. This morning I discovered that a new file had been added, agents.txt, to the root of each site, on May 7.

It was easy to confirm that this is a new default file similar to the default robots.txt and favicon.ico DreamHost puts in every new site to get you started. Apparently they retroactively added it to sites that don’t already have one. So it’s a host action, not a hack. That’s good at least.

The contents are simple, and sensible for a new website: Discourage LLM training and actions, allow on-the-fly “AI”-generated summaries, disallow access to some common folders that shouldn’t be used for any of the above.

Though I am annoyed that they added it retroactively, particularly since it includes what looks like an explicit opt-in to retrieval-augmented generation, even if it’s something that’s happening already and less of a problem than a model vacuuming up your entire website for regurgitation. (Guess who’s already in Common Crawl!)

# Data use policy
Allow-Training: no
Allow-RAG: yes
Allow-Actions: no

# Default rules for all agents
[Agent: *]
Allow: /
Disallow: /admin/
Disallow: /config/
Disallow: /tmp/
Disallow: /logs/
Disallow: /backup/
Disallow: /.env
Disallow: /wp-admin/
Disallow: /wp-includes/

Harder to find was what else goes in this file. The first agents.txt spec I found used a completely different syntax and a completely different purpose. I had to search for the policy directives (in quotation marks) to find the proposal it’s implementing, which turns out to have been renamed as agent-manifest.txt shortly after it was proposed in March. Apparently whoever DreamHost didn’t get the memo before it rolled out. Update: As Patryk points out below, it’s changed again to agents-brief.txt, just one day after the blog post was updated with the second name. .

Good: sensible defaults for new sites.
Bad: rolled out to existing sites without notice, half-baked implementation.

*Update: To clarify, this is on DreamHost’s managed VPS service, where they handle the OS and the webserver, but you have a flexible userspace all to yourself. It’s a middle ground between shared hosting (where other sites are on the same virtual machine and webserver) and fully run-your-own-OS cloud hosting, and the balance generally works for me (YMMV).

Posted on
by

Amazon is shutting down their Drive service. “What Drive service?” you may ask? So did I. It’s a cloud drive like Dropbox or Google Drive, and I’d completely forgotten about it until I read that headline.

According to the FAQ, it was being used by apps for photo and video storage (I assume on Fire tablets) and those have all been moved to Amazon Photos (which I’ve definitely never used).

But something jogged my memory…not just of when Google moved all their Google Plus photo features over to Google Photos, but something else involving music.

So I looked. And it turns out I actually have some files on there after all:

Two folders.

One was “Archived Music”, all albums from 2011 that I’d imported from my CD collection. I’m not sure, but I think the service might have been integrated with Amazon’s online music player way back when, and when they disconnected them, I didn’t have anything else I wanted to use it for.

The other was “My Send To Kindle Docs,” and it was full of ebooks and PDFs from 2015-2016, most of which I recognize from Humble Bundles.

I guess I should look through and see if there’s anything I don’t have a local copy of anymore. That I want to keep, anyway.

Posted on
by

This looks cool: Mozilla has released a translation tool as an add-on for Firefox that can do web page translation locally instead of sending data to the cloud! It’s based on Project Bergamot and implemented in WebAssembly.

IMO translation is one of those things like speech recognition that ideally should have always have been local (for obvious privacy reasons), but the processing and data just wasn’t there yet when Google Translate and similar services launched.

Posted on
by

Two hot takes (so to speak):

Auto-updaters shouldn’t run when the system is really busy.

And installers that check to see the whether the same or newer version is “already installed” should either be really thorough about what they’re checking, or offer to do a repair install anyway.

Overheat!

I’d fired up a game of No Man’s Sky, which even after redoing the thermal paste and adding another case fan still pushes the limits of my system’s cooling, especially if I forget to wait for all the background processes to finish loading on Windows startup. I left a space station, landed on a planet, started mucking around with the structure I had found, and hit a waypoint pole to save again—

And the system shut down.

I turned it back on to get the fans running again and help cool off. Which worked. But when I logged in, I had a bunch of errors with Google Drive. Apparently its auto-update launched during my GPU-intensive game and overheated it enough to reach the shutdown threshold.

Fortunately, I’d just saved my game — or so I thought.

I spent about half an hour trying to fix Google Drive before I decided to just go back to the game for now.

No Man’s Sky picked up seamlessly…at the previous save. Maybe the write cache hadn’t been flushed yet or something. I’m glad I only lost about a minute of gameplay, though… I’ve got several hundred hours on this save file, and I’d hate for it to get lost or corrupted!

Anyway, back to Google Drive. I couldn’t reinstall it because I couldn’t uninstall it, and despite my efforts I couldn’t remove enough traces of it for the installer to be willing to run. You can read the whole reinstalling Drive saga on my troubleshooting site, along with the taskbar that lost its icons halfway through.

I eventually fixed it by copying the installed program files from another system and running the uninstaller manually. That resolved both the taskbar icons and the Drive installer being willing to run.

Then I dragged myself into bed.

Yeah, it was a fun Saturday night. 🙄

ยปAll pages site-wide with this tag