3 ms·
True. But when you're developing a platform, you want it to be known as a place where developers are treated fairly. Just as with their trigger-happy deletion
by jdp23 15y ago
True. But when you're developing a platform, you want it to be known as a place where developers are treated fairly. Just as with their trigger-happy deletion of apps a while ago, Facebook seems to be sending a message of "screw you, we'll do what we want". Presumably I'm not the only developers considering whether or not to invest resources in the Facebook platform who notices stuff like this.
- mkjones 15y agoA lot of that thing a few weeks ago was a mishap, not anyone trying to say "screw you, we'll do what we want." Sorry it felt that way :-/. Hopefully if you were incorrectly affected, things got resolved? Check out https://developers.facebook.com/blog/post/521/ https://developers.facebook.com/blog/post/521/ for some info on how we're trying to improve the experience when we find apps to be too spammy / in violation of policy. I think the team working on that has already made quite a bit of progress (all while still keeping spam numbers down, which is pretty impressive). Disclaimer: I work at FB, but not on the platform team.
- jdp23 15y agoThanks for the response, mkjones. I certainly don't think anybody at Facebook is _trying_ to say "screw you, we'll do what we want", and I think the new approach is a very positive step. But the impression it leaves as an app developer is that you made a change that disabled a bunch of apps without thinking about the implications, and then rolled it back when people made enough noise. As somebody else says, Facebook's got a pattern of doing this; so you don't have a reservoir of goodwill.