Migrate remaining enpoints using v1.1 to v2

[robertoszek]

Twitter introduced a new tier of access (Elevated) to their API projects and although existing projects were promoted automatically, new users by default will get Essential access instead, which is not allowed to make requests to API v1.1.

Users can apply for Elevated access here, but it should not be a hard requirement.

We should move the little that's left of v1.1 to v2 and once fully migrated, remove the redundant twitter_base_url mapping from the config samples (and continue to use twitter_base_url_v2 internally, so we don't break old config.yml files created by users before these changes).

Endpoints which we still use v1.1 as of the time of writing:

• /users/show.json?screen_name={screen_name}
  • bio_text
  • profile_image_url_https
  • profile_banner_url
  • name
    • https://developer.twitter.com/en/docs/twitter-api/users/lookup/migrate/standard-to-twitter-api-v2
• /statuses/show.json?id={id}
  • extended_entities: media (video)
  • https://developer.twitter.com/en/docs/twitter-api/tweets/lookup/migrate/standard-to-twitter-api-v2

https://developer.twitter.com/en/docs/twitter-api/migrate/data-formats/standard-v1-1-to-v2

https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-level https://blog.twitter.com/developer/en_us/topics/tools/2021/build-whats-next-with-the-new-twitter-developer-platform

[robertoszek]

Welp, it seems video URLs are still not available on v2 as of yet: https://twittercommunity.com/t/how-to-get-video-from-media-key/152449/9

We'll migrate that part once it's ready.

[robertoszek]

Regarding the users endpoint:

• /users/show.json?screen_name={screen_name}

We can transition to /v2/users/by/username/{screen_name}" Where we can get the data we need:

• bio_text -> description
• profile_image_url_https -> profile_image_url
• name

However, the profile banner url is also missing on v2 at the moment: https://twitterdevfeedback.uservoice.com/forums/930250-twitter-api/suggestions/41506555-please-add-profile-banner-image

[robertoszek]

After e880169a96ed3d32f5f36a9d40939ae2ad648c59, this is the migration status. These are the endpoints which we still use v1.1:

• /users/show.json?screen_name={screen_name}
  • profile_banner_url
• /statuses/show.json?id={id}
  • extended_entities: media (video)

As of the time of writing there is no equivalent on v2 for obtaining this data, we'll move off them as soon as we can.

[robertoszek]

Included notice on the docs mentioning the Elevated access requirement for now Commit: d787f5e3a433f6412d6e211e2379b754b40970f2