Capitol letters in name? sex.bit vs Sex.bit

[Google]

Since both can be registered

see:

d/sex
http://explorer.dot-bit.org/tx/2362940

d/Sex
http://explorer.dot-bit.org/tx/2582805

how does this work on the browser? example, If I type Sex.bit <--(capitol S)

would it take me to d/sex or d/Sex?

Or does is it work that ONLY lowecase d/namespaces get registered .bit and anything else is merely data entry on this one big ass ledger?

[biolizard89]

Since both can be registered

see:

d/sex
http://explorer.dot-bit.org/tx/2362940

d/Sex
http://explorer.dot-bit.org/tx/2582805

how does this work on the browser? example, If I type Sex.bit <--(capitol S)

would it take me to d/sex or d/Sex?

Or does is it work that ONLY lowecase d/namespaces get registered .bit and anything else is merely data entry on this one big ass ledger?

From the .bit specification:

"only valid domain names are allowed, which means characters other than lowercase letters, numerics and dash are not allowed, as well as names longer than 63 letters and names starting with a dash"

d/Sex is not compliant with the spec, and any compliant .bit implementation will refuse to process it. My guess is that the owner of d/Sex is hoping that some implementations are buggy; the block explorer had a bug with case-sensitivity a while back (not sure if it was fixed).

EDIT: I can confirm that Convergence for Namecoin will direct you to sex.bit if you type in Sex.bit (just like Google.com takes you to google.com). So Convergence for Namecoin is following the spec regarding case sensitivity.