undefined | Better HN

0 pointswycats10y ago0 comments

That would mean that, for example on crates.io, you couldn't create a `libm`, because `libc` is already very popular. I don't think that works.

0 comments

4 comments · 2 top-level

utexaspunk10y ago· 2 in thread

True- levenshtein isn't the best algorithm for the purpose. Is there an algorithm that takes key proximity into account? Like, 'libm' and 'libc' are sufficiently different to preclude typos, but 'lib[n/j/k]' or 'lib[x/d/f/v]' are not?

sqeaky10y ago

Key proximity on which of the hundreds of keyboard layouts?

utexaspunk10y ago

Good question... I'd imagine your standard QUERTY makes up a sizeable majority of programmers, but then I have no data to back that up... :)

nikcub10y ago

The default approach would stop automated attacks, there is no reason why the repository couldn't whitelist libm after review

j / k navigate · click thread line to collapse