12

As has been announced, we're starting the public beta and spinning up a contest (as we did with V1.0).

As such, some of the guidelines for the private beta no longer apply.

The tag no longer exists, questions pertaining to V2 should merely be tagged . I've deleted most of the private-beta specific posts, as I said I would.

You can now list V2.0-only applications just like any other, likewise for libraries.

We're also switching gears a bit, posts are much less likely to be implemented now as we're striving for stability now. There are still a couple of things in the "maybe" pipeline, but the bar has been raised on new suggestions.

Some of things that we know still need polish/completion:

  • the app authorization dialog
    • it's gotten better, but still a bit rough UI wise
    • still not HTTPS pure, we're working on getting all app icons onto our CDN to alleviate this
  • request stats not implemented
    • authorization stats were more important
    • this should be done this week or early next week
    • delay caused by minor holdups in getting the data into a quick to query form
  • type documentation
    • there have been improvements, but type docs aren't nearly as well polished as method ones
    • compare /questions and the question type
    • we're still very much open to suggestions for improving the docs
Improve this question
6
  • 2
    Not sure if this is the right place, but: If the suggested edits queue is now completely public via the API, what's the point of not making it available via the site until 5k rep? Low-rep users have no business there, but you can review starting at 2k.
    – a cat
    Commented Dec 27, 2011 at 2:29
  • 2
    @lunboks - user's can't act on suggested edits until they hit higher rep, so showing them on the sites would be confusing. The same objections don't apply to the API, as there's no-one to confuse.
    – Kevin Montrose
    Commented Dec 27, 2011 at 2:49
  • @KevinMontrose Is there a list of which features are new in 2.0? I'm thinking of entering the app contest and want to make sure I don't write an app that ends up using only older calls.
    – Adam Lear Staff♦
    Commented Dec 27, 2011 at 4:53
  • @Anna - the most obvious new thing is authentication, but the most important thing is hitting the /2.0/ endpoint and not the /1.x/ ones. Most of the workhorse methods are very similar, by design.
    – Kevin Montrose
    Commented Dec 27, 2011 at 4:55
  • Contest... yaaaaay!
    – Nathan Osman
    Commented Dec 27, 2011 at 5:01
  • I assume the 1.1 registration page will stick around at least until the public beta is over; can that page be updated to be explicit about it being for 1.1 keys like the 2.0 one is? There's been a few cases recently where people have signed up for a 1.1 key inadvertently then been confused when it doesn't work against the 2.0 API, possibly in part because the 1.1 registration page is the one linked from /about
    – Tim Stone ♦
    Commented Feb 2, 2012 at 20:27

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .