Export tool doesn't register [from][to] time frame

[Younes-L]

Steps to reproduce

1. Select chat
2. Export messages
3. Choose "from" date (not oldest/first) to "present"

Expected behaviour

Only messages from specified time period are exported

Actual behaviour

ALL the messages are exported

Configuration

Operating system: Windows 10

Version of Telegram Desktop: 1.6.2

Used theme: default dark

Logs:

Insert log.txt here (if necessary)

[john-preston]

@Younes-L All messages are processed, but only the ones in the requested interval are written to the exported file. Otherwise I wouldn't be able to show the progress of the export :( that's an API limitation.

[Younes-L]

I only wanted a day's worth of messages, ended up with over 126k messages in processing it takes a super duper long time... Also can't do multiple exports at once.

Can this be solved by disabling progress bar ? We could have a check box "show progress" (with a warning it will take more time) or maybe have it hidden somewhere in settings.

[Niko-O]

In 1.7.10 it's not just "processing" all messages, it's saving them as well. I too wanted just a day worth of messages, but the export folder got to 7GB overnight before I cancelled, which is interestingly also more than the maximum of 1.5GB. The first message in the first "messages.html" file is also the first message ever posted in that group. Coincidently it also happened to be a 25th, but November 25th, 2015 while the interval I selected was June 24th 2019 to June 24th 2019. So I don't think that's related.

[john-preston]

@Niko-O I could’ve broken that, I’ll check.

[john-preston]

@john-preston Are you sure you've selected a valid period? I tried to export messages for one day (2nd July - 3rd July) and exactly them were exported. Can you share what settings and limits are you using exactly when it doesn't work?

[Niko-O]

Interesting. I tried it again and the behavior was different.

For all tests the overall settings are the same: All options active (Photos, Video files, Voice messages, Round video messages, Stickers, Animated GIFs, Files), Size limit is set to the maximum of 1500 MB *1, Download path is default ("Downloads\Telegram Desktop").

From the same very large group from my previous comment, I exported from 24.6.2019 to 24.6.2019. So the same dates as last time and the same overall settings too. Telegram did not immediately start writing out the html file and the progress was advancing in increments of 100 (which it did not when all messages were exported). Overnight the process finished. The resulting messages.html file was empty except for the group name header and "No exported messages".

Same thing happens in a small non-group chat.

However, when I select two non-equal dates (i.e. 3.7.2019 to 5.7.2019), messages from the end-date won't be exported. This is very unexpected. The end-date should be inclusive. Leaving "today" as the end date correctly exports messages from today. *2

I was not able to reproduce the behavior of exporting all messages when a small interval is selected. So either I goofed up or it's an inconsistent bug. The fact that at least one other user had this happen gives me hope. Any chance it's a UI bug where the start date is displayed but some variables aren't updated correctly?

Currently I'm exporting 24.6.2019 to 25.6.2019 from that same large group chat. I'll get back to you tomorrow (in ~14 hours) when it is hopefully done. *3

Edit 1: The export contains messages from 24.6.2019 only. But interestingly that took way less time than what I thought it would. I'll try again with 24.6.2019 as the start- and end-date to see whether that takes longer.

Edit 2: No, that also didn't take super long. I'll do another test (24.6.2019 to 24.6.2019) with a different big group chat where I haven't exported anything from yet.

Edit 3: No, same result. Well, I don't know what was going on.

*1 I'd like to add that that's somewhat arbitrarily low, considering I have a chat spanning 6 months and the export is (and I'm almost afraid to mention it in fear that it might get "fixed") 1.61GB big. Is there a good reason why "no limit" is not an option?

*2 I can open a new issue for this, if you would prefer that.

*3 As @Younes-L mentioned, this is quite frustrating when you only need a very small amount of messages but need to wait for hours. An option for ditching the progress would be lovely. And while I'm nagging: If the export dialog could remember its settings, that would be neat as well ;)

[Ovsyanka]

I faced this issue too. Any news about it? Will it be fixed any time soon? Do you need any help to reproduce it or something?

[Aokromes]

this bug is still valid?

[Niko-O]

Yes

[nicekkl]

@Younes-L All messages are processed, but only the ones in the requested interval are written to the exported file. Otherwise I wouldn't be able to show the progress of the export :( that's an API limitation.

If I don't want to show the progress of the export. And only the ones in the requested interval are processed. What should I do?

[nicekkl]

@john-preston

[nicekkl]

@Aokromes Could you please tell me when this bug will be solved? Exporting by time is really time-consuming now. ==

[stale[bot]]

Hey there!

This issue will be automatically closed in 7 days if there would be no 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!

[Ovsyanka]

This issue is still actual. If I choose some interval all messages processed, and this take a lot of time. Only chosen interval exported though.

[john-preston]

The last one - range applies to exported messages too, only the ones in selected range are exported (with attachments), but right now in order to show the progress correctly all messages should be gone through, even the ones outside the range, but skipped.

Recently there was a server API addition that will allow to improve that in the future and go only through the messages inside the selected range.

[john-preston]

@afwn90cj93201nixr2e1re No plans to extract any libraries right now, sorry.

[RememberTheAir]

And one more, as we already know there's 1m. limitation in chats, right?

This is already not the case when exporting chats. The export will also include these "archived" messages

[RememberTheAir]

@afwn90cj93201nixr2e1re yes it is:

This tool will be particularly useful for users who have millions of messages and can’t easily access the oldest parts of their messaging history.

This is taken from the official blog post introducing tdesktop's export tool: https://telegram.org/blog/export-and-more. Thanks for the additional salt though

Editing this message since I don't want to pollute this conversation even further with offtopics: I know this is irrelevant for the original problem described in the OP - I just wanted to point out that the famous "one million messages limit" has nothing to do with @afwn90cj93201nixr2e1re's voice messages issues, as he seemed to suggest in his previous comment

[Niko-O]

@afwn90cj93201nixr2e1re Yes, it seems like @RememberTheAir got something mixed up. But your sodium levels are like 50 times higher than the ideal daily intake of any adult.

@john-preston To me it seems like the disadvantage of not having an overall progress is heavily outweighed by the ability to have quick exports. Having a checkbox to enable or disable the progress was also suggested. Could you elaborate on why it wasn't changed yet?

[stale[bot]]

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!

[Younes-L]

no worries, this is an error, happily @stale

[stale[bot]]

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!

[Niko-O]

It still needs to crunch through all posts since the start of the chat, even when you only want a small time frame at the end. And the selected time span is still start inclusive and end exclusive.

So yes, stale bot, this was an error.

[psamim]

I can still see this bug.

[github-actions[bot]]

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!

[SpL1Ne]

Still relevant.

[github-actions[bot]]

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!

[Niko-O]

,jghqdsfhgjhgwrhtk.

[github-actions[bot]]

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!

[Niko-O]

fart