100% agreed Peter. Since Day One there has been a horrendous amount of redundant inquiry on this list.
Is the information just not obvious enough? Not organized or presented well enough? Thanks- - Andy Badera - and...@badera.us - (518) 641-1280 - Tech Valley Code Camp 2009.1: http://www.techvalleycodecamp.com/ - Google me: http://www.google.com/search?q=andrew+badera On Tue, Feb 10, 2009 at 6:15 PM, Peter Denton <petermden...@gmail.com>wrote: > Ok, this might come across as being sarcastic, but I am being 100% genuine > here. > > My question is: how do you miss this? > > Again, not trying to piss anyone off, but seriously asking a question > hoping you might provide some insight for a product manager. > > Would it be better if you: > > - received an email with a "read this first"? > - were forced to play in a sandbox and simulate worst case scenarios? > - were allowed to pay for immediate whitelisting? > > I am just curious on this. I know these are delicate questions, but would > love any feedback. > > > > > On Tue, Feb 10, 2009 at 2:57 PM, Sunny <sunde...@gmail.com> wrote: > >> >> Hi Matt, >> >> We have the exact same problem. Is there a possibility you could help >> us out as well? >> >> On Feb 10, 12:51 pm, Matt Sanford <m...@twitter.com> wrote: >> > Hi Elso, >> > >> > I replied to your direct email and we can discuss in that thread. >> > We'll do what we can to help out. >> > >> > Thanks; >> > — Matt Sanford >> > >> > On Feb 10, 2009, at 10:12 AM, Eiso wrote: >> > >> > >> > >> > > Hi Alex and the rest of the Twitter Support Team, >> > >> > > By now you might have seen the stream of tweets, messages and >> > > everything in my power to try and get a hold of you. We launched our >> > > startup today, Twollars.com - which is a virtual thank you currency >> > > for Twitter with as goal to support charities and encourage good >> > > behavior. Not realizing that there were API limits on the search and >> > > public user/show/usernameorid.json - we launched, had one bad loop and >> > > twollars.com got blocked, understandably. We then switched over >> > > everything to omniwiki.co.uk (proxy wise) but quickly ran into the >> 100 >> > > requests per hour rate limit; and believe we might be blocked now? As >> > > you can understand we're sweating here and stress levels building, no >> > > startup wants to go south on the day of launch ;) >> > >> > > Is it possible you can whitelist omniwiki.co.uk and twollars.com - >> > > we'd also be happy to discuss a paid api structure if Twitter prefers >> > > that. >> > >> > > All the best, >> > >> > > Eiso >> > >