On Fri, Jul 5, 2024 at 5:47 AM Eric Auer via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote: > > > Hi Jim, > > sounds like somebody copied their whole spam wiki on top of our wiki? > > That means it barely got damaged, we only need a way to mass-delete > their content, recognizable by originating from edits in a very small > time window from many different accounts which all are very young. > > We need some wiki expert to suggest a tool to automate cleaning :-)
While I *think* the spammers "only" copied a bunch of their content into other pages in our wiki, and *probably* didn't damage our pages (such as to add links from "our" pages to "their" pages) we can't be *sure* without looking at everything. That's a lot of pages. And see also this note from my email. Maintaining a Mediawiki requires a lot of work, and you have to patch to the latest version as soon as it's available, and do that *immediately*, or we risk having this happen again. > Maintaining a Mediawiki requires a lot of work. You basically have to > jump onto a new version as soon as they release a new one, because > they often fix security issues (probably like the one that caused our > problem). We were on the 1.41.x version, and the Mediawiki website* > says "The 1.42.0 stable release came out on 27 June 2024." That was > shortly after our wiki was spammed. I'm not excited about a future > where I need to drop all my other work immediately, just to apply a > new Mediawiki version to the wiki website. > *see https://www.mediawiki.org/wiki/MediaWiki_1.42 I think there's a better way to manage documentation. I really like Bernd's suggestion. See my reply to him about how to extend it - I think that will cover all our use cases, and provide flexibility down the road. Jim _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
