tweet_mode='extended' is undocumented on API.user_timeline but works
See original GitHub issueAPI.user_timeline does not state that tweet_mode
is a valid parameter, but when I used it (tweet_mode=extended
), it returned the tweets with the full_text
attribute.
It works perfectly, it’s just undocumented.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Does tweet_mode=extended work with the Twitter statuses ...
Yes, you can use tweet_mode with the statuses/user_timeline API. ... In short, if a tweet is a retweet, the extended tweet must be...
Read more >Sometimes, the hashtags node is empty in statuses/user_timeline ...
I read the hashtag node in the statuses/user_timeline.json api call to achieve this. ... Have you set the tweet_mode=extended parameter on your API...
Read more >[Fixed]-How do you get the "images" from a twitter feed to show in an ...
With tweet_mode set to extended ( tweet_mode is an undocumented parameter), it will now return the media as part of the response.. This...
Read more >twitter.api — python-twitter 3.4.2 documentation
2016) extended tweet mode. See docs for details. Choices are ['compatibility', 'extended']. proxies (dict, optional): A dictionary of proxies for the ...
Read more >python-twitter Documentation - Read the Docs
In order to use the python-twitter API client, you first need to acquire a ... that you have pyenv installed and working on...
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
Thanks, that solved my issue of truncated text fields with
tweet_mode='extended'
This does not appear to work as of June 2021 - running it on
user_timeline
returns truncated texts every time. Should it not? Currently on version 3.10.0.