> Shortly after thie article was published, Google silently prevented my domain from using the API:
> The client origin is not permitted to use this API.
> Welp.
So some buttons stoped working, and now you have to believe that everything was as the blog said. Well, it was.
And a "mitigation" from google being just avoiding the access to the API just makes things more interesting.
A lot of Google employees are reading HN and actively posting so no surprise. Did they at least contacted you to properly open a ticket now that they implicitely recognized the vulnerability? Otherwise very very dickish move as it solve nothing and you basically worked for free...
And now if anybody from HN team is listnening. Can you explain why this thread is fastly slipping from the front page?
Currently it’s being devanced by articles that are olders, with less upvote and fewer comments. Can you guarantee that nobody is able manipulate ranking? It’s only a hunch, but it’s not the first time that I notice that google related "bad buzz" move away from main page slightly faster than other...
PS: I’ll gladly accept downvotes. But answers on why I’m wrong or paranoid would have been better
There appear to be quite a few flags on the article pushing it down. The ratio of upvotes to age compared to the rest of the front page is a strong indicator of this.
Also: lots of HN'ers work at google. It would be a nice rule if people were told to abstain from using their flagging privileges when the company they work at is the subject of a thread.
It's probably because a lot of Google folks are on here - protecting their brand. Unfortunately that part isn't transparent, but its hopefully a minor issue.
So some buttons stoped working, and now you have to believe that everything was as the blog said. Well, it was.
And a "mitigation" from google being just avoiding the access to the API just makes things more interesting.