You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just upgraded a group to a supergroup. Everything fine on telegram desktop (it doesn't even mention the group has been upgraded tbf...).
On TELEports (which uses tdlib) the history before the upgraded is no longer visible.
I just saw issue #223... Would it be possible for tdlib to do this itself and just expose the history of both chat before and after the upgrade unified?
The text was updated successfully, but these errors were encountered:
The old messages are still located in the old chat. They are only visually showed to the user as being in the supergroup chat history. They can't be transparently returned in the supergroup's history, because given that they are located in the basic group, they can't be replied or pinned, don't have a public link even the supergroup is public, can be deleted just for self and are different in much more ways from the supergroup messages.
This can be transparently implemented in the future in TDLib, but proper implementation will need really a lot of changes in TDLib's API and internally.
Humm so the original question would be, how did the old Telegram clients (pre-tdlib) merge these chats transparently? For each message you would need to remember from which chat it came if you want to act upon them. I find this overly complex.
I've just upgraded a group to a supergroup. Everything fine on telegram desktop (it doesn't even mention the group has been upgraded tbf...).
On TELEports (which uses tdlib) the history before the upgraded is no longer visible.
I just saw issue #223... Would it be possible for tdlib to do this itself and just expose the history of both chat before and after the upgrade unified?
The text was updated successfully, but these errors were encountered: