Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

Chrome has always been broken with respect to handling custom local TLDs, UNLESS you remember to include the trailing slash -- for example, http://reg.for.free/

So is it broken now when you include the trailing slash for opennic domains?

And yes, if you're seeing the page with the list of domains, that's just my default landing page.

OpenNic doesn't have a .reg TLD, so registering.reg and openinc.reg of course would not work.  Not sure why this was listed as a problem.

On 12/09/2016 02:10 PM, Maiyannah Bishop wrote:

Yeah, it doesn't seem a gamebreaker or anything, but does seem worth noting.

The reg.for.free ones "just" have the silly Chrome behaviour which for now seems to have sufficiently been banished by a hosts file override.  register.fur seems straight up down though, and isn't on reg.for.free, now that I look

-mb

On 2016-12-09 16:06, Jonah Aragon wrote:

I think the gopher registration page is being reworked, last I heard. But you can register them at reg.for.free so it doesn't matter that much overall. I don't know about other domains. Which ones are having issues besides .gopher?

Jeff (Shdwdrgn) manages a lot of TLDs nowadays (look at the list ns2 has on the servers page) so a lot of them might also have reg.for.free options if their individual sites are down.

Jonah