@Makyen My theory would be that the request isn't pinned to a specific server and the different servers have different baseline configurations for max URL length. The error message is happening before we reach the application code and the message is just IIS's way of saying it can't interpret the URL. If it got past that, we'd end up with JSON.

I'll be looking into this but my gut feeling is that the URL is just too long. Historically, the maximum URL length was 923 characters (or maybe bytes?) but I'm not sure what it's currently set at. In the iOS app, I did batching of requests like this to limit the URL length.

Right now, the apps tab includes questions tagged either app or library.

1 and 2 would be fairly straightforward to implement. The query becomes app -placeholder -obsolete or library -placeholder -obsolete and knocks out about 50 apps. Setting min score to 2 knocks out maybe 20 more. 3 and 4 are more complicated because they scan the body after the list already loaded. The easiest thing would be to move items that pass 3 and 4 to the top of the list.

@ShadowWizard Guess I should rephrase. The app will still have some key features from SE.app. Split list and item view in landscape, live question preview, but it isn't getting special UI treatment in the way of having it's own special navigation compared to iPhone and it won't have its own custom user profile view. Some views will definitely be sparse or overly spread out compared to their iPhone counterparts, but probably not much more so than in the SE app.

@ShadowWizard It was just going to be iPhone initially, but now it's going to be iOS without much special treatment on iPad. Updated.

@BrockAdams There's no timeline yet for new features (and API backing them), just focussed getting the app working. Still, there are some smaller changes like submitting suggested edits, tag preferences, and can_ fields ready for 2.3 when I get the app shipped.