31–40 of 57 posts
I don't see the stack overflow model as being a great fit for what facebook api developers need. The main problem I saw with facebook api was that the right way to do things kept changing, and the docs and forum didn't keep up well. You basically needed to begin facebook API work by reading the entire blog in chronological order and then keep on scanning the dev blog daily, which may work ok if you're a fulltime face…
I don't see the stack overflow model as being a great fit for what facebook api developers need. The main problem I saw with facebook api was that the right way to do things kept changing, and the docs and forum didn't keep up well. You basically needed to begin facebook API work by reading the entire blog in chronological order and then keep on scanning the dev blog daily, which may work ok if you're a fulltime face…
I don't see the stack overflow model as being a great fit for what facebook api developers need. The main problem I saw with facebook api was that the right way to do things kept changing, and the docs and forum didn't keep up well. You basically needed to begin facebook API work by reading the entire blog in chronological order and then keep on scanning the dev blog daily, which may work ok if you're a fulltime face…
Maybe developers should just start an unofficial Facebook Wiki.
I don't love that facebook.stackoverflow.com looks exactly like stackoverflow.com — there’s no easy way to tell where you are, or to get back to the main stack overflow. Even more confusing, you can get to un-Facebook-related questions on facebook.stackoverflow.com (e.g. from your inbox, or from a user page). Since there are no redirects between regular and Facebook SO, this means that every question on Stack Overflo…
At first I figured they just created a separate SE site specific to Facebook development but it appears to just be a filter on all questions which have a tag that contains "facebook" while hiding all others.
Why not just create another stack exchange just for facebook? I mean, they've already got that system working for other topics.
Putting a filter on all SO questions and slapping a subdomain on it feels like it's a solution they created in 30 seconds.
Accurate or no?
e.g. Facebook offers devs with over X reputation access to alpha APIs, devs with over Y reputation direct email support, devs with over Z reputation are recommended on the Facebook.com site as developers to hire for freelance work, etc.
I don't see the stack overflow model as being a great fit for what facebook api developers need. The main problem I saw with facebook api was that the right way to do things kept changing, and the docs and forum didn't keep up well. You basically needed to begin facebook API work by reading the entire blog in chronological order and then keep on scanning the dev blog daily, which may work ok if you're a fulltime face…
Why try and build your own community when there's already an existing one with a lot of useful questions, engaged moderators and smart people answering?
Especially when you've failed to support your existing community at all.
Earlier quoted context omitted.
At first I figured they just created a separate SE site specific to Facebook development but it appears to just be a filter on all questions which have a tag that contains "facebook" while hiding all others.
Yeah, that's what I thought. Why not just create another stack exchange just for facebook? I mean, they've already got that system working for other topics. Putting a filter on all SO questions and slapping a subdomain on it feels like it's a solution they created in 30 seconds.
Second, programmers can keep their existing reputation, while a new SE site would put everyone back to 100. Since the topic is a subset, keeping it makes sense.
I don't really see what problems this solution brings that can't be solved with a custom logo.
I would love to see companies with APIs and active developer communities provide rewards to high reputation developers. e.g. Facebook offers devs with over X reputation access to alpha APIs, devs with over Y reputation direct email support, devs with over Z reputation are recommended on the Facebook.com site as developers to hire for freelance work, etc.
I don't see the stack overflow model as being a great fit for what facebook api developers need. The main problem I saw with facebook api was that the right way to do things kept changing, and the docs and forum didn't keep up well. You basically needed to begin facebook API work by reading the entire blog in chronological order and then keep on scanning the dev blog daily, which may work ok if you're a fulltime face…
Many developers I know, myself included, avoid facebook integration like the plague for just this reason. Other services manage to version their APIs and depreciate them gracefully. Facebook apparently doesn't understand how to do this, or simply doesn't care.
They didn't care. They didn't have to. Now they do, because they have to. (Hello, Google+)