Notices by Mikołaj Hołysz (miki@dragonscave.space)

@mttaggart @mwl I don't think this is actually going to happen.

There's so much stuff relying on .io at this point that I won't be surprised if major DNS providers just sidestep ICAN and take matters into their own hands.

ICAN isn't omniscient and omnipotent, if the majority of the world decides that they shouldn't be in charge of DNS any more and that we'd rather use a different set of root servers, their power basically goes away.

@Piciok If you were to do this for Android, you could even go as far as dumping the UI tree from an existing app and letting the user edit it.

Never attribute to malice that which is adequately explained by evolution.

@rysiek THe non-malicious interpretation is that you will get hit by this unless their website can, positively and with certainty, determine that you're a human and not a bot run by a competitor. If you're deliberately installing software that prevents this from happening, the results speak for themselves.

THe airline industry is extremely cutthroat, and companies have a habit of scraping airline websites and posing as web browsers to sell tickets at a profit, usually with a far worse customer service. Airlines have very little choice here.

@GossiTheDog @Quinnypig Quoting from the document:

"Data will not leak across workspaces. For any model that will be used broadly across all of our customers, we do not build or train these models in such a way that they could learn, memorise, or be able to reproduce some part of Customer Data."

Please stop spreading misinformation

@drewdevault I'd disagree here, a program can be I/O bound (let's say small requests to a slow service / on a slow network), but you might still want to e.g. accept input from the user while the slow service is doing its thing. If you don't have threads or async i/o, you're waiting on the network while the user thinks your program is broken.

Unpopular opinion.

"maybe later" buttons are kind of nice, actually.

If you have an actual "no" button, you need to figure out what to do when the user accidentally clicks "no" and wants to change their decision.

You either need a setting for every possible pop up you might want to display, or at least a "reset warnings" button somewhere. That's a lot of maintenance, not to mention the fact that most users don't know how to find those.

If you enjoy reading accessibility battles between blind users and absolutely clueless software developers, oh boy do I have a thread for you.

This guy is trying to add accessibility to an open source slicing tool for 3d printers, he's even willing to do a lot of the work himself if he gets assurance that his PRs are going to be accepted, but the developers are just not seeing it.

I think my favorite quote in the thread is the following, from one of the lead devs:

"it may be better to have these features NOT accessible to the screnreader[sic] at all (which means they are effectively removed from the UI), because there is no point in presenting a feature that a person cannot use"

Along with a suggestion to implement a half-assed, blindness-specific GUI with half the features later down the thread.

The whole discussion is here, for those brave enough to read it https://github.com/prusa3d/prusaslicer/issues/7595

@vik What if the manufacturer is using software / components to which they don't have full rights themselves? Nobody builds anything "from scratch" any more, and many spaces (I don't know about medical) just don't have any open source tools to go with. If the alternatives are not entering the UK market at all, having to make a completely different, from-scratch version from a single country or pay ridiculous amounts for full copyright on every single part you use, the first option is the only ones that make sense. This has the potential of removing access to all medical devices instead of making them freely available.

@simon Whatever you end up doing, ensure you're properly crawled by archive.org in any case. Custom domains help with this, I've seen a platform throw a tantrum over their content being there when they went down and opt themselves out, losing years of valuable community history.

Pro tip for Mac users. Option+enter on a link in Safari will immediately download the file behind that link to your downloads folder. This is one of these shortcuts that doesn't seem to be mentioned anywhere and that you won't know about if nobody tells you.

Today I learned. The Tesla owner's manual has alt descriptions for its images. They're not good alt descriptions, but they are there.

In fact, it is one of the most screen reader accessible manuals for any device I've ever seen, most are some weird PDF abominations where all the button names are replaced by their unlabeled icons. Even devices made specifically for the blind have these issues sometimes. This? This is just perfectly readable HTML.

It's especially ironic considering that Teslas (as far as I know) aren't accessible in any way. Even the infotainment system, which a blind person might want to use, for example when waiting for a sighted acquaintance in the car, does not have a screen reader and is not in any way usable.

If you're curious, the manual is here https://www.tesla.com/ownersmanual/model3/en_us/

I'd pay for a jacket and/or white cane that delivered small electric shocks to random passers-by who think that grabbing a blind person without asking first is a good idea.

I can see a tech outlet publishing a Top 10 most user-friendly jurisdictions to choose in your settings article about 2027 or so.