Hello. Because the OAuth flow of twitter.com cannot be used from the Web based client for the Japanese mobile phone that we are providing, XAuth is used. (I get permission in your support.)
The following problems occur if it accesses the OAuth flow from the cellular phone of a major career of Japan now. - NTT DoCoMo , Softbank 1.The over memory error happens frequently because the size of HTML and the image is large. 2.The alarm display concerning SSL goes out whenever the page is switched. - KDDI 403 errors occur on the way, and OAuth flow fails. Moreover, because JavaScript cannot be used with a lot of models, the user is confused. Because we cannot provide the DM function from the cellular phone to the user who uses it, an existing user is inconvenient the state as it is it. (The user of the Japanese mobile phone has a lot of people who do not have PC. ) Because it is thought that there is a development expert of the Japanese mobile phone of Japan in your company, Could you add the OAuth flow that can be used from web browser of the cellular phone of Japan by 6/14? -- Shinichi Fujikawa President & CTO Mindscope,Inc. http://www.mindscope.co.jp <http://www.mindscope.co.jp> movatwi http://www.movatwi.jp (Japanese mobile based Twitter app, Winner of OPEN WEB AWARDS 2009 “Best Mobile Based Twitter App”) -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
