Live data from Hacker News

Cloudflare Registrar now supports .dev domains

twitter.com

41–50 of 56 posts

Re: Cloudflare Registrar now supports .dev domains

#42

Earlier quoted context omitted.

I know I shouldn't judge a book by its cover, but I have such a hard time getting past this company's name.

Well if the name's annoying you, the dejigamaflip button will make you toss the book in the bin for sure.

...it actually exists!

> DEJIGAMAFLIPPER: Sometimes, you just got to put your domain down, dejigamaflip it, and reverse it.

but, the hell does it do?

Re: Cloudflare Registrar now supports .dev domains

#43

Earlier quoted context omitted.

Well if the name's annoying you, the dejigamaflip button will make you toss the book in the bin for sure.

...it actually exists! > DEJIGAMAFLIPPER: Sometimes, you just got to put your domain down, dejigamaflip it, and reverse it. but, the hell does it do?

It pops up a dialog box that you've successfully dejigamaflipped your domain.

Re: Cloudflare Registrar now supports .dev domains

#44
post #18

For those looking for a CF alternative, I have my .dev at Porkbun and am happy with them.

Worth noting that Porkbun still uses CF for the actual DNS nowadays: https://lowendspirit.com/discussion/4602/porkbun-ns-moving-t...

If you use their nameservers, yes. If you just use them as a registrar and have your own nameservers, then Cloudflare is not involved.

Re: Cloudflare Registrar now supports .dev domains

#45
post #6

I hope a CF person sees this: i am on a corporate network and I can't login to my CF portal to manage domains because I am on firefox. Tracking protection and adblocking is disabled. It worked, now it doesn't because it is stuck on "are you a human captcha". It doesn't even attempt to present me with a captcha challenge, just a checkbox that refreshes the page! As far as I can tell you are conspiring google to enable…

Don't know about your situation, but the only time I'm reminded Cloudflare exists is also when they throw me into a captcha loop that I can't get out of. In fact since yesterday gitlab.com has been blocking me with a Cloudflare captcha that's just stuck in a loop of making me click a "Verify you're a human" checkbox. I click it, it spins for a bit, then shows the same checkbox again. :D (Glad I don't use gitlab for anything serious.)

Re: Cloudflare Registrar now supports .dev domains

#47
post #16

Earlier quoted context omitted.

I am, yes. Not a slight to Cloudflare, but it's never good when one entity touches so much.

Especially considering that their core product is MITM.

I've never quite understood this idea that Cloudflare is an MITM. An MITM is by definition a covert intermediary. Cloudflare is a service provider that's deliberately employed by a site operator. If CF is a MITM then so is AWS, GCP, and every other CDN service provider.

Re: Cloudflare Registrar now supports .dev domains

#49
post #47

Earlier quoted context omitted.

Especially considering that their core product is MITM.

I've never quite understood this idea that Cloudflare is an MITM. An MITM is by definition a covert intermediary. Cloudflare is a service provider that's deliberately employed by a site operator. If CF is a MITM then so is AWS, GCP, and every other CDN service provider.

I guess MITM has a specific (adversarial) definition and I've bastardized it. The only cloud load balancers that I use are layer 4, so they're not unwrapping HTTPS for me, but your point is taken.

Re: Cloudflare Registrar now supports .dev domains

#50
post #47

Earlier quoted context omitted.

Especially considering that their core product is MITM.

I've never quite understood this idea that Cloudflare is an MITM. An MITM is by definition a covert intermediary. Cloudflare is a service provider that's deliberately employed by a site operator. If CF is a MITM then so is AWS, GCP, and every other CDN service provider.

> An MITM is by definition a covert intermediary.

I've never thought that it had to be covert or even nefarious to be a MITM. It's a man-in-the-middle if it's sitting between two endpoints talking to each other and intercepting the data stream.

For instance, I proxy all of my web traffic in order to be able to filter my HTTPS streams. It's neither covert nor nefarious, but is still a man-in-the-middle. It's just not a man-in-the-middle attack.

Post reply on HN