Even that would fit in the meaning of the art! (Which is easy, as there is no meaning to it by design)
For anyone wanting to give it a shot: https://github.com/p-e-w/heretic This is for locally running LLMs which often have baked in censoring (during training)
Hence AGPL exists, closing that loophole.
Just tell the clanker to use modern practices poof fixed.
Jokes aside a lot of that bad code can be detected by static linting tools and gated on, making it impossible for any of those to reach main.
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.
You seem to be misinformed. Kagi’s privacy pass cryptographically proves that you’re allowed to search, without having anything link back to your account. It doesn’t get more anonymous than that.
0 points on What was the silliest issue you discovered during debugging? in !programmer_humor@programming.dev ·
The good news is that with JavaScript now having adopted Temporal in the standards all of that should be in the past as soon as apps switch to it. (And when Apple decides to implement the damn thing)