search

CRMTH / RITHM

MIT License
2 stars 4 forks source link

Changes to user data in Twitter API #14

Open colditzjb opened 5 years ago

colditzjb commented 5 years ago

Per the below announcement, the user object data may look different as soon as May 20th:

The following fields should no longer be relied on by developers when making use of the user object, including when returned as part of a Tweet. Starting on May 20, 2019, all of the following fields will no longer be supported. Developers should expect them to start returning null values.

https://twittercommunity.com/t/upcoming-changes-to-user-object-and-get-users-suggestions-endpoints/124732

This may require some changes to the parser, to ensure that data are being looked for in both the old and new fields (where applicable).

colditzjb commented 5 years ago

Specifically... we may want to check that the profile image URL and profile background image URL fields are up-to-date or are handled so that they don't crash the process. Many of the other changed fields do not impact our code base.

NOTE: profile_image_url_https will continue to be valid and populated for user profile images aka "avatar images." HTTPS URLs are the only formats that Twitter will support in internal data objects in the future, and you should update your apps and code appropriately.