Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Twitter] Expand conversations/threads in timeline and few improvements #2665

Open
nisehime opened this issue Jun 8, 2022 · 1 comment
Open

Comments

@nisehime
Copy link

nisehime commented Jun 8, 2022

Hello.

Twitter truncates long conversations in users timelines (by long I mean longer than 3 tweets), which causes missed tweets from /with_replies timeline and even in threads from normal timeline. In other words if a long thread/conversation appears on timeline, only first one and last two tweets from it would be downloaded. So these conversations should be expanded. For example, when there's a tweet which is a reply you open it directly and then download rest of the thread. Maybe there's another way to do it with twitter's web API.

Secondly, I asked you to improve the replies setting and add option to grab tweets where user id matches the id of target (from URL) user id. Currently, if you set it to self it doesn't download target's tweet where he replies to other user, and if you set it to true than it downloads tweets from non-target users which are probably unneeded in most cases. Actually, I think you can just make self to behave like this instead of doing 4rd option.
It would be nice if target's user id or better all their metadata will be always accessible in keyword dictionary for some filtering purposes.

After that you can improve the default algorithm

  1. Set the default replies option to self
  2. Use /with_replies timeline for regular user links (twitter.com/user) instead of /tweets when retweets=true
  3. text-tweets=true should also switch the timeline to /with_replies instead of media like retweets. This also needs to remove media filter from search.
@aleksusklim
Copy link

If there will be a reliable method to stop downloading older content, then there is no need in implicitly changing endpoints (which is bad, when the user knows better what he wants) in trying to guess "which is better".

One such method I explained in the bottom of #2624 (comment)
I still did not experiment further, but I will.

mikf added a commit that referenced this issue Jun 13, 2022
- use '/with_replies' when appropriate
- consider 'text-tweets'
- build search query as necessary
mikf added a commit that referenced this issue Jun 13, 2022
If a username is given in the input URL,
only download from replies by that user.
mikf added a commit that referenced this issue Jun 28, 2022
'user_tweets_and_replies' was a mistake
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants