I have numerous domains using the keyboard’s default apostrophe. It never dawned on me that the apostrophe from the keyboard will not be used, instead, the copy/paste ’ version must be used.
I read that the default keyboard version ’ will be replaced with the ’ version. Why would we make it more difficult to type an apostrophe into our texts and force us to use a copy/paste version? I’m sure there’s a good reason but there was no warning.
If this is the case, would it be fair to reimburse those who purchased the ENS names with the keyboard version (') ? Or would it be best to allow whoever registered an apostrophe name first should get the normalized version of the apostrophe and whoever registered second get the reimbursement?
It won’t be fair to take ETH from either party without reimbursement or granting the domain to first-come first-serve.
Thank you for the update. Do all the fees paid for apostrophes go to the DAO for no product received? Or can we at least get ENS DAO tokens or an option to purchase other ENS domains? Even if it is less than what was invested into the domains, anything is better than taking ETH and not giving any product or service back in return.
It is a bit mind boggling that an apostrophe on the keyboard we use every day isn’t accepted, instead another apostrophe we have to copy/paste off the internet like an emoji works in its place. I’m sure there is a very good reason for it but very surprised. Almost like saying the dash (-) on the keyboard doesn’t work and we have to copy/paste a special dashed line off the internet every time.
If anyone bought domains containing apostrophes so far, they had to deliberately avoid using an existing interface, which would tell you the name is invalid, and instead manually interact with the contract directly. Anyone doing that knows that they’re registering a name that will not presently resolve, and may never resolve.
Thank you for the prompt feedback. Very helpful. Yes, I minted directly with the contract knowing apostrophes would be normalized. Shocking that the keyboard default apostrophe is not the default. I must have missed the warning on your ENS tool that the keyboard apostrophe will not work or perhaps did not notice it was replaced by the non-keyboard apostrophe.
In case the governments decide to regulate these mistakes, policies and reimbursements, I would recommend something simple. Perhaps registering new domains using the ENS console, or optionally extending current domains owned by those wallets. Scrutiny and regulations from politicians are a matter of time. Best to have a plan in place to protect our ENS investments. Overreaching regulations sometimes can be avoided but I feel the politicians already have their sights set on the industry.