I opened a bug in an unrelated repo yesterday and nearly immediately got hit with one of those. Kinda wish I'd downloaded the zip before it got deleted. I'm curious what the attack was.
I ignored it because it wasn't a pull request or patch file, it came too fast, and the explanation misidentified the source of the problem.
The picture of donkeys helping construct a wind tunnel at Langley is pretty interesting. Never thought anything used in the space race would have been built with animals.
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.
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.
> 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.
> 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.
I ignored it because it wasn't a pull request or patch file, it came too fast, and the explanation misidentified the source of the problem.