Added Support for Twitter API V2 and Decoupled Reverse Geocoding Service #21
Conversation
This file contains 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
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.
This pull request is in response to the recent changes in Twitter's API policies. As a result, we have updated our application to make use of Twitter's V2 API endpoint, which is now required. In addition, Twitter's V1.1 API no longer supports reverse geocoding in its free tier. Consequently, I've made modifications to ensure continuity of the aerialbot functionality while also maintaining location accuracy.
Here is a summary of the key changes in this pull request:
These changes aim to maintain the functionality of aerialbot on Twitter while adhering to the platform's updated API policies. Feedback and reviews are appreciated!