You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The website is hosted on GitHub pages meaning that it is a static website without a proper backend that can run a database or something, so sending the upvote action and storing the upvotes would have to be delegated to a third-party via JavaScript calls (periodic rebuilds of the website could eventually update the upvote stats for users with disabled JavaScript).
However, what could be more problematic is determining the identity of the user to avoid multiple upvotes for the same keymap coming from the same user and remembering the user's actions (so that future visits of the user X will still show the keymaps (s)he has upvoted in the past with a filled-in star symbol or something). Creating full-blown user accounts would be overkill. The most straightforward would be to group upvotes by IP address but VPNs throw a wrench in the works. Browser fingerprinting is another possible avenue but at the end of the day, I think I'll be most limited by what the third-party data storage solutions offer.
Here is my idea, link related pull request to each keymap, and then count 👍 and 👎 reactions via github api during CI. I might help with the implemention if you like this.
Activity
precondition commentedon Jan 3, 2026
The website is hosted on GitHub pages meaning that it is a static website without a proper backend that can run a database or something, so sending the upvote action and storing the upvotes would have to be delegated to a third-party via JavaScript calls (periodic rebuilds of the website could eventually update the upvote stats for users with disabled JavaScript).
However, what could be more problematic is determining the identity of the user to avoid multiple upvotes for the same keymap coming from the same user and remembering the user's actions (so that future visits of the user X will still show the keymaps (s)he has upvoted in the past with a filled-in star symbol or something). Creating full-blown user accounts would be overkill. The most straightforward would be to group upvotes by IP address but VPNs throw a wrench in the works. Browser fingerprinting is another possible avenue but at the end of the day, I think I'll be most limited by what the third-party data storage solutions offer.
webgtx commentedon Jan 3, 2026
Here is my idea, link related pull request to each keymap, and then count 👍 and 👎 reactions via github api during CI. I might help with the implemention if you like this.
precondition commentedon Jan 3, 2026
Unfortunately, most keymaps were added by me without going through a pull request every time.