Tim van der Staaij

The history of the group before it was converted is still associated with a regular group, with the group name it had just before being converted. Backing them up separately...

I'm glad you find it useful! And getting an issue that is not really an issue and not a support request camouflaged as an issue either is a first for...

In the sense "possible as in having enough data saved", yes. The jsonl files contain all the data necessary to create a formatted version. See [this script](https://gist.github.com/hay/7f5124f9992038d6c1ed00e1ed52772f) for example. In...

The thing is, the Telegram history downloading progress goes like this for every dialog (*n* is the chunk size): * Get *n* messages from offset 0 (these are the *n*...

The above commit is an implementation of the temporary file strategy I mentioned earlier. You can try it out if you want, note that this is on the branch `dump-old-to-new`...

Formatters should also work after the above commit, and again requires a fresh backup.

Actually, forwarded messages and replies are shown as such by the plaintext formatter, but not by the HTML formatter. I just implemented forwarded message support in the HTML formatter for...

I have not personally experienced any kind of service ban as far as I know. Although I should also mention that I generally don't have media downloads enabled. Telegram does...

Yes, these are called "service" messages, and can be identified by a `service` field set to `true` in the JSON files. Example: ``` json { "event": "service", "id": "02000000460c1000130b0300000000000000000000000000", "flags":...

Yes, Telegram considers the supergroup as a new entity with its own history, so when converting to a supergroup the history is not inherited. The old group will still exist...