Re: [twitter-dev] status destroy / caching in NewTwitter.

2010-10-19 Thread Pradeep Senanayake 
HI, Tom,

What I just want to know is, how to get access tokens dynamically, using
https://api.twitter.com/oauth/request_token
url. I went through the documentation but I cant understand. Pls give me a
clue.

Thanks in advance.
Pradeep.

On Wed, Oct 6, 2010 at 12:42 AM, Tom Monaghan  wrote:

> Hi folks,
>
> Can someone please share the caching expiration plan for newtwitter?
> It seems to cache new content for a really, really long time (at least
> 12 hours, though I think this number is falling).
>
> A few of our apps will regularly destroy some of their past tweets.
> Users with oldtwitter will not see said tweet if they haven't had it
> in their stream, and if it is in their stream, will lose it in their
> first refresh or authentication cycle.  This is our expected behavior.
>
> Users with newtwitter will see those tweets, even after they have been
> destroyed.  Even if they didn't have an active session during the time
> of their creation / destruction.
>
> You can manually flush your home timeline's cache by leaving the
> preview to return to oldtwitter.  If you then go back to newtwitter,
> they stay gone.  Signing out / signing back in to newtwitter and
> destroyed tweets are still there.
>
> What are the new caching expiration values?  Are there plans to
> decrease them?  Is there a goal min/max that we can expect?  Is what
> I've described expected behavior?
>
> Any help would be appreciated.
>
> Thanks much,
> Tom
>
> --
> 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

Re: [twitter-dev] status destroy / caching in NewTwitter.

2010-10-13 Thread CWorster 
Hi Tom,

very nice find. Manually switching between old- and newtwitter will
flush the ''statuses/home_timeline'' API-Endpoint. Hope this issue
will get some attention from Twitter-Devs.

-- 
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-dev] status destroy / caching in NewTwitter.

2010-10-05 Thread Tom Monaghan 
Hi folks,

Can someone please share the caching expiration plan for newtwitter?
It seems to cache new content for a really, really long time (at least
12 hours, though I think this number is falling).

A few of our apps will regularly destroy some of their past tweets.
Users with oldtwitter will not see said tweet if they haven't had it
in their stream, and if it is in their stream, will lose it in their
first refresh or authentication cycle.  This is our expected behavior.

Users with newtwitter will see those tweets, even after they have been
destroyed.  Even if they didn't have an active session during the time
of their creation / destruction.

You can manually flush your home timeline's cache by leaving the
preview to return to oldtwitter.  If you then go back to newtwitter,
they stay gone.  Signing out / signing back in to newtwitter and
destroyed tweets are still there.

What are the new caching expiration values?  Are there plans to
decrease them?  Is there a goal min/max that we can expect?  Is what
I've described expected behavior?

Any help would be appreciated.

Thanks much,
Tom

-- 
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