excursion22@piefed.ca to Privacy@lemmy.mlEnglish · 5 days agoKagi Blog - Education Shouldn't Be Held for Ransomblog.kagi.comexternal-linkmessage-square19linkfedilinkarrow-up11arrow-down10file-textcross-posted to: [email protected][email protected]
arrow-up11arrow-down1external-linkKagi Blog - Education Shouldn't Be Held for Ransomblog.kagi.comexcursion22@piefed.ca to Privacy@lemmy.mlEnglish · 5 days agomessage-square19linkfedilinkfile-textcross-posted to: [email protected][email protected]
minus-squareFiery@lemmy.dbzer0.comlinkfedilinkarrow-up0·4 days agoThat is factually incorrect. Help page from Kagi (I’d understand if you don’t trust it), fit for non-techie consumption. https://help.kagi.com/kagi/privacy/how-does-privacy-pass-work.html So here’s the RFC, which defined the protocol in the first place (Kagi didn’t invent it, just implements it) https://www.rfc-editor.org/info/rfc9576/ As such they have absolutely no way of ‘deciding’ to look up a searchers account based on the token used. That ofcourse does not reduce other ways anyone can track you like fingerprinting.
That is factually incorrect.
Help page from Kagi (I’d understand if you don’t trust it), fit for non-techie consumption. https://help.kagi.com/kagi/privacy/how-does-privacy-pass-work.html
So here’s the RFC, which defined the protocol in the first place (Kagi didn’t invent it, just implements it) https://www.rfc-editor.org/info/rfc9576/
As such they have absolutely no way of ‘deciding’ to look up a searchers account based on the token used.
That ofcourse does not reduce other ways anyone can track you like fingerprinting.