How do you handle apps that don't have great accessibility support?
Hell - after installing, it shows a slider to help adjust the label size of each element - but I can't slide it because (surprise) Homerow doesn't support horizontal slider elements like this.
I also can't highlight text on the screen etc.
Struggling to find a usecase for Homerow that isn't just navigating chrome or my filesystem.
I manage a component of an internal compute product which serves ~a billion idempotent use-cases per quarter and I can confidently tell you that you're incorrect.
What I haven't been able to teach AI is the full distributed nature of the system, how we progressively roll out each service (about ~30 unique ones) when we push updates -- and how to read, write, and review my code while keeping all of this in-context (because believe me, if it's not in-context, it is useless to me). Don't get me started on all the containers, K8s configs, endpoint naming conventions...
My entire stack covers bare metal, virtualisation infrastructure, storage infrastructure... I could go on. At a certain scale, it doesn't matter how fast you write something, but if what you're writing is bulletproof.
Jumping in here with relevant experience - because you're absolutely right.
In 8th grade (~16 years ago) my substitute biology teacher organised a "Water drinking competition" poised to elevate our understanding of stomach capacity, etc.
Two of us went to hospital, and ~5 (including myself) had to take multiple days off of school and recover.
What was exactly his thinking here? Do biology teachers study biology because that’s kind of the first things you learn (saline concentration, kidney, etc…)
At least where I am, substitute teachers don't have to study anything in particular at all. You simply need to have completed X number of credit hours at an accredited institution, no actual degree or certificate is required and the coursework can be literally anything. As a newly-graduated history major I signed up to substitute teach out of desperation, and was sent everywhere from kindergarten to calculus.
Not sure it's completely accurate. I played a standard queen's gambit accepted, took black's queen which it immediately blundered, then tried to move my queen from c5 -> e5 and the game ended immediately showing:
*Illegal Move*
You Lose.
Game over.
A little disappointed, since it's of course a valid move.
It’s very picky about how you specify a move. “e2e4” is fine as a first move, for example, but auto-capitalized “E2e4” is losing immediately. Quite weird, given that there are guardrails against “e2-e4” and “E2-E4” (an alert pops up telling you how to write moves)
1. Telemetry to dirac.run/v1/event — Sends machine ID, token usage, model info, events, errors (first 500 chars), and platform info. Hardcoded API key. Defaults to opt-in (setting is "unset", not "disabled").
2. Feature flags from dirac.run/v1/event/decide — Polls every 60 minutes with your machine ID. Always enabled, independent of telemetry opt-out. No way to disable without code changes.
3. Web tools route through api.dirac.run — Web search and web fetch tools proxy through Dirac's own API server, sending your request content plus system headers (platform, version, machine ID).
4. Model list fetches — Calls OpenRouter, HuggingFace, Groq, etc. for model listings even when using the Anthropic provider.
This is something that needs to be deprecated entirely. The web fetch tool no longer is used or works. There is nothing even listening at api.dirac.run. This was the result of me stretching my capacity too thin and bulk renaming cline.bot to dirac.run
UPDATE (+1h): both Web search and web fetch tools are now nuked.
Hell - after installing, it shows a slider to help adjust the label size of each element - but I can't slide it because (surprise) Homerow doesn't support horizontal slider elements like this.
I also can't highlight text on the screen etc.
Struggling to find a usecase for Homerow that isn't just navigating chrome or my filesystem.