Complete the WebSocket implementation for full item tracking

Including online/offline status updates. This will reduce the spam load. You will no longer have to check every second to see if all the items you need are still available. Currently, the WebSocket displays actions (price changes and new listings), but does not display items that have “woken up.” If a user lists an item, it will be visible, but if they go offline and then come back, no actions will be displayed. On the one hand, the price hasn’t changed, but it’s impossible to get up-to-date information.

You’ve set a 429 limit on overly frequent requests. Why? To protect against DDoS attacks? Well, fine—you’ve charged me N amount, so now I have 5k accounts that can make requests independently of one another…

Also, let’s say I need to get the maximum bid for the Nth item. I can make the request 3–4 different ways using different API versions and get different results. Somewhere in the site’s response, there’s clearly an offer for 10 rubles—it’s visible in the list—but the `bestoffer` parameter only sees the second or third item in the list. In some cases, the site’s response to a price change takes 40–50 seconds after the change actually occurs.

Because of all this, I have to manually check each item card individually using verified methods. The load on the server from these requests increases exponentially. What should take just a couple hundred lines ends up taking tens of thousands. The bot is already starting to resemble a large-scale project, and if there are a dozen of these, the site will be in serious trouble.