I know you wanted to reduce the amount of data returned, but hasn't it gone a little far? Especially as there are no numerical site IDs. For example the Apple site is now called AskDifferent, however the API returns in both stackauth routes that the name is Apple.
It means that the site names can change, it would be more useful to have site URL rather than site name, even though that would increase requests, because if you were displaying a list of associated sites then you'd need to go a request the site name from every single site.
Also with reputation, [many] apps show global reputation, that is now much harder, as a request has to be made to every single site to get the user's reputation.
Plus the reason for the reduction in information is to save bandwidth, yet the
/sites route has increased in size. And the associated route, returns the associaton_id for each site; this is exactly the same for each site, and the association_id is part of the request, so the app will already know it.
I know we can still use 1.0, but 1.1 is the direction the API is heading right? So when 2.0 and 3.0 come along we'll be left with the 1.1 route.
In total, I'm asking for the reputation and site url to be added to the