Oh, one more tip for requesting xAuth access: * Check your Junk folder regularly for responses -- many developers in the past have found their responses from our ticketing system in their Spam folder.
@episod <http://twitter.com/episod> - Taylor Singletary On Wed, Apr 6, 2011 at 7:21 AM, Taylor Singletary < [email protected]> wrote: > We're usually much faster than this at answering xAuth requests.. a few > tips on making sure that your message gets received and is actionable: > > * Send the email to [email protected] from the same email address associated > with the account that "owns" the application > * Clearly state the purpose of the request in the subject line > * Include your consumer key and/or application ID in the message > * Clearly describe what your application does, how Twitter is used in the > application, and information about your users. > * Include the platforms that your application will be used on. > * Include a link to your privacy policy and company (if you have one) > * Include links to screenshots of your application (don't attach them to > the message) > > @episod <http://twitter.com/episod> - Taylor Singletary > > > > On Wed, Apr 6, 2011 at 2:48 AM, henning0700 <[email protected]> wrote: > >> Hi all, >> >> What are your experiences in requesting xAuth access? >> >> The first time I requested access was nearly three weeks ago. I then >> sent another request last week and still no response. Yep...nothing, >> nada, zip, zero, zilch... >> >> Thanks. >> >> Henning >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
