From 737cdea1a7aed138eadf3db8b8cb737a7dc7339e Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 24 Oct 2023 14:51:13 -0400 Subject: [PATCH] Fix grammar in OHTTP section. Co-authored-by: Ted Thibodeau Jr --- index.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index b9d50b806..c37bfda10 100644 --- a/index.html +++ b/index.html @@ -4408,13 +4408,13 @@

Device Tracking and Fingerprinting

-One mechanism that implementers might consider utilizing when fetching external -resources that are associated with a verifiable credential or a -verifiable presentation is the Oblivious HTTP protocol [[?OHTTP]]. +The Oblivious HTTP protocol [[?OHTTP]] is one mechanism that implementers might +consider using when fetching external resources that are associated with a +verifiable credential or a verifiable presentation. Oblivious HTTP allows a client to make multiple requests to an origin server -without that server being able to link those requests to the client or to -identify the requests as having come from the same client, while placing only -limited trust in the nodes used to forward the messages. Using Oblivious HTTP +without that server being able to link those requests to that client or even to +identify those requests as having come from a single client, while placing only +limited trust in the nodes used to forward the messages. Hence, Oblivious HTTP is one privacy-preserving mechanism that can be used to reduce the possibility of device tracking and fingerprinting.