Revise Tile Usage Policy #119
Merged
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
- Remove prior permission requirement. Our experience has been that no one can evaluate if their usage is heavy, and we have had no issues in the last few years from any apps unless they are scraping, which is prohibited later. - Recommend a contact email on the web page, so we can contact users instead of immediately moving to a block. - Explicitly define the correct URL. - Update parallel download requirements to reflect modern HTTP/2 and HTTP/3 multiplexing which allows far more than 2 parallel over 1 connection. This was only ever an issue when scraping. - Define and prohibit bulk downloading. The tile service is designed for interactive viewing, not downloading to view later. - Disclaim any sort of SLA, as sometimes people ask what it is. - Recommend against setting up a cache in front of the tile service. These are generally more trouble than they are worth these days, and they do not significantly help back-end load as the user's cache and Fastly will have similar coverage.
tomhughes
approved these changes
Jan 22, 2024
Firefishy
approved these changes
Jan 22, 2024
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.
Remove prior permission requirement. Our experience has been that no one can evaluate if their usage is heavy, and we have had no issues in the last few years from any apps unless they are scraping, which is prohibited later.
Recommend a contact email on the web page, so we can contact users instead of immediately moving to a block.
Explicitly define the correct URL.
Update parallel download requirements to reflect modern HTTP/2 and HTTP/3 multiplexing which allows far more than 2 parallel over 1 connection. This was only ever an issue when scraping.
Define and prohibit bulk downloading. The tile service is designed for interactive viewing, not downloading to view later.
Disclaim any sort of SLA, as sometimes people ask what it is.
Recommend against setting up a cache in front of the tile service. These are generally more trouble than they are worth these days, and they do not significantly help back-end load as the user's cache and Fastly will have similar coverage.