Skip to content

get_latest_timeline silently ignores valid "home-conversation" entries #336

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

Open
ruizie opened this issue Mar 25, 2025 · 0 comments · May be fixed by #337
Open

get_latest_timeline silently ignores valid "home-conversation" entries #336

ruizie opened this issue Mar 25, 2025 · 0 comments · May be fixed by #337

Comments

@ruizie
Copy link

ruizie commented Mar 25, 2025

Hello!

I will try to fix this and submit a PR, but to start talking about the issue, I'm documenting it here.

On Twitter, it looks like a thread with replies, I don't know how exactly they are posted, but maybe by some third party social media service, but it's a couple of tweets linked to each other as a "conversation". They appear on timeline, they indeed are a couple of tweets which are very much necessary returning as the output of get_latest_timeline because they can be seen on the site and are integral part of the feed. There is a line on the left of the tweets in the "Following" timeline view indicating that they are grouped together.

In the debugger, it looks like this:

Image

The entries that start with home-conversation are completely ignored and never returned by get_latest_timeline. When you look at the data, the tweets themselves are embedded in a single entry, multiple tweets per conversation, with all the data for each tweets embedded into it. I believe (and hope) they are formatted the same as other entries just part of that conversation element.

I wish to unpack those tweets and return them as well.

Thanks

ruizie pushed a commit to ruizie/twikit that referenced this issue Mar 25, 2025
ruizie pushed a commit to ruizie/twikit that referenced this issue Mar 25, 2025
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

Successfully merging a pull request may close this issue.

2 participants
@ruizie and others