3 ms·
Add the ability to export your account config (yaml?) and use it with privacy pass. Maybe even sync it with git. To avoid fingerprinting by config, have a page
by dsp_person 2y ago
Add the ability to export your account config (yaml?) and use it with privacy pass. Maybe even sync it with git.
To avoid fingerprinting by config, have a page where the community can share and vote on best configs, then clone and use a popular one that suits your needs.
- CGamesPlay 2y agoThis defeats the purpose of Privacy Pass. Something similar is discussed in the post: https://blog.kagi.com/kagi-privacy-pass#:~:text=customization%20and%20personalization https://blog.kagi.com/kagi-privacy-pass#:~:text=customizatio...
- swores 2y agoTheir suggestion is that when using Privacy Pass you'd also send "&config=XX" where XX is an ID of a publicly shared config, so that you get the customisation of whatever config you choose without tying the config to yourself, just tying it to the searches you're doing with Privacy Pass. So while it does add a data point that could help track you, it's not defeating the whole point.
- tiltowait 2y agoThough the post doesn't touch on "community configs", it does touch on "the ten most popular configs", which would seem to be similar enough for this discussion.
- deleted 2y ago[deleted]