tdesktop
tdesktop copied to clipboard
telegramdesktop
Messages pinned before a group's conversion to supergroup cannot be unpinned/dismissed
Steps to reproduce
- create a group
- send and pin some messages
- perform one of the actions that trigger the group's conversion to supergroup, such as changing the chat history visibility
- optionally send some messages and pin them
Expected behaviour
The messages sent and pinned before the conversion to supergroup are displayed in the pinned message forever, without the possibility to unpin or dismiss them. They stay there forever
Actual behaviour
I'm not sure about what should be the proper behavior when this happens. The android app (and also Telegram X) simply doesn't show pinned messages belonging to the chat history prior the conversion to supergroup. I guess this is the intended behavior
Alternatively, tdesktop could still show the "old" messages in the pinned messages list, but should provide an option to dismiss/unpin them (even if it's just for me). Right now, they stay there indefinitely, without the possibility to unpin them, which sometimes is annoying
Configuration
Operating system: any (pop!os, windows 10)
Version of Telegram Desktop: 2.7.5
Related card on the suggestions platform: https://bugs.telegram.org/c/711
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Just run into the same problem. I pinned a message, just after the creation of the group. Using the desktop app on windows 11 I cannot pin/unpin it and does not show as pinned on mobile devices. But stays there on desktop app.
Would love for this issue to be fixed because I created a new group just because I wanted a clean start and I epic failed 🤣
Heavy plus to this one. The issue is totally reproducable on desktop client. It seems that desktop app is using different approach when it loads pinned messaged from API.
Expected behavior: e.g. Android app is behaving in a more predictable way — it shows only messages that have been pinned after the conversion to a supergroup.
Configuration Operating system: whatever Version of Telegram Desktop: 3.7.3 (from Flatpak)
Checked some more stuff — this issue is most likely not cache-related:
- Settings -> Advanced -> Manage local storage -> Clear all — won't solve
- Logout, log back in — won't solve
- Delete entire app (
flatpak uninstall org.telegram.desktop), install again — won't solve
@ilya-fedin, would you mind taking a look?
Judging by other issues, you seem to be quite a good reviewer of what's worth fixing (:
Sorry if it caused any unnecessary disturbance
I really know only Linux-specific code in tdesktop and this issue is not related to such code as far as I can see. And, moreover, this issue sounds like a server-side limitation. Once group is converted to supergroup, old posts become read-only and apparently no one can't do anything with that.
Once group is converted to supergroup, old posts become read-only and apparently no one can't do anything with that.
Hah, nice.
I looked into Telegram/SourceFiles/dialogs/dialogs_pinned_list.cpp and it looks quite clean & straightforward about what it's doing. Maybe, mobile clients contain some sort of hacks (filters for read-only pinned messages?) to elliminate the described behavior.
Sad to realize that the problem tends to vanish among other issues. Could someone at least add a "bug" label to it?
Could someone at least add a "bug" label to it?
It won't change anything...
@bandikoot Those are about pinned chats :)
I'll look into it later today.
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
Still happening. Still very annoying.
Someone could add a warning to the inconspicuous "Labels" toggle that triggers this unwanted migration.
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!