Obviously without a proper RAG pipeline or web search it is just going to hallucinate with maximum confidence. It would be more interesting to see the results with top tier models that have proper alignment to refuse to answer when token probability is low. As it is they just proved that people tend to trust well written text in a chat ui

The interesting taxonomy may be less about the source of the names and more about what properties they have

Somewhere in Cloudflare's DNS system, a random number generator briefly became the office matchmaker

A surprising amount of infrastructure design seems to be hiding patterns that humans will otherwise turn into unsupported features

The web has its own problems, but at least bad HTML is often still visible enough to repair. A custom canvas-like desktop UI can be basically a black box to assistive tech

Very true :)

I had this exact issue with the Elgato StreamDeck user interface, which renders the macro buttons as one big canvas only drag-and-drop interacts with.

It's rare that I outright cannot figure out a way to make a UI accessible, but that one managed to break everything I tossed at it. I eventually switched my effforts to an open-source third party client which had a web UI, which is now accessible to screen reader users.

As for repairing HTML, my last few engagements have clearly shown me that while HTML CAN be repaired, many devs these days wouldn't know where to even begin to do that. The amount of hand-holding I've had to do has made me suggest, several times, to just give me git access as it'd be faster if I just fix it myself.

Yeah, blind seems unavoidable there, since it's literally about a blind client

The "invisible" point is interesting, although I'm not sure I'd read too much into it. Visual metaphors are so baked into English that avoiding all of them can start to feel a bit performative unless the wording is actually excluding someone

> Visual metaphors are so baked into English

This is the point I am making.

Sidewalks have to be usable by people who can't hear, people moving slowly, kids, older people etc. If a cyclist is on a sidewalk and can't safely pass without the pedestrian reacting instantly, they're the one creating the problem

We can't individual responsibility our way out of systemic problems. Cyclists on sidewalks generally signals terrible bike infrastructure.

There are people on bikes that ride like an asshole. There are people on cars that drive like an asshole. Both cause (different levels of) risk for pedestrians. There's only so much we can do about assholes, social ostracism works only so far and social change is much harder to accomplish than modifying our built environment to reduce or eliminate conflict points.

As an aside, I've noticed people get startled when I'm on my bike stopped but balancing on my bike while I wait for then to cross. I think some people intuitively model bikes on the same category as cars, so being anywhere close causes them to react as if a car hard crept close.

Thanks for stopping.

In my experience as a pedestrian, bikes are worse than cars. Less predictable, less observant of laws, and more willing to take risks that depend on others jumping out of their way.

On the plus side, they don’t weigh 3000lbs.

The statistics still point towards being more concerned about cars.

Statistics don’t lie, but my experience doesn’t lie either. 90% of the assholes I encounter on the road are on bicycles.

FWIW, I live in Seattle, a famously bike-friendly city. Stop signs, red lights, pedestrians and even one-way street signs don’t seem to exist in the visual field of many cyclists here.

Obviously there are reasonable law-abiding bicyclists out there. Certainly all the cyclists online say they obey all the laws. But apparently I’m seeing an entirely different group of people in the real world, zooming around lawlessly.

What I've noticed is that the crimes of motorists, cyclists, and even pedestrians, are crimes of opportunity and convenience. In each case it's a matter of what's possible, offset by the chance of enforcement.

Motorists exceed the speed limit, roll through stop signs, and are looking at their phones while driving.

Cyclists blow through stop signs, and take advantage of shortcuts.

Pedestrians "jaywalk." There's not much else they can do.

I don’t personally know anyone hit by a car, but my dad ended up in the hospital with a collapsed lung due to a drunk cyclist ramming him on the boardwalk.

Bicycles belong on the streets. (I bike to work most days, I take the streets)

> Cyclists on sidewalks generally signals terrible bike infrastructure.

No. It signals cyclists not giving a fuck about the law. In at least some EU countries, it is illegal to cycle on sidewalks, except with children.

The "read only" example is such a good illustration of how accessibility problems often aren't one big broken thing, but a bunch of tiny reasonable-seeming decisions stacked together

So many things are like that. Trying to bolt on accessibility or security as an afterthought never work as well as making those things part of the initial design.

I've been at this long enough that yes I know that just getting something out the door so we can make money is important.

But this just creates another kind of technical debt that comes back to bite you.

The most interesting number is missing here, and that is the token distribution by use case. If 60-70% was eaten up by PDFs, agents and automation instead of people actually sitting in Claude Code, then it is a completely different story