@KevinMontrose you could change the api URL to math.api.stackexchange, and math.meta.api.stackexchange.com. So kind of like option 3 & 4 but without the site in the query string or path.

@Kevin, isn't it possible to get a certificate that covers more than one domain?

@Kevin, at least take off the .com, having dots in the middle of an url doesn't sound that normal?

@GeorgeEdison it would be much easier to have a system as svick suggested

@Kevin, it will be possible (and allowed?) to upload a user's token to a server, so that a server can check routes needing auth-ing on the user's behalf. (e.g. for push notifications for just about every mobile platform currently available)

Yes that's what I meant to type :) somehow never made it from my brain to the keys :)

If you say exactly what you're trying to do it may be possible to help you more.

Well getting the association Id from anywhere but the API is a bit of a fluke. In 2.0 the association id will become numerical like it is on stack exchange. On normal site you can use JavaScript to get the association I'd of the currently logged in user but it doesnt seem to work on stackexchange.com

So where are you planning on getting the association_id from in the first place? You're meant to get the association_id from the route in my post, put that in the stackauth route and get all the associations.

What are you trying to do then? Get every single user's association Id?

Oh right that makes a lot more sense. So the filter stay on the server side for a while, or "forever"? When a user first uses the app it runs the filter routes, then saves the opaque values to disk (to keep them between app runs) and then never has to use the filter route again?

@kevin, oh and I never said thanks for all the hard work you and the SE team put into this, so thanks :)

@kevin, 1.1 is ok, but the pagination of sites is quite annoying, as typically you get all sites at once, rather than questions etc where you only want a few at a time.

Will any 1.0 methods be carried over, specifically the stackauth routes (starting to read the spec now so I apologise if it has been answered in it)

Thanks George (I think thats about 1800 per minute max), Something like web hooks would make this a whole lot easier, and I'm guessing less intensive.