Sounds more like the classic we-need-a-client-for-our-service-so-we'll-buy-this-general-purpose-utility-with-a-large-fan-base-and-remove-any-functionality-that-doesn't-drive-them-to-use-our-service mistake. Don't have a Joel link for it.
Of course we couldn’t have Apple news without Gruber bashing.
"The big question, of course, is why Apple is storing this information. I don’t have a definitive answer, but the best at least somewhat-informed theory I’ve heard is that consolidated.db acts as a cache for location data, and that historical data should be getting culled but isn’t, either due to a bug or, more likely, an oversight. I.e. someone wrote the code to cache location data but never wrote code to cull non-recent entries from the cache, so that a database that’s meant to serve as a cache of your recent location data is instead a persistent log of your location history. I’d wager this gets fixed in the next iOS update.”
"The key question for Apple: Given that this file was widely known among iOS forensics experts back in September, why does it still contain historical (as opposed to just recent) location history today?”
Apps may not use users’ Instapaper data or other personal data in any way that a reasonable person would likely deem “creepy” or otherwise unacceptable. Instapaper reserves the right to decide whether an app’s usage of users’ data is creepy.