Closed Ulysses0817 closed 1 year ago
+1 when the script that hold the API need to be restarted , a brand new conversation id is created everytime, and there is now no way to return in the contexte of the previous conversation before the restart
After logging into the chat page, maybe it's feasible to using requests.post() with cookies taken from selenium? I'm a little confused why didnt you implement it, hhhh. If so, I think that we must consider the ssl client fingerprint or any other cases?
That's what I did in earlier version. But TLS fingerprint is so troublesome that it does not work consistently. Therefore, I have no way but to abandon this method.
+1 when the script that hold the API need to be restarted , a brand new conversation id is created everytime, and there is now no way to return in the contexte of the previous conversation before the restart
After logging into the chat page, maybe it's feasible to using requests.post() with cookies taken from selenium? I'm a little confused why didnt you implement it, hhhh. If so, I think that we must consider the ssl client fingerprint or any other cases?