Live data from Hacker News

GoDaddy locks out derivatives of Chrome

news.ycombinator.com

41–50 of 196 posts

Re: GoDaddy locks out derivatives of Chrome

#41
post #31
post #27

Earlier quoted context omitted.

I don't get disappointed at neophytes using GoDaddy. People who know better though should know better. Nobody on here should be using GoDaddy.

Like most things it's not as simple as that. I'm a long-in-the-tooth web guy (30+ years doing this stuff) and for Legacy Reasons I use GD. I wish I didn't, but all my domains (and all my client domains) are with them. Yes I could unpick, but do I have time / inclination? No. Do I want multiple domain registrars? No. So - yeh, agree in principle, disagree in practice.

I'm curious what the reasons are. I moved ~60 domains from Gandi to Namecheap and then back to Gandi over the span of 10 months. Namecheap was cheaper, but their support wasn't as good and their UI is a disaster (IMO).

Both times I had all domains moved over in less than 24 hours.

Re: GoDaddy locks out derivatives of Chrome

#42
> Only allows direct versions of Google Chrome, Edge, Safari and Firefox

Where are you seeing that? The error message doesn't say that's the problem, and it's much more likely to be that Brave is blocking something GoDaddy uses for login.

Re: GoDaddy locks out derivatives of Chrome

#43
post #31
post #27

Earlier quoted context omitted.

I don't get disappointed at neophytes using GoDaddy. People who know better though should know better. Nobody on here should be using GoDaddy.

Like most things it's not as simple as that. I'm a long-in-the-tooth web guy (30+ years doing this stuff) and for Legacy Reasons I use GD. I wish I didn't, but all my domains (and all my client domains) are with them. Yes I could unpick, but do I have time / inclination? No. Do I want multiple domain registrars? No. So - yeh, agree in principle, disagree in practice.

I used to have about 50 domains there and moving everything to Cloudflare was pretty simple. Just start using it as a DNS first, which I was doing anyway.

Then the transfer process takes about 2 minutes per domain so the whole process was done in a little over an hour.

Re: GoDaddy locks out derivatives of Chrome

#44

Fraud rates of 'other' browsers are over double that of mainstream browsers. Nearly every metric is worse - from spam comment removal rate to adspam rate to credit card chargebacks. I can completely understand a web host deciding to block any browser that isn't a major one.

None of that should matter if the services are only available to validated, logged in paying customers. And then you decide on the basis of the customer whether to block, not the browser.

But it turns out a bot can look very much like a logged in paying customer, just they're paying with a stolen credit card and you'll only learn that in 2 months when the chargeback arrives...

Re: GoDaddy locks out derivatives of Chrome

#46
post #9

This is because the browser fails to load some JS on the control panel because the browser blocks them. That's it.

This is an infuriatingly poor error message if the problem is disabled JavaScript. Surely they can detect that and show a proper error instead of trying to be cute with this "Your browser is a bit unusual" junk?

No post body was provided.

Re: GoDaddy locks out derivatives of Chrome

#47

Earlier quoted context omitted.

This is an infuriatingly poor error message if the problem is disabled JavaScript. Surely they can detect that and show a proper error instead of trying to be cute with this "Your browser is a bit unusual" junk?

The error message linked from the post says "Try disabling ad blockers, enabling JavaScript or using a different web browser".

This feels to me like they used too many abstraction layers to know what the exact error is in the place where the error message is shown.

Re: GoDaddy locks out derivatives of Chrome

#48
post #31

Earlier quoted context omitted.

Like most things it's not as simple as that. I'm a long-in-the-tooth web guy (30+ years doing this stuff) and for Legacy Reasons I use GD. I wish I didn't, but all my domains (and all my client domains) are with them. Yes I could unpick, but do I have time / inclination? No. Do I want multiple domain registrars? No. So - yeh, agree in principle, disagree in practice.

I'm curious what the reasons are. I moved ~60 domains from Gandi to Namecheap and then back to Gandi over the span of 10 months. Namecheap was cheaper, but their support wasn't as good and their UI is a disaster (IMO). Both times I had all domains moved over in less than 24 hours.

Can you say more about how this works? I find it intimidating. And I don't understand how the cost works -- if I'm in the middle of my term with the first registrar, do I get a refund when I move it over? Like when you moved from Gandi to Namecheap and back in 10 months, does that mean you paid 3x registration, or did you get proportional refunds when transferring?

Re: GoDaddy locks out derivatives of Chrome

#49
post #30
post #19

Works fine on Vivaldi (which is Chromium-based), unless the error is only supposed to occur after an actual logging attempt, which I can't test without an account. So I don't doubt there's a limitation, but it doesn't seem to disallow every derivative browser (assuming I'm not misunderstanding you somehow).

Vivaldi workarounds these kind of issues by identifying itself as chrome. When a site blocks vivaldi because it is not chrome the site is added to a list and it will identify itself as chrome in the future (I know because it happened with the web version of whatsapp).

It's actually a whitelist. Vivaldi always uses the Chrome user agent, unless it's a website known to not block it, like vivaldi.com, and probably some of their partners too.

Re: GoDaddy locks out derivatives of Chrome

#50
post #21

Earlier quoted context omitted.

This is an infuriatingly poor error message if the problem is disabled JavaScript. Surely they can detect that and show a proper error instead of trying to be cute with this "Your browser is a bit unusual" junk?

It's hard to differentiate between completely disabled JavaScript, some individual JavaScript files being blocked by an (overzealous?) ad blocker, and the browser not implementing some required JavaScript feature.

Actually it's trivial to detect if JS was completely blocked with the tag. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/no...

And on the flip side you can trivially detect if some .js file was blocked from loading with some inline tag that checks for whatever the .js file should expose.

The third case with the browser not implementing some feature is a bit more work but usually also rather easy to do.

Post reply on HN