Weird Discord bug after mass deleting messages that Undiscord isn't taking into consideration #450
Replies: 2 comments 6 replies
-
|
Since Undiscord assumes there are no messages if page 1 is empty, which is false, and there's no interest in caching more than one page for deletion. Then the best solution I have right now is:
|
Beta Was this translation helpful? Give feedback.
-
|
good workaround |
Beta Was this translation helpful? Give feedback.
-
|
@abbydiode that's not a viable solution since I have waited days for the first page to be re-populated. It did seem to fix itself after I posted a message and waited several hours. So Discord won't update the search if the server is inactive. Not always viable. Still, I do think Undiscord should take this into consideration. An empty first page, with additional pages, does not mean there are no messages. It would give a more reliable tool that goes around this Discord bug. |
Beta Was this translation helpful? Give feedback.
-
|
thank you for the detailed issue, unfortunately these edge cases are hard to test for since I no longer have anything that old to delete, and I can't send messages in the past. I have test accounts but I can only send fresh messages, in order to delete, if you still old have messages and you volunteer to be a test subject, we can try something. I have a new update in the works right now, the code has been tidy up significantly, should be easier to test for a new end condition. That said I haven't thought too much about your suggestion but I will try to take a careful look at it later today if I can. |
Beta Was this translation helpful? Give feedback.
-
|
While I do understand it's hard to test and it's a niche situation. Personally this is what I do use the script for, to delete old archived messages. It's a mostly inactive server, and this issue started to occur after deleting thousands of messages while the server was inactive for I think at least 2 days, which isn't much for a slow or even abandoned server, of which you want to remove your messages for private reasons. I don't think it has to do with the age of the messages, and I suspect it's just that if a server is inactive for 2 days or so, the search isn't being re-cached, and this issue isn't really noticeable until you delete thousands of messages (with is what this script is for, right?). Sometimes you don't even have the option to update the server, for example if it's an old archived server where writing is disabled, or it's a DM with someone I no longer want to be in contact with and don't want to randomly alert them, and if someone were to block me then I can also not write in the DMs. The last (my message) was sent at 2023-03-02 03:20 UTC+1, and I still got several thousands of messages to delete. So we'll see if the issue appears again. I do also wonder if it would speed up the searching after completing a page or in some other way improve it, if the "before date" was updated to be the time of the last message, since all prior messages are confirmed deleted anyway. It doesn't solve the issue where it stops when it finds an empty page, but it will reduce the likelihood of finding an empty page. 5 minutes after writing this reply and: So it took 13 h 34 min before it's acting up again. Although rerunning the script does make it work again. So even though the search works, having it not just stop after finding one empty page still helps with random bugs too. For example, imagine letting it run to delete messages for hours while you're away. You're back after 24 hours, and it has failed 3 hours in because Discord randomly returned an empty page once. 21 hours wasted. It really shouldn't give up this easily. It really should check more than one page, if possible. |
Beta Was this translation helpful? Give feedback.
-
i agree. I will try my best to make this work. currently there's already a workaround when a person have dozens of system messages "person have started a call..." and they pile up at the bottom filling an entire page of messages that can't be deleted. so in that case we increase the offset and keep looking for messages pages forward. on that stuck channel, if you use the discord app search what the results look like? it shows how many pages at the bottom? |
Beta Was this translation helpful? Give feedback.
-
|
When I searched for my username with no other filters inside Discord itself, when it "found" the deleted messages as real messages. The whole first page was empty in Discord, but the page navigation was still available. I could navigate to page 2 and 3 as usual, which were also empty. Page 4 had 2 messages (and presumably 23 deleted messages) and page 5 and onwards appears as normal. So these phantom deleted messages won't show up, but they still take up the place of a real message. |
Beta Was this translation helpful? Give feedback.
-
|
yes , I have seen that before too. |
Beta Was this translation helpful? Give feedback.
-
In short. After mass-deleting messages, Discord search will act weirdly. If you search for that user, you will get some blank pages, but if you continue to scroll, you will find actual messages. Undiscord seems to still be able to estimate the total number of messages, but if the first page or more are blank, then it will fail to delete any messages and just give up.
But if you set the "before" date to a date that makes the first page have a valid message show up in Discord search, then Undiscord will find these messages and delete them. But after deleting the messages of the first page, and make a new search, Discord must at this poit return a blank first page again.
This search was done with the before date set to 2017-11-04 21:00, and after deleting 25/983 messages, it fails. The last message is dated 2017-11-03 14:04:44. If I retry without changing the date, it will find 983 messages, but 0 to delete, and will stop. If I update the before date to 2017-11-03 14:05, it works again.
The issue is clearly that Discord has for some reason stopped considering deleted messages to be deleted. Undiscord need a way to work around this and still delete messages. It only tries to delete page 1 and assumes Discord has updated the search, which isn't always the caase.
So there are two "solutions", and both wouldn't be bad to implement:
Beta Was this translation helpful? Give feedback.
All reactions