Honestly the most interesting thing to me would be how they got GPU drivers working for a hobby OS. I suspect this was difficult. Unfortunately the blog makes no mention of it.

The source, conventions are quite similar to Linux. So, probably some level of POSIX compliance + reusing standard libraries (such as mlibc) helped a lot.

I bet it's just running llvm-pipe to render in software.

Steam sockets and CloudFlare's UDP forwarding really are different though. They provide ddos protection as well as route optimization due to lots of points of presence.

Here there seems to be no mention of ddos mitigation or shorter routes due to infrastructure. Yes you need a key to connect but your iroh relay server can still be attacked. I suppose you could roll your own distributed anycast system for this.

I assume that the 'enterprise' relays have ddos protection. DDoS protection also comes standard these days, but we've seen attacks go from 20gbps to 20tbps so if uptime is required then tough luck.

Misread that as open office xml not office open xml. I wish the standards were named more differently. They are too easy to confuse

Microsoft did that deliberately.

My SD cards have always had stuff in that folder. It scares me. I try not to look

> Is there an opinionated reason not to break out capabilities?

If you have a disability and need tools to use your computer the last thing you want to do is have those things not only off by default but complicated and involved to turn on.

Is there a reason a capability has to be covered by only a single permission? Why not have one accessibility permission that covers all that and then a bunch of individual permissions for non-accessibility apps?

Controlling my computer is appropriate scope for an accessibility tool

> However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and and move the cursor... This is completely ridiculous and the proper engineering solution would actually be to phase out the accessibility API and replace it with something that is narrowly scoped so you can grant specific permissions individually

If you don't have use of your hands you want that. The whole point of accessibility APIs is allowing arbitrary control of your computer via novel means. One of the big selling points of Dragon Natually Speaking is the ability to tell your computer to do things based on descriptions without a mouse. "open outlook", "click compose", "select subject", "type foo", etc.

And no the solution here is not computer vision with an LLM. Text and buttons rendered on my computer exist in memory somewhere as text and buttons. We should not need to convert them to pixels and back lossily to recover text and buttons. We should just expose things to the accessibility API and not guess.

> And no the solution here is not computer vision with an LLM.

Also, even if you hypothetically wanted to use computer vision with an LLM… what API is that LLM going to use to take screenshots and click on stuff?

> Chrome and anything electron based don't provide any accessibility information to the OS

Are we sure about this? At least on windows, NVDA works fine with chrome and any electron apps.

Looks like they fixed this one since I last checked in 2016

Isn't it a mediatek CPU with an Nvidia GPU on the same package? At least thats what most of the reporting for nvidia laptop chips has been saying.

Worse it's from a marketing perspective if you read the guys bio.

The Donner Party begs to differ