While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

About custom filters, the Wiki says that the filter method accepts a Message instance, but in the source code it accepts only an Update instance.

What is right? Should

On a weekly basis, customer report issues around the 15 second timeout. This problem manifests as Exceptions and looks like a timeout.

We need to offer a more robust guidenance around Async / Long-Running operations. This guidenance likley takes the form of:

1. Your bot responds very quickly.
2. Do Needed Processing()
3. Send the result to the user as a Async / Proactive message.

There

What prevents a bot from receiving the 'reply_to_message' section in a message?

My bot uses the username of the user from the original message that was responded to, but this section from the message is missing for this in some telegram groups.

user1: hi
user2: (reply to user1's message) /welcome Have a look here: xxx

nodejs console.log(msg):

Message structure in a working group:

When trying to find the options that can be used to initialize NLP.js, I have to delve into the code and navigate through many files to find what I am looking for, if I am lucky. Also the structure of the settings are hard to figure out and require a lot of trial and error.

For example, we are using the NlpManager with these:

{
    ner: { builtins: [] },
    autoSave: false,
    langua

Context

• Telegraf.js Version: 3.37
• Node.js Version: 13.13
• Operating System: Ubuntu 19.10

Expected Behavior

In the Telegraf documentation in Doc says that the extra parameter can be whatever that official telegram doc has said! So I can be able to send something to bot:

ctx.replyWithAudio(downloadLink, {
        title: mytitle,

Description

While hubot-slack has support for reconnecting when the connection to Slack is lost, there is a limit to the number of reconnection attempts. If several reconnection attempts fail, the bot will simply hang without a connection. This causes trouble for our process manager, since the client staying open means we don't end up automatically restart it. When this has happened for us