* === v0.4.1 (2010.09.02) === # BugFix: issue 49 . thanks Pro711 # Feature: username case insensitive.Need to re-certification from twitter.com # Feature: optimize procedures * === v0.4 (2010.07.02) === # 只支持 Oauth 方式的身份认证 # 可修改 secret key * === v0.3 (2010.03.01) === # 增加 is_hop_by_hop 函数 # 重写了从twitter抓取数据后返回给客户端的部分 * === v0.2.2 (2009.12.30) === # fixed 版本显示的错误 # 增加了对search.twitter.com和api.twitter.com的支持,如: # https://search.twitter.com => https://gtapserver1.appspot.com/search # https://api.twitter.com => https://gtapserver1.appspot.com/api * === v0.2.1 (2009.08.03) === # 在app.yaml中增加了参数secure,强制客户端用https连接 # 再一次修改了TwitterFox 1.8.3,现在API和所有在浏览器中打开的链接,均使用HTTPS * === v0.2 (2009.08.02) === # 修改了身份验证部分,可以更正常的代理API # 完全照模样返回Twitter API的响应 * === v0.1 (2009.08.01) === # 想法+简单实现,我自己可以凑活用了 # 可以代理几乎所有REST API(未完全测试) # OAuth没测试过,也没研究过,不知道能不能行。估计是不行 # 提供一个API测试地址 http://gtapserver1.appspot.com/ # 弄了一个使用上面这个测试地址的 TwitterFox 1.8.3修改版 you can change "main.py" to "main-private.py" in file app.yaml for private using. 1,you MUST set USER_PASSWORD in main-private.py for your gtap and DO NOT share it with anyone. 2,find these variables of your application from https://dev.twitter.com/apps/ and modify them in main-private.py CONSUMER_KEY = Consumer key CONSUMER_SECRET = Consumer secret ACCESS_TOKEN = Access token ACCESS_TOKEN_SECRET = Access token secret *if you can not find "Access token" and "Access token secret", click the "Create my access token" button. 3,now you can use gtap via USER_PASSWORD(and any username) without any oauth-authorization