lazov

The commit history is a mirror of the real codebase, I wanted to show people that I've been working on this for a long time and that it's not vibe coded ai slop. In retrospect it seems that it was a mistake to do this.

Neverclick is digitally signed with Microsoft Trusted Signing (now known as Azure Artifact Signing). I had to send them my address and ID to get my identity verified so that I'd get approved for it.

Is there anything else I can do to put your mind at ease?

I wanted github to recognize the project as being written in C++. I made a controversial video about C++ a few months ago and people were clowning me that I had no C++ repos on my github lol.

Hello, I'm Lazo. I built Neverclick. Nice to meet you FinnKuhn.

I'm not anonymous, this is my name irl.

Neverclick is digitally signed with Microsoft Trusted Signing (now known as Azure Artifact Signing). I had to send them my personal information like my address and ID to get my identity verified so that I'd get approved for it. Additionally, Neverclick doesn't require admin privileges to run, and it works completely offline so you can block it via firewall and it'll work just fine.

Is there anything else I can say or do to put your mind at ease?

The commits are a mirror of the real codebase. My intention was to show people that I've been working on this for a long time and that it's not ai slop abandonware. But after reading some of the comments here I can see how it has raised more questions than it has answered.

The point is to track issues. I thought this was fairly common practice, apps like Keypirinha do this.

It uses CV to analyze the pixels on your screen to detect clickable UI elements.

Neverclick dev here. It's not random, a lot of thought went into how the key combinations are generated and assigned.

When Neverclick generates the key combinations, it prioritizes keys in the center of the keyboard. It then sorts the key combinations from most to least convenient (so for example JJ and FF would be at the top of the list). It then assigns the most convenient key combinations to UI elements closest to the center of the screen because that's where people are most likely to want to perform a mouse action.

As the other commenter already said, with dynamic data, you can't really make things repeatable. However, it's still really cozy to use and way better than if it were randomly generated and assigned (which is how it used to work before it was updated to the new system).

Most software in this space relies on accessibility apis, which means it only works in apps that have accessibility support. Neverclick uses computer vision. There are several advantages to using computer vision, the biggest one is that it works in every app. It also produces really good bounding boxes around text so it's great for editing text. And counterintuitively, it runs significantly faster than the traditional accessibility api approach. The hints show up instantaneously, even on old hardware.

Hello, I'm the developer behind Neverclick. Neverclick doesn't use accessibility apis. It uses local computer vision so it works in every app.

I've had a poor experience with accessibility apis, they're clunky, slow, and unpredictable, and as you said many apps aren't built with accessibility in mind. With computer vision you don't have to worry about that.

This might sound strange, but the cv system in Neverclick actually runs significantly faster than UI Automation (which is the accessibility api on windows) in nearly all of my personal tests. I can't believe that accessibility apis are so poorly optimized that raw pixel analysis is faster lol. Also, I have users that use Neverclick on 10 year old hardware and they tell me that the cv runs instantly whereas UI Automation is super laggy for them.

Also, accessibility apis typically don't give you useful bounding boxes for text in text editors, this is another advantage of the cv approach.

I really wish the title of the post was "Desktop application for performing mouse actions with your keyboard using computer vision" so that it's more obvious that it uses cv, although it's my fault since the current title is how I have it in the readme and they probably just copied that.