Skip to content
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.

Sign up for GitHub

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

Change "herd immunity" to "herd privacy" #541

Merged
merged 1 commit into from
Jan 20, 2021
Merged

Change "herd immunity" to "herd privacy" #541

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5060,13 +5060,13 @@ <h2>
a single service endpoint. In some cases, the publication mechanism might
reference a DID Document with no service endpoints at all. For the second
category, prefer using only one service that points to an authorization server,
mediator, or proxy that can provide herd immunity. For the third category,
mediator, or proxy that can provide herd privacy. For the third category,
avoid the use of multiple service endpoints for a DID because some
of these (e.g., an authorization server) are likely to be reused with other,
related DIDs. Place correlatable service endpoints behind a
privacy-preserving mechanism, if possible, or introduce a mediator or proxy
as a sole service endpoint in order to obscure related devices and documents
through herd immunity.
through herd privacy.
</p>
</section>
</section>
Expand Down