Remove access_token
from gist loading.
#8614
Merged
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.
GitHub has deprecated use of
access_token
in query parameters and is email spamming us nonstop about it. (dozens of emails a day)Gists can be read anonymously with a rate-limit of 60 requests per hour per client IP address.
Since we stopped using gists for Sandcastle example code two years ago, the gist codepath is only for extremely old examples, so the rate limit is unlikely to be an issue in practice.
Also someone with the credentials for @Cesium-Sandcastle needs to revoke the old access_token and stop the endless deluge of emails. Also note that account is still using an agi.com email address.
Fixes #8593