Answers should take the form of feature requests/modifications that are either obviously beyond the scope of v1 and or have been status-declined or status-deferred
They will be indexed here in the Q.
id value into the query string
In that the id is vectorized, it is designed to represent multiple values.
id field is a component of the url. This severely constrains the number of records that can be retrieved far below the stated maximum of the max
pagesize which is 100.
Another, more serious, implication of this limitation is that, with
id in the url, the limit is arbitrary and undefined, which is never a good thing, requiring trial and error to find the max url length in respect to the variable length
id, or make many single
id requests increasing load on the server.
id were a query string component, it is quite possible to issue a request for 100 items even with large
id. Currently, using short
id values, the server starts issuing errors at ~30 items.
What I would like to see:
Which would obviate the necessary hack described here
This is an obvious one (and a stated goal for V2, I think).
The basics would be for some way to authenticate a user against his StackOverflow/etc user. Also, a way to access the "linked accounts" information would be great (so authenticating a StackOverflow user will automatically give the application knowledge of his other accounts which are linked to the same user).
That last part might be problematic, so some way of letting the user disallow sharing the linked info/informing the user is important.
At this stage I see no way to get what questions and answers user has voted on. It would be good to have this ability for future releases of my app.
Seeing other user's votes is a pretty bad idea as they are meant to be private.