If you have a good solution to rent-seeking, a great many marketplaces would benefit.

Not giving out real estate on a "first come-first serve basis" but actively moderating the allotment of real estate.

I’ve seen and reported those squads and the admins did properly address those.

The discussion in this subthread is about https://crates.io/crates/keyboard which still exist as do the other obvious squatted names from the same user: https://crates.io/users/swmon

Composite namespaces. Like "mcdonje/fourtytwo" or "com.acme/http".

How is that an issue?

One consequence is that you end with cute names instead of clear names. Cherry picking from the top 30 or so crates:

- parking_lot

- hashbrown

- ryu

- heck

The longer there's a shared namespace, the stranger the names get as the "good" names are already in use.

For implementations of a known idea, I would rather have a fun codename than see the word for the idea used to also name the implementation.

The contrary case gets confusing fast. "Oh Known Algorithm doesn't work" "Huh, I read a paper which proved it works" "No, I mean, Known Algorithm, not known algorithm". "What?" "The implementation by Popular Author. It's broken for the case we care about". "Can't they fix it?" "They say that although their implementation is called Known Algorithm it's just better that it not fix this because now Known Algorithm is different from the known algorithm". What?

Knowing there's a problem, or a different performance trade off, or a lack of maintenance for Haphazard (Jon Gjengset's Hazard Pointers implementation) is very different from having a problem with Hazard Pointers the idea.