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

First image URL is repeated when multiple images embedded in tweet #1867

Open
notchia opened this issue Apr 21, 2022 · 2 comments
Open

First image URL is repeated when multiple images embedded in tweet #1867

notchia opened this issue Apr 21, 2022 · 2 comments
Labels
API This is regarding Twitter's API

Comments

@notchia
Copy link

notchia commented Apr 21, 2022

When images are embedded in a tweet, links to the images appear under the entities.urls field, in the format https://twitter.com/user/status/123456789/photo/[number] . However, when N>1 images are embedded as media, entities.urls contains only the url information for the first one (https://twitter.com/user/status/123456789/photo/1), but repeated N times.

The attachments field does list N unique media_keys, so it seems all of the images are at least being returned in some form.

@Harmon758
Copy link
Member

I'm able to reproduce this, but it seems like an issue with Twitter's API rather than with Tweepy, as Tweepy just provides the entities data from the Twitter API.

You should report this on the Twitter Developers Forums.

I've found two posts there about this:
https://twittercommunity.com/t/duplicate-url-entities/162482
https://twittercommunity.com/t/repetitive-urls-in-entities/159093
but neither has a response.

@Harmon758 Harmon758 added the API This is regarding Twitter's API label Apr 21, 2022
@notchia
Copy link
Author

notchia commented Apr 21, 2022

Thanks! Just responded to one of those original posts on the developer forums.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API This is regarding Twitter's API
Projects
None yet
Development

No branches or pull requests

2 participants