Just wanted to mention that I've made those settings configurable now, and it'll default to the normal vim line numbers. Feedback shifted this one up the priority list!

Ideally, I could fix the mousing clicking and add targets that you need to delete.

I'm actually curious who would win that race. Because you're right; mouse users have a huge advantage right now, but no one just clicks on code haha!

I think adding the ability to order by different columns would be good.

I'm actually not 100% sure if I can achieve that with dynamo db and my current data structure though. It has a great free tier, but the query language and limitations are very foreign to me.

If I wanted to sort by timeTaken, I had to set it to be one of the two keys. This also has the unfortunate consequence of blocking duplicate times.

It might just be my implementation that is strange, or the dynamo is significantly less featureful than an SQL server.

Just a note, I've looked into this a bit more and it's technically possible. It would just require some redundancy and extra logic to keep everything in sync.

The donate feature has a goal now to replace dynamo db with a sql db because it will make development and maintenance easier.

Oh that's a huge find thank you. I wasn't sure what was missing.

I think I'm working off a white list, so I should just be able to add that to it.

Another variation on that is relative in both modes, but my current cursor line has the absolute. That's what I tend to roll with!

Thats a good point! I'll have a better description by the next release.

I'm conflicted about keypress count because I really want the focus to be about speed. VimGolf does a great job of covering those types of puzzles/scenarios. The differentiator here is speed. I'm hoping that I'll be able to do some sort of data analysis on key strokes. An interesting finding might be that www is faster than f<a character>.

One of my hypothesis was that searching with 'f' and 'F' is not as efficient as simply navigating with more commong motions like w, e, h, j etc. I've already been proved wrong, Although, I should phrase it like "many top performers use 'f' and 'F'." Which would suggest that they might be fast, or using them isn't too much of a detriment

I'm very suspicious of the 1s leaders on the board.

F and f are fast (ditto T and t) because , and ; are faster.

There are some things that make the fake scores really obvious.

It's going to be a challenge to protect the leaderboard against fake scores. There weren't a whole lot of them before, but it's starting to increase as the site grows.

Sorry about that! Something seems to be broken with my publishing pipelines. It used to be a graceful switch. Now I have to manually invalidate a cache. Seems to only happen on some publishes.

Another user mentioned this too. I'll be adding settings to let users turn relative lines off.

is the vimrc exposed?

For maximum vimness you could let players mod an empty vinrc from start

I think the library just has key bindings, so it wouldn't even have a vimrc.

The library seems great at the time, but I might need to look into alternatives in the future.

A full vimrc would allow blatant cheating, such as preprogramming commands to do exactly the movements you need for a given case.

It sounds like allowing toggles for a few key options would probably satisfy most people while keeping the spirit of the exercise.

I might just have to add a :q easter egg some day.

I've got this feedback quite a few times, so I'm going to bump configurations up on the roadmap. I think proper vimrc configs might be impossible unless I swap out some of my libraries.

I should provide the ability to disable relative lines though

I'd echo that "what am I even aiming for" was an initial confusion for me as well. The targets are pretty subtly styled and it took a few rounds of looking to realize it was already there. Also found it confusingly visually similar to the matching-brace/paren/bracket markers. And I'd say I have sharper eyes than most. I imagine even mildly color-blind people will struggle.

Changing to a more distinct color for the targets could already help a lot to improve on those parts I think.

I couldn't figure out what targets were either. simple fix is to put am example yellow square in the sentence inline.

Oh that's a great suggestion! I was adding a bit to the description, but I should provide an example too.

Are there any other configurations that people want to have? I can try to do a number of them manually.

I think a choice between standard/relative line numbers would be nice to have because that choice potentially affects your chosen motions