News for hackers. Stuff that matters.
Re:Pokemon Go is a huge security risk by RKoutnik on Monday July 11, 2016 @04:13PM (#12074064)
You're absolutely right - Niantic's history with Google does not preclude them having crummy security practices that we aren't aware of.

However, "Popular thing possibly has crummy security practices (we just don't know)" isn't HN-worthy, it's just FUD. I think both of us would prefer a HN full of well-researched articles over one full of clickbait FUD.

Re:Pokemon Go is a huge security risk by Sir_Substance on Monday July 11, 2016 @06:56PM (#12075451)
>However, "Popular thing possibly has crummy security practices (we just don't know)" isn't HN-worthy, it's just FUD.

Bullcrap. Best security policy is trust, but verify.

Assuming that well established businesses have good security practices without doing proper review is what allowed all those fraudulent SWIFT transactions to go through a few months ago. It's perfectly valid to ask why the hell Pokemon Go thinks it needs access to your private email.

Re:Pokemon Go is a huge security risk by aioprisan on Monday July 11, 2016 @06:19PM (#12075236)
Actually, that's all there is to "research" about this topic, as there is nothing available to read around what they could possibly use the full access tokens in any terms of service or application literature.
Re:Pokemon Go is a huge security risk by eggy on Monday July 11, 2016 @10:07PM (#12076264)
Not FUD to me. I am not going to install Pokemon Go until this is cleared up. I am glad he pointed it out, since I may have clicked through given I would have made quick judgements about them being Google-owned.
Re:Pokemon Go is a huge security risk by WillPostForFood on Monday July 11, 2016 @11:49PM (#12076605)
One thing the article is wrong about is that you can create a new account a pokemon.com (bypassing the google kerfuffle). You just need to keep reloading until it let's you past the "try again in an hour" message.
Re:Pokemon Go is a huge security risk by jeeva on Tuesday July 12, 2016 @10:51AM (#12079507)
May or may not be an issue for you - affects iOS only, if I'm reading this correctly.