Please prevent crawlers from accidentally activating `undo` links
This has been going on for years, the unwanted changes and their reversion keep spamming the log, which is especially annoying for those who are subscribed to the feed. Here is a recent and ongoing example.
It seems around 100% of reverted changes from logged out users are undesirable and should themselves be reverted, so the easy fix would be to make the undo function available to logged in users only. If you want to implement a more granular counter-measure, that's great too!
Here is the latest instance, 200 reversions by 1 bot in 5 minutes, which I then had to revert by hand in 30 minutes...
Please prevent logged out users from using the "Undo" feature URGENTLY!!!
(... Come to think of it, not sure this is the best repo to report this... Certainly feel free to forward this to the best place.)
@vsedach Hi! Can you help with this issue?
Ah, right, I should have thought of pinging him, thanks!!
Yes, I agree and also noticed the problem. I will try to put together a fix soon.
The current CLiki2 project page is at common-lisp.net: https://gitlab.common-lisp.net/cliki2/cliki2
Awesome, thank you!!
For the record, I consider usage of non-GitHub code hosting platforms to be a completely insane, gratuitous usability problem nobody should ever contribute to, but whatever...
(Yes, I fully realize there is nearly zero point in pointing out the obvious since it's obviously not going to help anything at all, most likely.)
GitHub was purchased by Microsoft, not sure why you want to use it anymore. I will probably have time to work on this in May.
GitHub was purchased by Microsoft
Literally so fucking what?!?
Hating Microsoft in 2000 was fucking meaningful. Hating Microsoft in 2025 is fucking meaningless.
There were rightful fears before the acquisition that Microsoft might completely ruin GitHub, but it has literally gotten exponentially better since then, especially thanks to GitHub Sponsors.
The main drawback has been people suiciding their projects for no fucking reason by migrating to completely unviable code hosting platforms.
not sure why you want to use it anymore
Because it is literally the ONLY viable code hosting platform, at least for anyone who cares about usability and success. (Except for NSFW projects, obviously.)
I will probably have time to work on this in May.
Awesome!! 🎉🎉