Please disable case sensitive!!It's very bad with no rules.
and some other rules for the ID, like disable space.
you can ask toast, he had make some rules for the domain name.
It's a good chance!
at least we should disable space, I can register a ID of "bytemaster " or "bytemaster "
who want a ID system like this?
and we should disable utf8 charset
because too much special charset, like chinese space: "bytemaster "
Case-sensitivity is already accounted for by the name_hash. You get different keys generated with different capitilization, but all the forms of the capitilization will hash to the same hash value, so it's not possible to have someone registered as Alpha and alpha in the blockchain itself. The choice of capitilization used during creation just sets the public key generated (this is why the ID creator should remember the capitilization he used). But phishing attacks based on trying to register Alpha and alpha won't work, since only one will be allowed to register (the first to try).
We're looking into using some ICU functions to eliminate the various unicode spaces in the calculation of the name_hash for keyhotee IDs. Ideally there will also be functions there for taking care of some of the common chars that could allow phishing attacks. This part is still a little fuzzy as we're going thru ICU docs now and they're not fun to read.
Right now we're leaning towards a RFC 3454-style StringPrep to scrub the unicode string, maybe stripping accent marks, then our usual processing of trimming, eliminating consecutive spaces, smashing case, and replacing similar-looking letters