John - I am working on switching my /read calls to pass parameters in the body of the request, but I want to let you know about some serious problems with that, which probably explain why I'm using the URL form for passing parameters in the first place.
It looks like the URL will ignore most parameters in the body. For example, if I try to ask for a specific id, or ask for only posts of draft format, it just returns the regular list of posts. Similarly, the start offset is ignored, so paging requests of posts is impossible.
I'm going to assume that NO parameters to /read should be put into the body of the post except for the authentication parameters.
Seeing as how the parameters in the body are ignored, it seems safe to assume that ALL clients who are currently using the V1 API are in fact passing parameters in the URL and not in the body of the request. Thus probably all V1 clients who use /read are affected by this issue.
WIll you please consider restoring the old behavior at least until you have a chance to consider the implications on clients? My support inbox is starting to ramp up with inquiries from affected customers.
Daniel