Technically, all TelegramBot frameworks for Smalltalk or Python or whatsoever are only clients. They use the Telegram Bot API which connects them to the actual server. This means that a part of the bot's state
is kept on the Telegram servers. Concretely, this is an event queue. If you make requests for the same bot from multiple clients (i.e., images with TelegramSmalltalkBot), these conflict which each other because they both pull updates from the same queue.
Usually, you can simply ignore this error by pressing Proceed. If it occurs again, you should make sure that no other client is running at the same time. For TelegramBot in Squeak, you can do so by opening the
process browser and searching for any telegram bot process. You can yellow-click them and choose terminate.
For testing, you can also manually inspect the latest updates for the bot by evaluating the following in your workspace:
bot peekUpdates explore.
If you have sent a message to the bot before, you should see a non-empty list.
>
I think perhaps I should try an older image 5.3 or early 6.0alpha, and not update it ? What do you think ?
No, TelegramBot/TelegramSmalltalkBot are explicitly designed to "live at head", older versions of Squeak Alpha are not supported. I can only tell that it works well for me with an up-to-date Trunk image for both Windows 2004 and Debian/Raspbian. If you
can provide a concrete stack trace, we should be able to solve the problem. :-)
Best,
Christoph