we telegram users are encouraged to collect interesting supergroups and channels we come across, because there's no easy way to find them later if don't join or after we leave (especially private groups/channels).
This causes many users to reach the 500 : Too Many Communities limit and leads to massive loads on telegram's servers, as the servers need to process and send messages updates from all 500 cloud superchats to their respective members.
Proposed solution :
Step 1 : discourage users from joining too many chats :
instead of joining those groups and channel, telegram should give the option to bookmark them. Bookmarked groups and channels will appear in a dedicated list, can be found easily by search, but don't generate a message preview that constantly updates in the chatlists. This reduces the load on telegram's servers and cleans up everyone's chatlists.
Step 2 : offer a compromise for users who already reached the 500 limit :
For instance, by making archived chats behave like archived stickers. Unfortunately it is too late to change archived chats feature, since users are already accustomed to the existing behaviour, but a new feature can be introduced like "frozen chats" or "sleeping chats" .
Once a user reaches the 500 limit, they will be asked to freeze some superchats in order to make room for the new ones, similar to what happens with stickers.
Dear Telegram Support When I want to join a channel or group , I face the limit of too many channels and groups. Please remove this restriction for my account Best regards.
I
Ivan Sholohov
In the notification management section, I would show whether a chat is synced or not (if "no sync", display an "Enable sync" button; if "synced", show a "Disable sync" button). If the app's codebase determines which chats receive updates and notifications based on a subscription list, I would introduce a "sleeping" entity and move all chats with disabled sync into this "sleeping" state. I'd add a separate counter for all resources that distinguishes between "active" and "sleeping" subscribers. We could keep the total public counter unchanged, but show admins the breakdown in parentheses (e.g., how many are "active" vs "sleeping") for analytics purposes. I would add a setting called "Disable sync after..." where users could set the number of days without reading after which a chat automatically becomes "sleeping" (default: 6 months - assuming read status is tracked and can be used for this purpose). For desktop and web versions, I'd add "Share" buttons for all entities: channels, groups, bots, etc. In settings, I'd include a checkbox to "Automatically subscribe to resources when sharing links", even when sharing to "Saved Messages", along with configuration for default subscription status - for example, allowing users to set subscriptions as "sync disabled + notifications muted" by default. In the context menu for "Delete chat", I'd add an additional option between "Cancel" and "Delete" called "Disable sync". In app settings, I'd add a "Hide sleeping resources" checkbox (those without active sync). For subscribed but sleeping resources (no sync), we would simply display a "Zzz" icon (or bookmark, or any other indicator) in the same place where we show verification badges for official channels when they appear in search results. This is particularly useful when users want to keep channels in this state while still being able to distinguish them from similarly named channels when returning later or sharing with colleagues/contacts.
When I want to join a channel or group , I face the limit of too many channels and groups. Please remove this restriction for my account
Best regards.
If the app's codebase determines which chats receive updates and notifications based on a subscription list, I would introduce a "sleeping" entity and move all chats with disabled sync into this "sleeping" state. I'd add a separate counter for all resources that distinguishes between "active" and "sleeping" subscribers. We could keep the total public counter unchanged, but show admins the breakdown in parentheses (e.g., how many are "active" vs "sleeping") for analytics purposes.
I would add a setting called "Disable sync after..." where users could set the number of days without reading after which a chat automatically becomes "sleeping" (default: 6 months - assuming read status is tracked and can be used for this purpose).
For desktop and web versions, I'd add "Share" buttons for all entities: channels, groups, bots, etc.
In settings, I'd include a checkbox to "Automatically subscribe to resources when sharing links", even when sharing to "Saved Messages", along with configuration for default subscription status - for example, allowing users to set subscriptions as "sync disabled + notifications muted" by default.
In the context menu for "Delete chat", I'd add an additional option between "Cancel" and "Delete" called "Disable sync".
In app settings, I'd add a "Hide sleeping resources" checkbox (those without active sync). For subscribed but sleeping resources (no sync), we would simply display a "Zzz" icon (or bookmark, or any other indicator) in the same place where we show verification badges for official channels when they appear in search results. This is particularly useful when users want to keep channels in this state while still being able to distinguish them from similarly named channels when returning later or sharing with colleagues/contacts.