All notable changes to this project will be documented in this file. The format is based on Keep a Changelog.
- Synpurge can now cleanup/reindex the database as it works through the
rooms. This is disabled by default and has to be enabled in the
[database]section of the configuration file. - Synpurge can now fetch room lists from PostgreSQL directly. If database access is configured, this faster method is used automatically (#6).
- Improved filtering of rooms for which a valid reference event could not be found. As a side effect, information message in verbose mode report progress done/total more accurately.
v3 - 2017-01-05
- Synpurge can now connect directly to PostgreSQL to map dates to events. This makes operation substantially faster.
- Purging rooms for which a suitable reference event cannot be found are skipped, instead of causing API calls to the purge history endpoing which have bogus parameters.
v2 - 2017-01-05
- New command line syntax, with subcommands.
- Better logging: the
purgesubcommand supports both verbose operation (-v,--verbose), and outputting debug messages (-d,--debug). Note that full URLs including the access tokens being used are printed when debugging output is enabled. - The
purge --pretendwill figure out which calls to the purge history API endpoint are needed, and print a summary without doing the requests. - Added the ability to continue with the next purge operation on a timeout
(
-k,--keep-going).
- Python 3.4 is supported now.
- Include
CHANGELOG.mdin generated tarballs.
- Initial implementation.