Remove use cases where website interests conflict with user interests #8
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
|
An example of why we shouldn't help sites block crawling for prices: https://mastodon.gamedev.place/@badlogic/111071424197722223 |
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.
Product prices aren't sensitive from a user's point of view, and in fact several browsers are starting to include price comparison as a feature. The overall use case does seem solid in the public!=publicized sense, so I added a different example of public data that it can be harmful to allow scraping of.
Product catalogs also don't seem like a great example of IP that the web platform should work to protect, but I don't feel as strongly about that part of the change.