User talk:Lethosor

From RogueBasin
Revision as of 16:38, 7 February 2016 by Kyzrati (talk | contribs) (→‎Main page spam)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

I have asked the site owner, User:Bjorn, to make you an administrator as you have been helping with spam deletion. You are welcome to email him with any suggestions for changes to the site. His email address is on his user page.

I also asked Bjorn to install the AbuseFilter extension, but it seems not to be configured correctly and is preventing all page deletions at present. I have drawn this to his attention. Once AbuseFilter is working properly, you might be able to create some filters (or import them from Wikipedia) to prevent spammers from creating pages at all.-Muscles (talk) 02:39, 23 May 2013 (CEST)

Thanks for letting me know. AbuseFilter seems to let me delete pages right now, but it can be picky sometimes :) Lethosor (talk) 01:57, 24 May 2013 (CEST)


Hey. Could you please answer this or redirect me to someone who can? It's posted here. -Joel Pera (talk) 14:48, 17 September 2015 (CEST)

Main page spam

Hey Lethosor,

Several months back I started moving duplicate releases to the old news, so that for each game there is only one notice on the main page (the most recent release). It was getting really crazy with some devs intentionally spamming it with a new release every day or two and covering the main page (because, understandably, a *lot* of traffic comes from Rogue Basin). A lot of devs over on /r/roguelikes were talking about this, and some have either felt wrong about spamming the main page and avoided putting up notices for new releases if in rapid succession, or who were outright deleting their previous entries, both of which are bad for the community in terms of record-keeping, so it would seem like the best course of action is to simply move duplicates so they're not on the front page. Is there a better solution to keep the main page spam free? I know I feel better about putting up multiple new release notices if I don't have to delete an old one or look like a spammer on the front page... --Kyzrati (talk) 03:10, 7 February 2016 (CET)

I guess that makes sense, but it seems like it would be a lot more maintenance to reorganize everything when migrating all of a month's releases to old news (if you don't mind doing that, it's fine with me). It would be a lot easier to set up something cleaner (e.g. hiding duplicate releases from the main page but keeping them on news or old news) if this wiki had decent extensions, like ParserFunctions, but unfortunately it doesn't. About the only solution I can think of is wrapping each line that shouldn't be on the main page in <noinclude>...</noinclude>, but that's pretty messy.
The difference between the two categories on old news could be clarified, though. I think I understand that the lower one contains releases that have been superseded, but the upper one confuses me - for example, it currently contains "The Temple of Torment Stable 8.3", which makes some sense since 8.4 is listed on news, but why isn't it in the lower category? Lethosor (talk) 17:21, 7 February 2016 (CET)
Yeah, I visit every day anyway, and there's rarely more than one release every day or two, so it's easy to take care of. That and several of the devs I know with multiple releases per month take care of their own because they saw all the spamming and we talked about it. I'll admit the two lists are kinda confusing, but it ended up that way because out of fairness we can keep up to two months of releases on the front page, but that means that technically a release in two separate months will still end up with multiple duplicates on the main page. (E.g. ToT has had a Feb release, too, so I temporarily removed the second entry from the main page, and come March I'll spice the main page's January list into the proper two sublists.) If you look back at previous months you'll see what I've been doing for the final results. It seems like the best solution for both keeping a record of releases while making it easier to actually read what's new, which is the main purpose of news :P. It's also scared away a couple of the spam releasers, and in one case a dev has started just removing his older releases, which is fine by me so long as we don't have a ridiculous amount of spam. Certainly an automated approach would be the best, but I'm sure that could end up complicated and I don't mind doing it to keep things tidy. (Honestly I first started it because there were two devs in particular who were releasing a huge number of insignificant updates for the publicity, and it was pissing me off. Since then one of them had the only copy of his project deleted, and the other has all but stopped development lately for some reason. Then there was also the case of a commercial company release spamming their product here and I don't want to see them return... But anyway, the cleaner look gives a better impression for visitors, so may as well keep it up.) And thanks for understanding. I first hit undo, and then saw you were an admin and went oh damn, maybe I shoulda talked first :P --Kyzrati (talk) 17:38, 7 February 2016 (CET)