Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GoDaddy locks out derivatives of Chrome

news.ycombinator.com

Post reply on HN
Print view View original

71–80 of 196 posts

Re: GoDaddy locks out derivatives of Chrome

#71

Post by ytjohn »

abirch wrote: post #10
andybak wrote: post #4

"Your browser is a bit unusual". Why, yes. Thank you for noticing. That is entirely intentional. Welcome to the web.

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

I have a user agent switcher extension for Firefox. I have a linux machine for development work, and a Windows imaged laptop for email. There are some work related sites I have to switch the agent for. I know one of the sharepoint sites was arbitrarily "locked down" to Windows only, so I report that I'm running Edge on Windows.

Re: GoDaddy locks out derivatives of Chrome

#72

Post by addingnumbers »

oriettaxx wrote: post #57
pluc wrote: post #14

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

why? I'm just curious (I do not see any bad event in wikipedia: am I missing something?)

> I do not see any bad event in wikipedia

There is a "Controversies" section of their Wikipedia article with 8 distinct sub-headings, and the section is prefixed with "For a more comprehensive list, see List of controversies involving GoDaddy" linking to another dedicated 15-section article.

https://en.wikipedia.org/wiki/GoDaddy#Controversies

https://en.wikipedia.org/wiki/List_of_controversies_involvin...

Re: GoDaddy locks out derivatives of Chrome

#74

Post by jefftk »

zelphirkalt wrote: post #28
pdw wrote: post #21

Earlier quoted context omitted.

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.

https://example.com/js"> is not an experimental web platform feature.

Re: GoDaddy locks out derivatives of Chrome

#75

Post by psz »

jrochkind1 wrote: post #48
windexh8er wrote: post #41

Earlier quoted context omitted.

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?

For .pl the transfer is free, but it also does not extend expiration period (it stays the same).

Re: GoDaddy locks out derivatives of Chrome

#76

Post by e63f67dd-065b »

_notathrowaway wrote: post #53

Speaking of registars, what does HN recommend? I was a happy namecheap user until they decided to go all political against Russian citizens. I am unsure as to what service I should migrate to.

You can’t get any better than Cloudflare, they sell domains at cost and have really good DNS tools.

Re: GoDaddy locks out derivatives of Chrome

#77

Post by patrakov »

oriettaxx wrote: post #57
pluc wrote: post #14

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

why? I'm just curious (I do not see any bad event in wikipedia: am I missing something?)

Really bad security. They still enable broken ciphers like RC4 via ssh on their shared-hosting web servers. BTW - these servers use CPanel, which runs on CentOS 6 (or a derivative), which is EOL. If your company uses any security scanner, it will flag a lot on GoDaddy.

Re: GoDaddy locks out derivatives of Chrome

#78

Post by mkl95 »

oriettaxx wrote: post #68
mkl95 wrote: post #61

Earlier quoted context omitted.

A particularly egregious example is "Tell HN: Never search for domains on Godaddy.com" https://news.ycombinator.com/item?id=24506303

uh, but I see there is a clear response cited there, too https://www.godaddy.com/garage/godaddy-felons-io-unregistere... anything else?

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

Re: GoDaddy locks out derivatives of Chrome

#79

Post by random_savv »

dicknuckle wrote: post #69
dave4420 wrote: post #52

Earlier quoted context omitted.

I thought Cloudflare had a deliberately manual (and therefore more secure but also more expensive and slower) process for registering domains. Has that changed?

I didn't have much issue with the process, it seemed like any other. A local business is a friend of mine, they were paying too much for too little from their previous web host/dev so I transferred the domain name to CF and ran their WordPress "business card" type site through a static site generator, placed all the files in GitHub, and pointed CF Pages at the repo. Whenever they want to make changes, they spin up th…

That sounds interesting. Which static site generator?

(Currently happy with the bitnami wordpress image, but wouldn't mind going 100% static!)

Re: GoDaddy locks out derivatives of Chrome

#80

Post by spaceheater »

oriettaxx wrote: post #57
pluc wrote: post #14

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

why? I'm just curious (I do not see any bad event in wikipedia: am I missing something?)

All the cool kids on HN hate GoDaddy. When prompted to elaborate the usual answer is "cuz they suck" or "I don't like their CEO". I first used GoDaddy about a decade ago, and thought nothing of it. I guess some people just like to hate. (or is it cancel nowadays?)
Post reply on HN