Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Strip timelines up to a max_length #122

Open
dialelo opened this Issue · 3 comments

3 participants

@dialelo
Owner

For saving memory. Make it configurable with a sane default (e.g. 100).

@joedicastro

It's a good idea, but it can slow the navigation if requires more requests to twitter when you're searching a particular previous twitter down the list, isn't it? Maybe, you could use a file as a cache for tweets already received (e.g. 300)... I don't know, what you think?

@dialelo
Owner

... it can slow the navigation if requires more requests to twitter when you're searching a particular previous twitter down the list, isn't it?

Actually I should have thought about what happens when you scroll down and you already have the maximum amount of statuses for the timeline. If we limit the number of statuses that can be in a timeline we could hit the limit and not get older statuses displayed. That would ruin the user experience.

I think it's better to do a "cleanup" once in a while instead of limiting the status amount.

Maybe, you could use a file as a cache for tweets already received (e.g. 300)

Sounds good. I have yet to investigate the caching options of tweepy because we might get it for free from the library.

The motivation behind this is to be able to leave turses running for long periods of time without bloating memory.

@z411

I think it's a good idea, I've left turses running for some hours and it starts running very very slowly, and I have to restart it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.