While looking at localStorage in the browser, I noticed that when I connect with @anywhere various details are written to localStorage for my page including
twitter_anywhere_cache_["account/verify_credentials",[]]_expiry: 1307546741323 twttr_anywhere_expiry: 1307552140184 which if interpreted as javascript Dates correspond to 30 minutes and 2 hours (respectively) after my connect time - that is 1800 * 000 and 7200 * 1000 ms. I haven't tried playing with them, but remembering that @anywhere is still largely experimental and undocumented, those keys might give you some thing to look for in the code and see if you can spot anything that looks like a valid way to tweak them. . -- 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
