This sounds nice, but it won't change the fact that they can be independently auctioned on the blockchain level because technically the names are distinct (case insensitively) strings in punycode. it'd be nice to establish some tooling conveniences for managing these kinds of things more automatically, but i think it's too late to redesign hns to deal with them differently at the consensus protocol level.

I do think that on the namebase site, the pages that feature a punycode name could also show links to related variant names (alternative capitalizations, _ and - substitutions and removal, similar emoji, even semantic word pluralizations and conjugations, etc) but UI design wise i'm not sure how i'd expect that to look without getting very busy very fast. for most words/phrases this could be a very long list of potential variations.

Namebase could also consider sorting these similar names alphabetically next to each other based on the unicode form rather than punycode string.

Also, it might be really handy to be able to manage DNS for two or more names that are closely related such as above so that they all land in the same place from a user perspective. This could potentially become a convention to follow in the ecosystem so that instead of typo-squatting parked domains showing junk ads and such, they'd just get us where we were (obviously) trying to go.