v2.4.1

• Fixed crash in plaintext formatter [#79]

v2.4.0

• Several robustness improvements regarding unexpected telegram-cli behavior, especially when downloading media. See #73 for details. Contributed by @jmendeth, also thanks to @pdonadeo for the original PR.
• Make standard output unbuffered for better piping to other programs (contributed by @jmendeth)
• Default setting for maximum_dialogs is now much larger. If you were having issues with some dialogs not being found by the script, this might have been causing it. [#59]
• Forwarded messages are now shown as forwarded in HTML output [#60]
• Fixed crash caused by messages with an empty ID field [#72]
• Fixed crash caused by the HTML formatter attempting to linkify URIs in certain message texts [#75]
• Speed up dumping somewhat by subracting processing and media download time from sleep time

v2.3.0

• Implemented a new method for determining message freshness that does not rely on dates [#35]
• Added support for communicating with telegram-cli through a unix socket (contributed by @tmmsartor) [#56]
• Support for more event types in HTML and plaintext formatters [#49,#50]
• Fixed a problem where some user ids do not appear in the PISG usermap in certain situations
• Fixed a problem that could cause full formatting memory usage even if all formatters are disabled [#57]

v2.2.0

A number of new features have been lingering on master for a while and haven't had any issues reported, so it's time for a new tag. Changelog:

• Added support for supergroups [#22]
• Added option loop_video to HTML dumper for autoplaying videos/gifs (contributed by @gorlug)
• Added option maximum_dialogs to allow dumping of dialogs beyond the 100th (contributed by @the-glu)
• Added option chunk_retry for retrying message chunk requests when telegram-cli times out (contributed by @4r0n05)
• Option backup_dir may now be an absolute path (contributed by @araishikeiwai)

Because there are some new configuration options, if you use a customized configuration file, it should be recreated based on the default one.

---

The next major feature I am planning is a mode where telegram-cli is run under supervision of telegram-history-dump instead of having to start it manually. This will be easier for many users, but the most important reason is to allow crash recovery (automatic restart of telegram-cli), as it turns out telegram-cli regularly crashes on media downloads, and since it is currently not being actively maintained this will likely not change in the foreseeable future.

I will also handle some open issues that I haven't gotten around to yet.

v2.1.0

• Compatibility changes for latest telegram-cli master (tested against tg#6547c0b)
• Added dir and limit CLI options (contributed by @Hiyorimi)
• Added support for backing up user dialogs when the other user does not exist anymore [#14]
• Changed config.yaml template to use brace notation for objects, to prevent headaches from accidental spacing mistakes causing weird behavior

v2.1.0 beta1

v2.0.x versions have a compatibility issue with the latest master revisions of telegram-cli. Specifically, incremental backups are broken (see #15). This beta should be compatible with the latest telegram-cli but has not been thoroughly tested yet.

v2.0.1

• Fixed division by zero in HTML formatter (contributed by @hennes-maertins)

v2.0.0

• Configuration format changed to YAML (eliminates json5 gem dependency)
• Support for incremental backups [#3] (enabled by default)
• Improved compatibility with telegram-cli test branch [#4]
• Better support for custom output formats by introducing formatter modules [#6]
• Added HTML formatter (contributed by @lgommans)

v2.0.0 beta1

This beta version is intended for users who want to beta test partial backups (issue #3).

v1.0.0

This version has been successfully used for a while now and should be good for the foreseeable future. Future improvements will be released according to the semantic versioning standard. Specifically, everything that could severely break your backup routine will be a major number bump, new features and other significant (but compatible) changes will be a minor number bump, and bugfixes will be a patch number bump.