Live data from Hacker News

Thanks HN: Lessons learned after Google nearly killed my site

uploader.win

231–240 of 296 posts

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

#231

>Now we run automated tests to monitor server uptime and check server for problems every 30 seconds. Unfortunately automated test scripts were happily getting HTTP/200 replies while people using the Chrome browser were being told this is a scam business trying to steal their bank account information. I was surprised this wasn't part of the lessons learned. But it seems the monitoring basically failed but that wasn't…

I wonder if there are page monitoring utilities that can download the full html payload, render the page via a headless chrome browser, and then perform a diff against the content? Most landing pages are quite static, and like you said, it's about full page load, so measuring how long the entire page took to load, along with each asset's network request and subsequent content paints, you could get a pretty good idea of your holistic page load health.

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

#232

Earlier quoted context omitted.

No. Absolutely hard disagree. To give you an example of this working well: In some countries(UK) regulators recognized that you cannot operate in the society without a bank account. So a rule was made that a bank cannot close down your bank account without a court order. They can block your access to nearly all other services, block all of your cards, but at the end of the day, you cannot lose access to your basic ba…

> you cannot lose access to your basic bank account and money in that account unless a judge says otherwise. "Losing access to the money in that account" is blatantly stealing from you. It's should be obvious that no company should be able to do this under any circumstances, but that is a separate issue from the question of adequate competition. You still need competition because a monopoly can find an unlimited numb…

> Which allows banks to remain an uncompetitive yet inherently necessary market. But how is that better than having enough competition between banks that anyone can find one willing to provide service?

Just because the market is regulated doesn't mean there is no competition.

It's better because the banks can't gang up on you like tech companies do. At least in the EU.

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

#233
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.

One one hand I understand that any site can be hacked anytime and that that can have huge repercussions, therefore I'm happy if Google reacts quickly when it detects something like that (if I were the owner of such a site I would be even thankful to Google to limit the damage). One the other hand it seems, based on this and many other posts, that there isn't much communication from Google to its "clients" to 1) expla…

Google doesn't need to explain to him anything because he is not their client. That's the problem we have now. Google have become judge and executioner. They are also decide what gets distributed because they own a browser used by most users. The solution to this is just stick to the basic, let the browser be a browser and the search engine just a search engine.

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

#234
post #217

Earlier quoted context omitted.

Surely there is a better way to address malicious content than blocking the entire domain. It also doesn't seem like sites like Facebook, Reddit, Youtube, Google photos, etc. run into this problem, even though they allow user uploaded content so there is some kind of bias against smaller companies.

You won't get away with uploading malware to your Google drive without Google noticing. The no-no here is that this guy is operating a demo site that allows anonymous file uploads without policing the content that goes there. That's just mind blowingly dumb and ripe for abuse.

So you need a google quality malware detection filter to allow user content upload on your site? That's a pretty big barrier to entry.

And I find it hard to believe that there isn't any malware or phishing content on any of the big content provider's properties.

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

#235
post #232

Earlier quoted context omitted.

> you cannot lose access to your basic bank account and money in that account unless a judge says otherwise. "Losing access to the money in that account" is blatantly stealing from you. It's should be obvious that no company should be able to do this under any circumstances, but that is a separate issue from the question of adequate competition. You still need competition because a monopoly can find an unlimited numb…

> Which allows banks to remain an uncompetitive yet inherently necessary market. But how is that better than having enough competition between banks that anyone can find one willing to provide service? Just because the market is regulated doesn't mean there is no competition. It's better because the banks can't gang up on you like tech companies do. At least in the EU.

But regulation is being proposed as an alternative to competition. It can't do that. You need competition whether or not you have regulation.

Look at what a dumpster fire every regulated private monopoly is. "Success" is a stagnant inefficient bureaucracy that ossifies everything it touches. Failure is the F-35 wasting a number of public dollars with twelve zeroes after it.

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

#236

>Now we run automated tests to monitor server uptime and check server for problems every 30 seconds. Unfortunately automated test scripts were happily getting HTTP/200 replies while people using the Chrome browser were being told this is a scam business trying to steal their bank account information. I was surprised this wasn't part of the lessons learned. But it seems the monitoring basically failed but that wasn't…

I wonder if there are page monitoring utilities that can download the full html payload, render the page via a headless chrome browser, and then perform a diff against the content? Most landing pages are quite static, and like you said, it's about full page load, so measuring how long the entire page took to load, along with each asset's network request and subsequent content paints, you could get a pretty good idea…

I've seen automated testing tools for that. I was thinking about it for the future once I get other monitoring I want. I'm literally building this to be a monitoring tool I want to use. But you would have to make the montioring system aware of deployments or design changes. But those are the things that generally break things.

But the key thing for me is the "goal" montioring. So for ecommerce it's orders but for other systems it's different. That's the thing I really want to monitor. If other things break they'll affect those so you can detect lots of failures. The only issue is finding out what the cause is. But first I'll improve the anomaly detection a bunch before looking into root cause detection.

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

#237
post #164

Earlier quoted context omitted.

Go figure why nobody keeps them accountable. They have enough money to influence the USA government if anything changing the situation were to be introduced.

They're a frequent target of rhetoric and legislation by the republicans. Granted, nothing comes of it because the fundamental issue they have is that reality has a liberal bias.

The actual issue is that reality has a bias towards people with deep pockets.

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

#238
post #232

Earlier quoted context omitted.

> Which allows banks to remain an uncompetitive yet inherently necessary market. But how is that better than having enough competition between banks that anyone can find one willing to provide service? Just because the market is regulated doesn't mean there is no competition. It's better because the banks can't gang up on you like tech companies do. At least in the EU.

But regulation is being proposed as an alternative to competition. It can't do that. You need competition whether or not you have regulation. Look at what a dumpster fire every regulated private monopoly is. "Success" is a stagnant inefficient bureaucracy that ossifies everything it touches. Failure is the F-35 wasting a number of public dollars with twelve zeroes after it.

As a solution to this particular problem, not banking overall. And we're not talking about central banks, but normal banks. The competition is still there.

Tell me, why shops are not allowed to discriminate on the basis of race? Why not just have competition deal with that?

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

#239
post #190

Earlier quoted context omitted.

Whose should it be? Why would they be better than Google?

The job of the police

At least in the Bay the police can't even stay in the confines of the laws they're sworn to uphold (stop signs, speed limits, not drunkenly swerving into the bike lane I'm inhabiting, ...). What reason do we have to believe they'd handle an unfamiliar problem domain with any better proficiency?

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

#240

So, clearly Google has too much power over the internet, it's arbitrary and opaque, etc. I agree. However, I think it is worth pointing out that: 1) malware is often very aggressive and fast-spreading, and once it's on a user's computer it's hard to get off, therefore... 2) the system to detect it and stop access to the site has to be automated, not a human-in-the-loop system that might take hours or days to shut off…

I think if Google is going to decide to police the web like this, they need to alert people more proactively. The first the OP should have heard of this was Google emailing them through uploader.win's Contact Us email address. It's easy and obvious to find on the site; seems like that should be part of the automated process.

Locating contact info for websites is not something that can be automated. Some sites provide an email address, some a form, some point people at twitter or facebook and some don't provide any contact information at all. None of this is arranged in any sort of standard way. Contact info may be under a link marked "contact" or "about" or "bio" or appear at the bottom of every page.
Post reply on HN