Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Emergency Breaking API Change #208
The bulk_delete endpoint will no longer delete messages older than 2 weeks.
This was not a decision made lightly, as I've finally narrowed down the root cause of the recent API stability issues to people using bulk delete to purge channels with extensive message history, creating excessive table fragmentation within our cassandra cluster.
We'll be introducing a proper "purge channel" endpoint at some point in the future - which will be able to delete old messages without creating excessive table fragmentation (we already have a plan on how to do so).
For now, bulk delete requests will silently discard older messages when attempting to delete. The next time we roll APIs, the API endpoint will fail with a bad request, with error code:
You can figure out the minimum allowed snowflake with the following code:
added a commit
Jan 30, 2017
So the only solution to bulk delete old message is to completely recreate the channel and re-configure all integrations that use it? Won't this also remove any notification settings users have and break all invites and links to it? That's pretty unfortunate.
At the very least, the documentation should be updated to no longer indicate that a solution is coming for this.
@shkkmo Time ago, you can't delete default channel, and everyone mass deleting messages - that why they said
Through a bot if your bot has the right permissions you could shift the webhooks to target the new channel before deleting the old one? That would probably solve a significant portion of your integration issues.
Still deletes invite links, user notification settings (I think)...