GoDaddy locks out derivatives of Chrome • Hacker News Board

Re: GoDaddy locks out derivatives of Chrome

#21

Post by pdw » Thu, Jul 14, 2022, 10:56 AM UTC

alias_neo wrote: post #13

rvnx wrote: 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?

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.

Re: GoDaddy locks out derivatives of Chrome

#22

Post by capableweb » Thu, Jul 14, 2022, 10:56 AM UTC

sshine wrote: post #15

abirch wrote: post #10

Earlier quoted context omitted.

Too bad there's not a chance to respond, "I assume all responsibility for my unusual browser." I remember having to change the user agent string in Konqueror

You would do that rather than change domain provider?

Faking the User-Agent usually involves changing one configuration value in your browser.

Changing your domain provider usually involves finding a new provider, evaluating it, setting up payments, moving a bunch of records and so on.

I know what I'd do unless I was already planning on changing my domain management.

Re: GoDaddy locks out derivatives of Chrome

#23

Post by rsstack » Thu, Jul 14, 2022, 10:57 AM UTC

sshine wrote: post #15

abirch wrote: post #10

Earlier quoted context omitted.

Too bad there's not a chance to respond, "I assume all responsibility for my unusual browser." I remember having to change the user agent string in Konqueror

You would do that rather than change domain provider?

I too would prefer to press a button once rather than change a domain provider, yes.

Re: GoDaddy locks out derivatives of Chrome

#24

Post by usrn » Thu, Jul 14, 2022, 10:58 AM UTC

pluc wrote: post #14

You already shouldn't be using GoDaddy, so there's another reason

They're a pretty terrible registrar/host but their marketing is fantastically good. Every non-tech business owner I've met uses them. It makes me kind of sad.

Re: GoDaddy locks out derivatives of Chrome

#25

Post by alias_neo » Thu, Jul 14, 2022, 10:58 AM UTC

pdw wrote: post #21

alias_neo wrote: post #13

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.

I don't envy web developers, that's a difficult situation.

I still stand by that the error message could be a lot clearer regardless.

Re: GoDaddy locks out derivatives of Chrome

#26

Post by londons_explore » Thu, Jul 14, 2022, 11:02 AM UTC

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.

Re: GoDaddy locks out derivatives of Chrome

#27

Post by pluc » Thu, Jul 14, 2022, 11:03 AM UTC

usrn wrote: post #24

pluc wrote: post #14

You already shouldn't be using GoDaddy, so there's another reason

They're a pretty terrible registrar/host but their marketing is fantastically good. Every non-tech business owner I've met uses them. It makes me kind of sad.

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

Re: GoDaddy locks out derivatives of Chrome

#28

Post by zelphirkalt » Thu, Jul 14, 2022, 11:04 AM UTC

pdw wrote: post #21

alias_neo wrote: post #13

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.

Easily solved, by sticking to web standards and not using any experimental JS features. Still them to blame, not the client browser.

Re: GoDaddy locks out derivatives of Chrome

#29

Post by rejectfinite » Thu, Jul 14, 2022, 11:05 AM UTC

No post body was provided.

Re: GoDaddy locks out derivatives of Chrome

#30

Post by jorgemf » Thu, Jul 14, 2022, 11:06 AM UTC

V-2 wrote: 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).