From 8cee36a4e8fb973489be6f0981bdc8ebe9d1466f Mon Sep 17 00:00:00 2001 From: fria <138676274+friadev@users.noreply.github.com> Date: Sun, 16 Mar 2025 15:12:27 -0500 Subject: [PATCH] add problem section --- blog/posts/privacy-pass.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/blog/posts/privacy-pass.md b/blog/posts/privacy-pass.md index 5d5fc73b..3ae65e5a 100644 --- a/blog/posts/privacy-pass.md +++ b/blog/posts/privacy-pass.md @@ -14,4 +14,11 @@ description: | --- # Privacy Pass: The New Protocol for Private Authentication -Services that require authentication can correlate your activity on that service with your account, and that account is normally linked with payment information that could potential link back to your real identity. With the privacy pass protocol, it doesn't have to be that way. \ No newline at end of file +Services that require authentication can correlate your activity on that service with your account, and that account is normally linked with payment information that could potential link back to your real identity. With the privacy pass protocol, it doesn't have to be that way. + +## The Problem + +Services that don't require an account or payment to use are great; you can use them with Tor, clear your browser history, whatever you need to do to keep your activity private. + +But logging into an account completely invalidates all of that. As long as you're logged into an account with a service, all your previous and current activity can be linked together, along with any data you provided such as an email address, payment information, etc. +