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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add centralization-is-bad section #95
add centralization-is-bad section #95
Changes from 1 commit
4a84e36
9855bae
35aa295
8f52710
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The DNS is hosted by a 'small number of "trusted parties"'. Are you suggesting that the Web shouldn't use it?
There are only three browser engines; does that represent a 'small number of "trusted parties"'?
Does this mean that Google Safe Browsing is centralized?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, i dont intend or think DNS would be covered by this wording. I can stand up a DNS server at home and it'll work just as well. But it would be very bad for a web standard to say "step 3: talk to Google, CF or Comcast's DNS servers".
No I didn't intend browser engines to be covered here. I'm happy to revise the text to make that clearer. A browser engine isn't a trusted party, its auditable (or at least an implementation could be auditable, even if not all are). But, it would be bad if a standard was written to require talking to software or a service that was designed to be unauditable ( widevine…), for example.
Google safe browsing is absolutely centralized. I think it'd be very bad to have a W3C standard that required talking to Google Safe Browsing servers to work correctly. Its a useful and valuable system, and I'm glad it exists, but it doesn't seem like a good model for building open standards for the Web.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re DNS, @mnot I realize I might have misunderstood your comment. Were you referring to root servers, or resolvers? My comment was about the latter, but on second thought I see you might have meant the former.
If you meant root servers, yea, thats a tricky one, I take your point. Its unappealing, but maybe its least bad. I could try and emphasize "unless necessary" or "unless no other alternatives exist" or similar (though i appreciate that direction has its own downsides too)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, I meant the root servers.