I can promise you it isn’t. This totally predates llms. Been using them for a long time

I’ll give you a use case. People with disabilities who can’t use the keyboard. Ploopy stuff has been absolutely amazing.

Does it work better than a trackball (thinking of the Kensington ones) in that respect ?

Use those a lot to (always try and focus off the shelf first). But for cases where we need to position differently we often need something custom

Depends on the disability. Not a homogenous group. "Work better" for whom?

I’ve provided a lot of different of the balls. Last one was for someone in bed and needed to control the whole pc with his chin. We adapted the base to fit on a mount. Other uses for people with ALS with reduced hand function - altered the ball shape to hold the hand.

I find that the new "drug" is constantly hunting down new cheaper models.. z.ai/glm, mistral, deepseek.. if you need to get your fix - find the cheaper path..

Average drug connesiuer activities

take a peek at https://github.com/willwade/app-automate?tab=readme-ov-file#... - its early and needs some work -but this is the idea behind this.. (my use case is not agents but actual real disabled people..who need tooling to provide better access to the desktop)

Interesting! I started something - nowhere near as complete as that and quite different but again using accessibility UI elements. The BIG problem I've found is SOOOO much stuff does really poorly having these elements exposed. Here was my approach https://github.com/willwade/app-automate?tab=readme-ov-file#... - What I do here is build UI templates - either using UIAccess OR using a one pass using a vision model.

Now the argument against this on [reddit](https://www.reddit.com/r/openclaw/comments/1s1dzxq/comment/o...)

"my experience is the opposite actually. UIA looks uniform on paper but WPF, WinForms, and Win32 all expose different control patterns and you end up writing per-toolkit handlers anyway. Qt only exposes anything if QAccessible was compiled in and the accessibility plugin is loaded at runtime, which on shipped binaries is basically never. Electron is just as opaque on Windows as on macOS because it's the same chromium underneath drawing into a canvas. the real split isn't OS vs OS, it's native toolkit vs everything else."

sorry i had missed this! this is extremely interesting. thank you for sharing. i thought about this approach and came to the same conclusions as the reddit thread you shared. then again, it probably works fine for 80% of cases...

It gave me strong vibes too. It’s the writing style. I’ve seen OpenAI write just like this. Doesn’t mean it’s bad. There’s a few other markers. Note “silly” in quotes and over use if that word. Once would be enough. But also this is very very typical. The bolting and short quite direct and a bit repetitive statements “it absolutely does not solve “dumped a bag of candy on a messy kitchen table and took a dramatic iPhone shot.”

Real example programs are where the joke becomes a language I didn’t want this to stop at “hello world with candy colors.”” The over use of quoting. The bold. It’s not like a human wouldn’t write this. But it’s unusual for a human to do this imho. All the same - it feels novel. And at the end of the day it’s a neat idea. It’s just we enter this new brave world where things written like this give you the ick. “Where do the ai learn this from?” Well I wouldn’t mind betting the author asked it to be written in a hn style post.

Please re-read your comment and tell me you're not grasping at straws just to accuse someone of using AI to write.

Yeah, the execution is stronger than the idea and design choices as well, which suggests heavy AI support

You have a problem. I would suggest thinking about it.

how did you redact the sensitive data? did you use a library for that?

.. and fentanyl for sure right? surely its the largest producer of fentanyl.. or is it cocaine? hold on whats that drug ICE? ah thats it..

Well flying over it the place does seem covered in white powder?

that to me looks like a error in whatever logic is behind the positional error code. You'd think they would have transformer models based on different layouts but maybe some weighting issues going on.. ie I would have thought its a model that is altering based on likelihood weights and maybe something up with that..