fix the missing blue checks in timelines, in profile and in tweet detail #686
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…etDetail request.
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the response of the timeline request, the users under globalObjects have a property ext_is_blue_verified that tells if they have a blue check or not. (In that response, the verified property of the users seems to always be false, so not useful).
In the response of the profile request, under result there is a is_blue_verified property that tells if the user has a blue check or not. (In that response, the verified property under legacy also seems to always be false, so not useful).
In the response of the graphql TweetDetail request, under result there is a is_blue_verified property that tells if the user has a blue check or not. (In that response, the verified property under legacy also seems to always be false, so not useful).