But having a degree of some kind still serves as a signaling mechanism, demonstrating lots of things including the ability to "play the game". to follow instructions, and so forth.

Last week they released a change that put the header Strict-Transport-Security into all responses (yes, even non-HTTPS ones!). This broke not just BookOrbit, but every other app I had running on that server, because suddenly everything being served by that host refused to work without HTTPS.

I probably should have done it sooner, but I spent a big chunk of the afternoon setting up new DNS entries so I can access each app through a different hostname. That was easy enough for me, running OPNsense with my own internal DNS, but you may not have that much flexibility in your home.

I submitted an issue (see https://github.com/bookorbit/bookorbit/issues/760) and a few days later, they created a semi-fix such that the header is only sent out in secure responses. But this still has the effect of forcing every app on that server to require HTTPS.

To be fair, it is now possible to load your favorite fonts onto baseline Kindle.

I discovered BookOrbit about two months ago. I think that it, together with the KOReader plugin that exposes the remote BO UI, may turn out to be a game changer in how I organize and access my ebook repository.

If you're working at just the most basic level of functionality, I don't think KOReader is necessarily worse than native Kindle. The latter is hampered by being very opinionated about how you should experience it, and that includes pushing their store above the user's own library, and this is a real annoyance.

As you start to demand more capabilities they diverge more. Organizing when you've got many books on the device is clunky on both platforms, but in different ways. The native Kindle options for grouping are simple, but not necessarily easy. They're very generic, and very cumbersome to work with. Bare KOReader's support for folders makes more sense to me, and it's easier to deal with bulk books than is Kindle's.

Getting books onto Kindle is super-easy if you get them from Amazon, but complexity ramps up for other sources. Your best bet is plugging it into USB and transferring via the file system. Native KOReader add to this an OPDS capability (if your book repository supports it), which works but is less than pleasant. If you use BookOrbit as your repository, there's a plugin that gives you the remote BookOrbit UI from the Kindle, which makes things a LOT better.

I experimented with Simply UI for a bit but could never get it to work quite right. About a month ago I found Bookshelf, and this makes the UX pretty wonderful. It has a very attractive and intuitive UI. And it simplifies the interactions needed for group management a bit.

Bottom line is that KOReader + Bookshelf are, for at least a power user, a potentially far superior experience compared to baseline Kindle.

I'm surprised that we don't hear more about this from the American government and media.

For example, you'll see farmers on the Shanghai streets come in from the countryside to sell their produce - and doing so with impunity. In, say, NYC there are vendors still, but they've got their wares on a blanket that they can quickly scoop up and get away when the police come by.

There seemed to be a tacit agreement between the people and the Chinese oligarchy: if you let those in power just keep doing what they want, they'll just ignore you.

However, China is a pendulum. It was very much the opposite at the time of Tienanmen Square; from the late 90s into the 10s there was quite a lot of freedom; but now with Xi's power having been consolidated, it's swinging back toward authoritarianism again. I've seen people describing more recent conditions there as the start of Cultural Revolution 2.0.

Around here we'd come to that conclusion at least a couple of years ago, due to abusive SEO and so forth. And that understanding was becoming even more widespread.

I don't know if Google's got the later parts of the game figured out yet, but I have to think that they'd realized that Search was dying. While there's still some value there, may as well use it as a hook to pull people into what they expect to be the next era.

Judging from my own frustrating attempts to use Gemini for vibe-coding, it seems like Google is badly over-sold (i.e., under-provisioned).

From all those promos giving away their pro-level subscription with phones; spinning up a mid-level subscription to undercut other providers and (probably most significantly) putting AI queries into ever search response because their flagship search product had become useless; they're promising a lot more processing to customers than they can reliably deliver.

The recent iterations seem to be intended not to push the capabilities forward, but to deliver capabilities at the current level while consuming less resources. That will allow them to maintain their trajectory until (I'm expecting) they get the huge infusion of extra compute resources from Space X later this year.

If I'm right, then I expect we should see Google start pushing forward again (rather than more of this lateral stuff) by the end of the year.

The design of these systems is the opposite of that: they're intended to intercept everything within their reach. The fact that with only four devices, their reach isn't (yet) so great has no bearing.

That's with running activity tracking including GPS for about an hour a day, and continuous heart rate monitoring.

At least on my device (and my body) the spo2 sensor is very finicky, requiring absolution stillness, and even at that I don't think it's accurate. So I don't use that.

I also discovered recently that simply using a custom watchface - even one built with an eye toward efficiency - lowers my battery life to about 2 weeks. The native faces enjoy privileged operations and are thus highly efficient. But custom-coded stuff apparently runs in a sandbox that has the effect of costing much more power. That's unfortunate, because my custom face used custom high-legibility fonts (derived from what's on interstate signage), making it noticeably easier on my aging eyes. The built-in fonts aren't great for this.

I just got a Garmin Instinct 3 Solar. It does mapping, and cost me about $300 US.

You're right that it's slow due to a wimpy processor. But the processor isn't because they're too lazy to innovate, but because they have something sipping tiny amounts of power so that I can get a battery life of several weeks.

But I also hate the "you had one job" meme and want to argue against its mindless usage. Most of the time, when people do the "you had one job" thing, it's false. And that's true most of the time in the case of buttons, too. In a typical user interface, a given button has some combination of these jobs:

* Communicate what action will occur should the button be pushed.

* (Sometimes) communicate the current status of some aspect of the system (e.g., often a button is used to enable/disable a mode, and the button itself visually conveys what the current mode is).

* Execute the intended action upon clicking.

* (Sometimes) communicate that the command has been received and is being executed (e.g., in the OP, the button might disable itself while animating the rotation in order to avoid the confusion the OP complains of).

> Learn to hack from TRASH WORLD NEWS, the underground computer magazine.

It seems like a missed opportunity not to name-drop 2600. But I guess they wouldn't be allowed to do that anyway.

I'm aware that there's widespread support for the idea that there's some odd atmospheric effect with refraction or something, that displaces the apparent location of real headlights. But even granting that, it doesn't change that it's a pretty weird thing.

But I was really speaking more broadly, about healthcare in general. There are only so many doctors, so many MRIs, so many heart surgeons, so many this or that. Giving everyone a bunch of extra money so they could pay the current prices doesn't do anything to address the scarcity, so everyone flush with those subsidies will just bid up the prices - which is exactly what happened.

While waiting for sunset, we also took a drive out of town to the southwest toward Mexico. It started as a nice paved road, but after an hour or so the pavement disappeared. A bit later, we started meandering down the side of a mountain, on loose shale, only one lane wide and nowhere to turn around. The views were amazing, but it seemed that was a clear sign that it was time to turn back.