ENS Normalization with {FE0F} inclusion - ENS Fee and more

Exactly what I’ve been trying to point, if something has been happening for a while that doesn’t mean it can’t be improved further. Furthermore FE0F is a variation selector and I speculate it might be of use in future browsers/apps probably few years down the line. Adopting primitive versions doesn’t set right logically. It only confuses the registerer further like in this case, I’m not the only one - Registered Emoji contains "EF%B8%8F" symbols

Right now we just assume it’s useless, while I’ve also shown examples above how FE0F makes a huge diff in price and in the appearance of a few emojis, and could be of importance in the future.

in your own words @raffy
Continuing the discussion from ENS Name Normalization:

I’m with the opinion that the DAO should consult Unicode or alteast be a part of the consortium.