Closed CTassisF closed 6 years ago
Following the v1.1.0 update I noticed that supergroups are always recognized as channels and because of that the sender_id attribute of the table messages is always empty when that message is from a supergroup.
sender_id
messages
According to the following code, it was supposed to be empty only when that message comes from a channel: https://github.com/fabianonline/telegram_backup/blob/2321fa11eec72ec9d3d7d3e8fd2b774f6c1f4c84/src/main/java/de/fabianonline/telegram_backup/Database.java#L216-L221 It may still be possible to get the sender_id from channels though when "sign messages" is enabled for that channel.
I guess this is happening because supergroups are in fact channels with the megagroup attribute set to true.
megagroup
true
Thanks. Fixed this in code. The fix will be included in the next release.
Thanks! By the way, I think the data saved in the chats table still saves supergroups as channels.
chats
Following the v1.1.0 update I noticed that supergroups are always recognized as channels and because of that the
sender_id
attribute of the tablemessages
is always empty when that message is from a supergroup.According to the following code, it was supposed to be empty only when that message comes from a channel: https://github.com/fabianonline/telegram_backup/blob/2321fa11eec72ec9d3d7d3e8fd2b774f6c1f4c84/src/main/java/de/fabianonline/telegram_backup/Database.java#L216-L221 It may still be possible to get the
sender_id
from channels though when "sign messages" is enabled for that channel.I guess this is happening because supergroups are in fact channels with the
megagroup
attribute set totrue
.