Csepp 🌢<p>Interesting <a href="https://merveilles.town/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> thing I stumbled upon: the <a href="https://merveilles.town/tags/RFC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RFC</span></a> for <a href="https://merveilles.town/tags/PrivacyPass" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PrivacyPass</span></a>.<br><a href="https://www.rfc-editor.org/rfc/rfc9576.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">rfc-editor.org/rfc/rfc9576.htm</span><span class="invisible">l</span></a><br>"Privacy Pass is an architecture for authorization based on <a href="https://merveilles.town/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a>-preserving authentication mechanisms. In other words, relying parties authenticate Clients in a privacy-preserving way, i.e., without learning any unique, per-Client information through the authentication protocol, and then make authorization decisions on the basis of that authentication succeeding or failing. Possible authorization decisions might be to provide Clients with read access to a particular resource or write access to a particular resource."</p>