|
|
|
|
|
by t-writescode
162 days ago
|
|
Using the example doc you’re citing from kagi.com - though not the RFC, I don’t have the time to dive into that one at the second, I see that a session token plus some other stuff is passed in and a token comes out. Where does it show that on the Kagi backend they couldn’t, theoretically, save the session key before performing the token response? |
|
If you're not going to make an effort to understand how it works, don't make assertions about how it works. Ask your favorite LLM about the RFC if you have any further questions.