I really don't understand why google released their api with a 1k/day limit. I could see this being a problem for a weekend hackathon. How many people are going to devote time to a real project reliant on any api with such a low api limit... my guess, not many.<p>TL/DR- 89n requested a limit bump to 1m requests/day but only got 10k/day.<p>Facebook's open graph seems to have a 100m/day/app limit.
(<a href="http://www.quora.com/Whats-the-Facebook-Open-Graph-API-rate-limit" rel="nofollow">http://www.quora.com/Whats-the-Facebook-Open-Graph-API-rate-...</a>)
This is just one reason that providing a good, robust API is so important: people will just page-scrape.<p>In the early days of audioscrobbler/last.fm, I added comments to the HTML of our pages, asking people who were writing scrapers to get in touch so we can add additional webservices.<p>It's much cheaper to serve up an API request, and trying to block scraping is futile.
Has anyone else had a better experience with the Google+ API? It really worries me that this means that no businesses can be built on top of the G+ API. Less developer investment means less options for users. Data becomes less open.