Undiscord 5.2.4, but with some fixes.
UPDATE: MY FIXED UNDISCORD VERSION HAS ALWAYS WORKED, BUT I FEEL JADED ABOUT UNDISCORD SO I AM SWITCHING TO DISCRUB.
I am thinking about abandoning Undiscord. It does not sit right with me that the 401 errors have existed for three years and the Undiscord developer doesn't want to do anything about it. So many people have posted possible fixes, and not a single one has been implemented. We can show clear, concrete evidence that for the 401 errors, Undiscord is taking a user's password and plugging that into the Authentications Token box. Why in the world would we be happy with our Discord password being taken and plugged somewhere it does not belong? And the fix is so simple. We can just replace the word "password" with "text" and the 401 errors go away and the script works. Also, in two years, we only got one freaking update, and it was a simple one that someone else made. It had nothing to do with 401 errors.
The following extension seems to be a better alternative to Undiscord. I thought about using it 6-12 months ago, but I am often afraid to try new things. But I'm probably going to switch to it now. It is regularly updated, has a lot of users, has a lot of positive reviews, is available on Chrome Web Store, and seems to do a great job. It probably has more features too. Like mass editing messages instead of removing them, etc.
**Discrub - A working alternative to Undiscord that you can install from Chrome Web Store**
https://chromewebstore.google.com/detail/discrub/plhdclenpaecffbcefjmpkkbdpkmhhbj
PREVIOUSLY
The official Undiscord is here:
https://greasyfork.org/en/scripts/406540-undiscord
For two years, it was abandoned and stuck on v5.2.3. Users were unable to use it because of 401 errors. These errors are caused by autofill. Undiscord takes the user's Discord password and replaces the Authentication Token with it, and that is the cause of the 401 errors.
I applied the fixes suggested here and named my version 5.2.3.with.fixes:
https://github.com/victornpb/undiscord/discussions/627#discussioncomment-10232854
I also modified Line 101. There was a problem where if my browser window was too small, anytime I clicked on the Undiscord button the popup Undiscord window would be mostly off-screen. So I changed the position attribute and set it to right:44px, which means the right edge of the Undiscord window will always be 44px from the right edge of the browser no matter how small the browser window might be.
Then around June 2025, there was a bug where the official v5.2.3 and my v5.2.3.with.fixes was broken because the Undiscord window was almost completely transparent, making it impossible to see. The official developer of Undiscord then came back after a two year absence and applied some fixes to fix the transparent Undiscord window. I also applied those fixes to my v5.2.3.with.fixes.
I then compared my newest v.5.2.3.with.fixes.c with the official v5.2.4. They were identical except I had the fixes for the 401 errors, and two other small fixes for things like the Undiscord window being off screen when the browser window is too small and Undiscord not deleting all of the messages even though there were messages left. When I saw that my userscript was almost identical to v5.2.4, I renamed my version to v5.2.4.with.fixes.
All of the fixes that I made were extremely simple but fixed critical bugs.
You can see the full list of changes by comparing my userscript with the official v5.2.4 one:
https://github.com/victornpb/undiscord/pull/719/files
https://www.diffchecker.com/oLdrptRi/
