5 ms·

> 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

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

bobross 8y ago
This is what you would see if it still worked: https://twitter.com/LiveOverflow/status/994560352149999616 https://twitter.com/LiveOverflow/status/994560352149999616
deleted 8y ago
[deleted]
ComodoHacker 8y ago
API ban was probably automatic due to HN effect.
- bobross 8y ago
  Actually Google temporarily shuts down the service as I've tried changing API keys/domains but received the same error
  - Twisell 8y ago
    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...
    - bobross 8y ago
      Nothing
      - Twisell 8y ago
        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
        deleted 8y ago
        [deleted]
        lerpa 8y ago
        Although I don't think this is some sort of conspiracy, HN front-page is curated content, ranking is not only based on votes.
        deleted 8y ago
        [deleted]
        jacquesm 8y ago
        Flags are a factor, and function as downvotes on articles but are much heavier weighted than upvotes.
        jacquesm 8y ago
        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.
  - CC11 8y ago
    Ho do I hack into google I'm a kid and I want to make it say giberish instead of Google
    - CC11 8y ago
      does anyone know?
- pavel_lishin 8y ago
  That doesn't sound plausible; what sort of service would YOLO be if a popular website using it resulted in an API ban?
technion 8y ago
I know I'm just one person - but I can confirm the content of the blog was accurate and the described attacks did work at the time I read it.
kerng 8y ago
Quite a sketchy move from Google... Hope OP will eventually get a big bounty paid out.
- mkagenius 8y ago
  > Google Big companies trying to strangle hold the small ones -- nothing new, time to move on. Its pathetic.

bobross 8y ago

This is what you would see if it still worked: https://twitter.com/LiveOverflow/status/994560352149999616 https://twitter.com/LiveOverflow/status/994560352149999616

deleted 8y ago

[deleted]

ComodoHacker 8y ago

API ban was probably automatic due to HN effect.

bobross 8y ago
Actually Google temporarily shuts down the service as I've tried changing API keys/domains but received the same error
- Twisell 8y ago
  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...
  - bobross 8y ago
    Nothing
    - Twisell 8y ago
      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
      - deleted 8y ago
        [deleted]
      - lerpa 8y ago
        Although I don't think this is some sort of conspiracy, HN front-page is curated content, ranking is not only based on votes.
        deleted 8y ago
        [deleted]
        jacquesm 8y ago
        Flags are a factor, and function as downvotes on articles but are much heavier weighted than upvotes.
      - jacquesm 8y ago
        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.
- CC11 8y ago
  Ho do I hack into google I'm a kid and I want to make it say giberish instead of Google
  - CC11 8y ago
    does anyone know?
pavel_lishin 8y ago
That doesn't sound plausible; what sort of service would YOLO be if a popular website using it resulted in an API ban?

technion 8y ago

I know I'm just one person - but I can confirm the content of the blog was accurate and the described attacks did work at the time I read it.

kerng 8y ago

Quite a sketchy move from Google... Hope OP will eventually get a big bounty paid out.

mkagenius 8y ago
> Google Big companies trying to strangle hold the small ones -- nothing new, time to move on. Its pathetic.