Take the 2-minute tour ×
Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.

If I call the Auth "sites" API, then it shows Meta Stack Overflow as:

  "name": "Meta Stack Overflow",
  "logo_url": "http://sstatic.net/stackoverflowmeta/img/logo.png",
  "api_endpoint": "http://api.meta.stackoverflow.com",
  "site_url": "http://meta.stackoverflow.com",
  "description": "Q&A for the Stack Exchange engine powering these sites",
  "icon_url": "http://sstatic.net/stackoverflowmeta/img/apple-touch-icon.png",
  "state": "normal",
  "styling": {
    "link_color": "#3D3D3D",
    "tag_foreground_color": "#6F6F6F",
    "tag_background_color": "#E7E7E7"

Is the "normal" state incorrect here? Or is Stack Overflow a "special" case?

share|improve this question
add comment

1 Answer 1

up vote 4 down vote accepted

No, this is expected behavior, Meta Stack Overflow is indeed a special case - see the original Per-Site Metas announcement, specifically the last paragraph:

For now we are leaving meta.stackoverflow.com grandfathered in, as-is, with no changes; it’s still a standalone community with a standalone reputation system. We think Stack Overflow is large enough to justify this, and it just so happens that Stack Overflow is also the name of the company, too. Meta Stack Overflow will serve as the “National Capital” where we process feedback not just for Stack Overflow but for the core engine itself — while the smaller meta sites are akin to regional or state capitals.

I've submitted a follow up question Shouldn't you take the plunge and have a per-site Meta for Stack Overflow too in favor of meta.stackexchange.com? back then, and Jeff Atwoods answer indicates that this isn't going to change anytime soon, though still something they might reconsider in the future.

share|improve this answer
add comment

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .