😁.to

@bentossell Thanks for the questions, Ben! > [how is it different?] Many sites let you register emoji domains, which is fine if you know exactly what you want. What 😁.to provides is a visual overview of available domains so you can pick and choose. Generally this approach doesn't work since there's an unlimited number of domains you could possibly register, but when it comes to single-character emoji there's only about 1,500 of which 30% is already taken. For example I wouldn't have thought of register 👏.to until I saw it was available. I might add support for other TLDs in the future, but I believe most single-character emoji domains on other TLDs are already taken. There's some exceptions for untrustworthy ccTLDs I wouldn't use myself. (do your own research if you're going to build a business relying on an uncommon ccTLD) > [why did you make it?] Max Guerin told me about emoji support in .to domains. He suggested I'd register one, but I wasn't sure which one to get. So I made a script that checked all possible emoji domains. That way I could pick and choose. After I registered my personal favorites (👋.to, 👏.to, and 🙌.to) I figured I should publicised the list for the rest of the world to benefit from :)

@bentossell @marckohlbrugge So this is your new highscore.money? ;)

@bentossell @nadermx No, that's still coming :)

@arunsathiya Yeah I think that's a recent change due to security concerns. Some unicode characters look a lot like regular characters so someone could register a domain that looks like paypal.com but is actually something else. I don't see why regular emoji couldn't be whitelisted though. I expect they will change that at some point. For what it's wroth, the emoji domains do still work in browsers Chrome. Sites load fine. They just don't show up as visually pleasing.

@marckohlbrugge Exactly. Whitelisting regular emoji should happen soon.

@flarup @marckohlbrugge I checked that too. Love it!