Slashdot Mirror
Facebook Mistakenly Leaked Developer Analytics Reports To Testers (techcrunch.com)
This week, an alarmed developer contacted TechCrunch, informing us that their Facebook App Analytics weekly summary email had been delivered to someone outside their company. TechCrunch: It contains sensitive business information, including weekly average users, page views and new users. Forty-three hours after we contacted Facebook about the issue, the social network now confirms to TechCrunch that 3 percent of apps using Facebook Analytics had their weekly summary reports sent to their app's testers, instead of only the app's developers, admins and analysts. Testers are often people outside of a developer's company. If the leaked info got to an app's competitors, it could provide them an advantage. At least they weren't allowed to click through to view more extensive historical analytics data on Facebook's site. Facebook tells us it has fixed the problem and no personally identifiable information or contact info was improperly disclosed.
information wants to be free, as in speech, so this was a success.
IN SOVIET RUSSIA... Developer analytics reports leak Facebook.
no personally identifiable information or contact info was improperly disclosed
Nope. No, it was properly disclosed.
We test in production goddamnit!
Facebook can be trusted with your data.
They are spending millions and millions of dollars to make sure you get this wonderful news.
Check your premises.
The only mistake here is that Facebook was not being paid.
I'm a good cook. I'm a fantastic eater. - Steven Brust
Nothing, nothing happens @ Facebrook by accident...
CAP === 'contrast'
I did receive a copy of those reports.
The most interesting parts were that last week:
1) cre!mer spent 32.5 hours recording a single video that he then published on YouTube.
2) cre!mer spent another 41.2 hours spaying links to said video wherever he could.
3) cre!mer spent 11.5 hours searching for click-bot providers.
4) cre!mer made 2.38$ in revenue with his venture, minus 20$ paid to his click-bot provider.
oops..my towel slipped again..by mistake.
This is the sharing economy. The data wants to be shared. This is a feature, not a bug, to opt out all the devlopers had to do is follow a simple 100 step privacy checkup, upload all their personal data, includ ing a photocopy of their current passport, sign a waiver, stand and their head, and chant yay facebook!
You deep down are in love with this 'Creimer' person. C'mon, it's okay to admit it. You love Creimer. Let it all out, cry. It's all-right... That's it, let it all out honey, we got you... Feel better?
Good. :) Now please, find another outlet in life. Have you tried tennis?
Let's get real, FB wants to monetize all of your metadeta and your data, and will do it any way it can.
So they may claim it was a bug, but they planned to include it in a Premium add-on for the people they sell your data and metadata to, is my extrapolation, based on their prior behavior.
-- Tigger warning: This post may contain tiggers! --
"DevOps"
"Agile"
"Continuous Deployment"
These are all the constituent paradigms of a cancerous "engineering" culture that Facebook hath deemed "Move Fast And Break Things".