Favorited state in search is always false
See original GitHub issueI’ve been trying to use the status.favorited
variable of a status retrieved by api.search
but it was always false. When trying to favorite this tweet it gave me exceptions with a message that that tweet was already favorited. After some help from the discord, I’ve discovered that this is fault on the twitter API itself [1]. My suggestion is to internally cross reference with a user’s favorites to mitigate this.
As a developer, this was not a fun experience and I want to prevent this from happening to others.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Redux Error: TypeError: state.favorites.concat is not a function
Am I returning the data in a wrong format? I am new to redux and am following a tutorial so I am not...
Read more >Customize searching in Safari on Mac - Apple Support
Stop showing icons for your favorite websites below the Smart Search field. In the Safari app on your Mac, choose Safari > Settings,...
Read more >The Lumineers - Sleep On The Floor (Official Video) - YouTube
Check out the official music video for "Sleep On The Floor" by the LumineersCleopatra is the brand new album from The LumineersOrder on...
Read more >Optimize your site for search engines (for beginners)
Google doesn't accept payment to rank a website higher, or rank websites higher if they advertise on Google. If anyone tells you otherwise,...
Read more >Why Most Published Research Findings Are False - PMC - NCBI
The probability that a research claim is true may depend on study power and ... likely relationships or searches for only one or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please don’t necro-bump old closed issues.
@thekillgfx That is the same thread that is linked in this issue and that was added to the documentation with https://github.com/tweepy/tweepy/commit/1ab151956ec2874ae0f724ebf97d030f9ca9f5c8, the commit that closed this issue. The relevant Twitter API documentation you’re referencing was also added to Tweepy’s documentation in that commit.
As for Twitter API v2 support, see #1472.
@lg188 I’ve found a workaround for this. for each status, overwrite that status by the same status, but from a different endpoint.
status = api.get_status(status.id)