Every time you send a post to 127.0.0.1:8000, Deepseek-API creates a new conversation and pastes the whole backlog of chat into it, over and over. This unnecessarily overloads Deepseek™'s resources, and creates a confusing list of conversations, where each conversation is only a single reply with the whole backlog uploaded again. It also quickly looks very SPAM-ish and unnecessarily triggers Deepseek™.
It would be nice if Deepseek-API develops the concept of session, where it submits posts in the same session to the same chat.deepseek.com conversation, without pasting the whole backlog again and again. Then, Deepseek can internally do its backlog compression and send to its models in ways it wants as per the chat.deepseek.com implementation.
Every time you send a post to
127.0.0.1:8000, Deepseek-API creates a new conversation and pastes the whole backlog of chat into it, over and over. This unnecessarily overloads Deepseek™'s resources, and creates a confusing list of conversations, where each conversation is only a single reply with the whole backlog uploaded again. It also quickly looks very SPAM-ish and unnecessarily triggers Deepseek™.It would be nice if Deepseek-API develops the concept of session, where it submits posts in the same session to the same
chat.deepseek.comconversation, without pasting the whole backlog again and again. Then, Deepseek can internally do its backlog compression and send to its models in ways it wants as per thechat.deepseek.comimplementation.