This way it's ruined for everybody, and they get nothing in return, except for some HN points on their blog post.
There was no real-world case where this data was useful in a non-creepy way.
I'd prefer that it was. This is clearly something that leaks personal information.
And, you know, some increased measure of privacy.
For some odd reason people seem to be concerned about all the private data they (willingly) give to these corporations leaking outside of the corporation proper as if it's a violation of their (misplaced) trust or something. Lots of that going around recently for...reasons.
I haven't used OkC since then, but I thought I'd share that in the context of this blog post ;-)
Pet peeve of mine, but too many people don't even think about it and just procreate because it's part of the Standard Life Script™.
The site has changed quite a bit then. Now you would of never been able to message her unless she "liked" you.
How can the developers behind an endpoint like this not confirm/test that it requires permissions/authentication to consume? (I mean, look at all that data...)
Amateurs I can understand - but OKCupid has been around long enough they shouldn't be employing people of that nature.
Is there no code review process?
This is just nuts.
And I will tell you on sprints where anyone is busy that team introduces something sloppy or nutty when one of us does not watch closely and ask, sometimes both. But when I point things out people are eager to roll it back.
Never attribute to evil that which comes from ... you get the idea!
It works so no one complains.
Are you implying that it's not outlanding for professional programmers to not have these things in mind?
Disclosure: Paying OKCupid customer. I don't mind paying to support the service, it's provided ongoing value to us.
Aside from a token few they can blog about, what's their incentive to be successful?
I've seen too many 300+ lb women describe themselves as "average".
Is that a multi-user account? Or are you guys swingers or something?
5 miles in LA can be a long drive. So I wrote a chrome plugin to add additional drop down options of 0.1, 0.5 and 1 mile. I was surprised to see it work.
It was awesome.
There is also a hack to get the infamous “top X% of hottest people” feature unlocked... :)
I mean, it was obviously a bug, right? I imagine the only "explanation" would involve detailing the origin and nature of the bug which would be unwise until they've gone through all their other endpoints to ensure that there's not another instance of this same information leaking.
