Page Caching Issues...

I would like to ask if you could tweak the page caching expiration times a bit in both the website and iphone app... the lifestream items are always out of date. I usually open the twitter site manually to see the latest tweets and responses.

Also if a person posts a new tweet, the cache should always expire. It is kind of weird if you post a message and the lifestream doesn't show it...

Thanks for the great service! Love it...

I’m thankful

Inappropriate?

Reply to this idea

1 person likes this idea

I like this idea! Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.

The best point from the company

Matt Galligan, Official Rep, replied on June 21, 2008 22:09
Thanks for the suggestions...and I'll explain how a few things happen:

1. The reason you're seeing out of date stuff isn't because of our cache expiration, but because we can't call the service enough. We're working on some ways to tweak how often we call Twitter, but when you're logged in we put you into a priority queue so that you're updating every 5 minutes or so. We're working on a way that we can do this without you needing to be logged in. One of the reasons that the iPhone is consistently more out of date than the desktop version is because when you log in with the iPhone we don't prioritize you just yet. This is a UI issue more than anything and will be fixed shortly.

2. We can't exactly do an auto-call whenever you post a tweet because it could provide lots of problems (with API call limits). What we can do is provide visual representation of what we know you posted. Granted, this is sort of a "faked" approach, but not really, because we know the post actually went up.

The company and 1 other person think this is one of the best points

Remove this from best good points

EMPLOYEE

Inappropriate?
Delete or Edit (for 15 minutes)

Matt Galligan, Official Rep, replied on June 21, 2008 22:09

Thanks for the suggestions...and I'll explain how a few things happen:

1. The reason you're seeing out of date stuff isn't because of our cache expiration, but because we can't call the service enough. We're working on some ways to tweak how often we call Twitter, but when you're logged in we put you into a priority queue so that you're updating every 5 minutes or so. We're working on a way that we can do this without you needing to be logged in. One of the reasons that the iPhone is consistently more out of date than the desktop version is because when you log in with the iPhone we don't prioritize you just yet. This is a UI issue more than anything and will be fixed shortly.

2. We can't exactly do an auto-call whenever you post a tweet because it could provide lots of problems (with API call limits). What we can do is provide visual representation of what we know you posted. Granted, this is sort of a "faked" approach, but not really, because we know the post actually went up.

The company and 1 other person think this is one of the best points

Add a comment This is one of the best points Mark as a company good point