4 ms·

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 th

by Simucal 15y ago

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.

joelhaasnoot 15y ago
More and more this is just a patch for the problem, while what they need is a 180 degree turn and commit to actual developers. Facebook treats its developers just like its users and throws out updates, new features and changes very very often. With so many users they can afford it for their users, but they need to see they can't just do that for their developers. As a user there are so many little bugs and quirks in Facebook, especially in the News Feed, that popup and a few days later disappear. Facebook needs to realise they need developers too, and that many advertisers run campaigns on their facebook pages, meaning that the API is not just a fun addon for users, but a money maker too.
andypants 15y ago
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.
- icebraining 15y ago
  Well, first off Facebook API questions are still on-topic on SO, so they will have more eyeballs and therefore a greater probability of being answered. 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.
  - click170 15y ago
    I agree with your second point, but your first point goes against established precedent at Stackexchange. I mean, if it was about getting more eyeballs then I think the best way to go would have been to use tagging, so that questions would be posted to 'stackexchange' and would then be tagged with 'programming', 'codereview', 'superuser' etc and as they were tagged they would show up on the programming.stackexchange.com (and other) sites. IIUC the current way is that if I post a programming question to stackoverflow, it will get 'migrated' to programming.stackexchange. That works, but it detracts from the total number of eyes because it is removed from stackoverflow. That design decision is something that has always kind of confused me about the Stackexchange sites.
    - icebraining 15y ago
      It's about the topic of the site. FB API questions are on-topic with SO, others aren't. The Code Review is debatable since it's arguably a subset of SO, but other SE sites (like Programmers) don't really intersect that much.
- scorpion032 15y ago
  > Why not just create another stack exchange just for facebook? If Facebook wanted to, it is not like they can't write a question-answer site or use one of the open source alternatives. This is an endorsement of Stackoverflow from facebook. Nothing more.

by Simucal 15y ago

joelhaasnoot 15y ago

More and more this is just a patch for the problem, while what they need is a 180 degree turn and commit to actual developers. Facebook treats its developers just like its users and throws out updates, new features and changes very very often. With so many users they can afford it for their users, but they need to see they can't just do that for their developers. As a user there are so many little bugs and quirks in Facebook, especially in the News Feed, that popup and a few days later disappear. Facebook needs to realise they need developers too, and that many advertisers run campaigns on their facebook pages, meaning that the API is not just a fun addon for users, but a money maker too.

andypants 15y ago

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.

icebraining 15y ago
Well, first off Facebook API questions are still on-topic on SO, so they will have more eyeballs and therefore a greater probability of being answered. 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.
- click170 15y ago
  I agree with your second point, but your first point goes against established precedent at Stackexchange. I mean, if it was about getting more eyeballs then I think the best way to go would have been to use tagging, so that questions would be posted to 'stackexchange' and would then be tagged with 'programming', 'codereview', 'superuser' etc and as they were tagged they would show up on the programming.stackexchange.com (and other) sites. IIUC the current way is that if I post a programming question to stackoverflow, it will get 'migrated' to programming.stackexchange. That works, but it detracts from the total number of eyes because it is removed from stackoverflow. That design decision is something that has always kind of confused me about the Stackexchange sites.
  - icebraining 15y ago
    It's about the topic of the site. FB API questions are on-topic with SO, others aren't. The Code Review is debatable since it's arguably a subset of SO, but other SE sites (like Programmers) don't really intersect that much.
scorpion032 15y ago
> Why not just create another stack exchange just for facebook? If Facebook wanted to, it is not like they can't write a question-answer site or use one of the open source alternatives. This is an endorsement of Stackoverflow from facebook. Nothing more.