This repository was archived by the owner on Sep 18, 2023. It is now read-only.
This repository was archived by the owner on Sep 18, 2023. It is now read-only.
Description
After going through more than 10 poe accounts in my tests, I found that the banning of poe accounts is related to at least the following behaviors（The following tests were performed using the latest version of poe-api and a proxy server.）:
- Sending a new request before the bot has finished replying. This will result in a ban if it happens a few times, as mentioned by @SuperLiveYou in other issues.
- The interval between requests is too short. I recommend a 9-15 second interval between requests; otherwise, there is a high probability of being banned after 15 requests.
- The interval between clearing chat history and sending a message to the bot is too short. Surprisingly, this has a high probability of getting banned, even higher than frequent requests. I suggest taking a 30-second break after clearing the chat history.
- I noticed that when using the web version of POE normally, a forced page refresh occurs after a large number of conversations. After avoiding the three behaviors that may cause a ban mentioned above, a situation arises where after 30-35 requests to POE's API, the API is successfully requested but there is no response. (On the web page, it shows that the message was successfully sent, but there is no response from the bot's side. At this time, there is no problem using the web version for conversation.) Continuing to request the API under these circumstances will result in multiple requests with only one or two successful responses, and further requests will lead to a ban. To avoid this situation, I automatically disconnect and reconnect the WebSocket after every 9-15 API requests, then clear the current bot's history after a 30-second interval. This effectively avoids the situation where there are multiple requests but only one or two responses.
- Even if the above four situations are avoided, a ban will still occur after more than 40 consecutive requests (in my tests, this happened at 43, 45, and around 60 requests). I am not sure of the reason for this ban.
- By the way, I found that when using this project for frequent requests, there is a small probability of successfully responding to the API but the web version shows no response (similar to situation 4 mentioned above, but with a response in the API and only successful sending in the web version with no content on the bot's side). This situation usually occurs when the bot's reply content is minimal, and of course, encountering this situation means that a ban is not far off.
At present, the reason for the 5th type of ban is unclear. After avoiding bans from situations 1-4, it is best not to make more than 40 frequent requests within a short period (I encountered this situation within 10 minutes).