Telegram on iOS crashes when browsing stickers or gifs longer than 30 second
If you open the sticker/gif panel when entering a message, flip, twist, rotate, no matter how, but view them, 15-20 seconds - the application crashes. Steps to reproduce Entering a message; Click on the…
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.