Conversation

Notices

1. Embed this notice
   feld (feld@friedcheese.us)'s status on Friday, 14-Feb-2025 05:26:52 JST feld
   This is pretty wild
   
   https://blog.kagi.com/kagi-privacy-pass
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 14-Feb-2025 05:38:52 JST feld

     in reply to

     • barrett
     @barrett so somehow you can request tokens which authenticates you. Each token can only be used once.
     
     But somehow the server doesn't know who the tokens were generated for, only that they're valid. And you use a unique token for each request. But the tokens can't even be linked to the same user by any method either.
     
     The tokens can't be forged. I don't understand how this works yet. Super weird.
   • Embed this notice
     barrett (barrett@shitposter.world)'s status on Friday, 14-Feb-2025 05:38:53 JST barrett

     in reply to
     @feld i'm not sure whats going on here, but it seems like this could be big
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 14-Feb-2025 05:40:08 JST feld

     in reply to

     • barrett
     @barrett how can the token only work once but not require the server to track a ridiculously huge database of tokens?