Live data from Hacker News

Thanks HN: Lessons learned after Google nearly killed my site

uploader.win

111–120 of 296 posts

Re: Thanks HN: Lessons learned after Google nearly killed my site

#111

Earlier quoted context omitted.

> This account "owns" digital goods, thousands of songs, and many domain names. Google is actively stealing these things, but they don't care and, "can't help". I long for the day that they cross the wrong person with means to take them to court over their negligence.

My very-much-not-a-lawyer understanding is that their legal obligations and liabilities are minimal on account of Gmail being offered free of charge. Anyone know if that's true?

Not true.

Say I offer my front yard for anyone to use for free.

You come and set up a bbq stand to have a picnic with your friends. You walk across the street to a lemonade stand, and when you return, you're confronted with a security guard who won't let you back into my yard.

You demand entry, saying your property is in my yard. You want to speak with me, but the security guard says you can't do that. What you can do is head over to the town square and ask if anyone there knows how you can regain access to your property.

Re: Thanks HN: Lessons learned after Google nearly killed my site

#112
Website blacklists exist because of malware and phishing. Malware exists because our browsers and OS's are insecure. Phishing exists because our auth systems are insecure. Solving software security and auth will have wide positive effects on society.

Re: Thanks HN: Lessons learned after Google nearly killed my site

#113

> But there are plenty of Google engineers and good helpful people on Hacker news. > (from a screenshot) I work at Google [...] so I escalated your issue [...] > I believe the HN thread getting on the homepage tremendously helped me and somebody from Google saw it and expedited the review after all So, once more an issue with FAANG could only be fixed because somebody knew somebody else and went out of his way to get…

You're not the only one who finds it unbearable. Google acts like they own the internet. They cause massive damage to people and businesses when they unilaterally block them. They compound that damage by refusing to resolve the issue unless people somehow manage to reach some insider.

Re: Thanks HN: Lessons learned after Google nearly killed my site

#114

> But there are plenty of Google engineers and good helpful people on Hacker news. > (from a screenshot) I work at Google [...] so I escalated your issue [...] > I believe the HN thread getting on the homepage tremendously helped me and somebody from Google saw it and expedited the review after all So, once more an issue with FAANG could only be fixed because somebody knew somebody else and went out of his way to get…

The worst part is that we are just conditioning people to accept this as normal. Just like EULA and cookie banners. It's always the same story. Some guy gets on Twitter or HN who happens to get noticed, then FAANG releases a statement saying they made a "mistake". Mistakes in the aggregate that affect millions of people aren't "mistakes." That's deliberate malfeasance at scale. Funny they never ask you that design qu…

Upvote for Brazil! Great movie, Gilliam is a genius, so good. https://m.imdb.com/title/tt0088846/

Re: Thanks HN: Lessons learned after Google nearly killed my site

#115
post #43

Earlier quoted context omitted.

A secret set of rules, a single party that is the judge, jury and executioner, an opaque resolution process that involves backchannels rather than merit, and no oversight ? Is that really something to accept as inevitable ?

Yes, networking is inevitable. Transparency and accountability are hedges against this, but incentives aren't there short of some sort of massive public pressure.

Massive public pressure means.... sounds like legislation to me.

Re: Thanks HN: Lessons learned after Google nearly killed my site

#116

> But there are plenty of Google engineers and good helpful people on Hacker news. > (from a screenshot) I work at Google [...] so I escalated your issue [...] > I believe the HN thread getting on the homepage tremendously helped me and somebody from Google saw it and expedited the review after all So, once more an issue with FAANG could only be fixed because somebody knew somebody else and went out of his way to get…

I can't access my 13+ year old gmail account because Google now requires I verify I have access to a phone number I've never owned. There is no 2FA on this account, I know my password, and have access to the "Recovery Email" (which gets emailed a "Somebody knows your password" warning whenever I attempt to sign in to the account with my password). I reached a real person at Google Domains and managed to get things es…

I can't access my flickr account because it's tied to a Yahoo account which won't let me access unless I know the 2nd Yahoo account email address 2fa which is blurred out and yahoo won't let me access it because it's been locked even though I know all the info.

Re: Thanks HN: Lessons learned after Google nearly killed my site

#118
post #18

They can remove your YouTube account, app, entire Google account or even your website at any time and you can only make guesses why did that happen, because they always make the rules really vague and it's never clear what is or is not allowed. And even when they do admit the mistake and get you back up, they still won't explain anything and nothing is ever fixed. Thank you Google, very cool.

I am now left wondering about the .dev gTLD, isn't it owned by Google?

Yep. Adjust risk factors as necessary.

https://en.m.wikipedia.org/wiki/.dev

Post reply on HN