Maximum number of subscriptions?

[Florian Curinga]

Hi,

For transparency, I have created this question originally as issue in GitHub because I did not realize this group existed. https://github.com/tinode/chat/issues/976

I was wondering how tinode would handle the case where a user would keep subscribing to many topics without ever leaving them.

I guess the size of "sub" in the "me" topic would become very large when queried, which could cause problems on the client side? Or is it somehow capped (such as the eldest subscriptions will be removed)?

I am wondering how to handle this corner case so at least the client does not crash.

[Gene]

The maximum number of subscriptions is controlled by the following parameters:

https://github.com/tinode/chat/blob/b6b89594094cc871804f71389b511309bcb993d9/server/tinode.conf#L46C3-L46C23

"max_subscriber_count": 128,

Once this limit is reached, new subscription requests will be rejected (does not affect channel readers).

"max_results": 1024,

https://github.com/tinode/chat/blob/b6b89594094cc871804f71389b511309bcb993d9/server/tinode.conf#L248C21-L248C22

If this limit is reached, the number of subscriptions read from the database in some cases will be truncated at this count.

"max_message_size": 131072,

https://github.com/tinode/chat/blob/b6b89594094cc871804f71389b511309bcb993d9/server/tinode.conf#L43
If the response contains so many subscriptions that its size in bytes exceeds this limit, then the client-server connection will be dropped.

On Tuesday, October 14, 2025 at 4:03:42 PM UTC+3 Florian Curinga wrote:

Hi,

For transparency, I have created this question originally as issue in GitHub because I did not realize this group existed. https://github.com/tinode/chat/issues/976

The github issue template states the following on top of the form in a very large bold font: 

If you are not reporting a bug (requesting a feature), please post to https://groups.google.com/d/forum/tinode instead.

It's kind of hard to miss.

[Florian Curinga]

Hi,

Thanks for your answer, and sorry for posting in the wrong place originally.