[cuu508]

My SaaS is sending monitoring notifications using signal-cli, and I regularly run into rate limits (enforced by Signal servers, not signal-cli), especially when sending to new numbers/usernames.

To the author--do you have any plans on how to work around that?

[stavros]

I guess they've hit the limit, because the bot isn't responding for me.

[inetknght]

Why should the author work around Signal's rate limiting? Are you asking the author to enable spamming?

[DaSHacka]

GP is presumably asking what their plans are once the service gets popular, runs into the ratelinit, and cannot send any notifications at all (or with significant delays) to the clients.

[gwillem]

Messaging is internally rate limited and capped per recipient. And it uses a sender pool.

[cuu508]

I use per-recipient internal rate limiting too, that alone is not enough, especially for new numbers. I'm not using a sender pool though.