1.3.1

• Adds a new feature for skipping specified channels using the -s parameter (thanks to @git-bruh for introducing this)

1.2.7

• Fixes #25. Thanks to those of you who reported the issue.

1.2.6

• Fixes an issue where the Linux build did not run on systems with older GLIBC

1.2.5

• Support for detecting Discord PTB/Canary and grabbing the auth token
• Update to API v8
• Some other minor fixes

Deletion is currently very slow because the API appears to have throttled deletions to about 1 message/s. It is unclear if this is permanent.

1.2.4

• Marginal speedups to deletions by reducing the number of 429 responses
• Added --dry-run/-d for partial deletion
• Changes to make us ready for the switchover to discord.com, with thanks to @kanouharu

You may need to update to this version in the near future. Discord are moving everything from discordapp.com to discord.com which will break previous versions.

1.2.3

• Fixes an incorrect assumption that the token will always be a multi-factor token

1.2.2

• Added support for automatic token retrieval on Linux when using the unofficial client
• Added nice summary message at the end of deletion totalling number of deleted messages and requests
• Minor code improvements

1.2.1

• Added automatic token retrieval feature for Windows
  You no longer need to specify the DISCORD_TOKEN given you have the Discord client installed and are logged in. Just run ./discord-delete-windows.exe partial and it should start working.

1.1.5

This release mostly reverts the commits of the previous release.

Discord's API has reverted to the previous behaviour. They appear to have also alleviated their backend problems.

You will probably need to update to this release for message deletion to work properly once again.

1.1.4

This release has a fix for messages not being deleted due to an update in the Discord API.

As per the comments made in the code, the Discord API returns empty pages where messages have been deleted now. In the past, the Discord API immediately removed them and shifted other messages to the top. This is possibly related to their Cloudflare response caching.

There may still be problems deleting messages due to these API changes. Please report these under issue #21.