User talk:Drakkos

From Discworld MUD Wiki
Jump to: navigation, search



Sorry to bother you, but I think a simple change in css might make quoting things from the mud much easier, namely by making <pre> tags wrap long lines and I think maybe only you can change the css file(s) for the wiki.

This is in response to some complaints raised by visitors about lack of wrapping lines in <pre> tags that results in horizontal scrolling and breaks in the layout.

Unfortunately, other options like using the template:prebox doesn't preserve white space or newlines and requires adding lots of <br> tags which change the space between lines. (See other options considered here and here.)

I'm wondering if it would be possible to add the following lines to the existing lines in the css file(s) in the pre section:

pre {
 overflow-x: auto; /* Use horizontal scroller if needed; for Firefox 2, not needed in Firefox 3 */
 white-space: pre-wrap; /* css-3 */
 white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
 white-space: -pre-wrap; /* Opera 4-6 */
 white-space: -o-pre-wrap; /* Opera 7 */
 word-wrap: break-word; /* Internet Explorer 5.5+ */

I think this would make it work like people expect, preserve white space and newlines but wrap if it doesn't fit in the browser's window. It seems to work in local tests.

Thanks. Frazyl 01:16, 31 March 2010 (UTC)


Hi! Would you consider installing the ReCAPTCHA extension? It would hopefully curtail the periodic floods of spam we've been getting while not overly inconveniencing non-spambot users (since it looks like it only triggers for edits that include external links (it might be possible to have a whitelist, too, as the extension it's based on allows that--whitelisting Kefka's site, the MUD's site, dwpriests, and the tm wiki would probably take care of nearly all legitimate external links), and the CAPTCHAs have audio versions). I'd swear the last one must have had seventy spam edits or so... preemptively protecting pages (and their research and talk pages, argh) that are a couple links away from the main page seemed to basically work, but it's not exactly the greatest solution. --Ilde 03:31, 23 April 2010 (UTC)

Sure - having some internet connection problems at the moment, but I'll install it when I can. Drakkos 07:37, 23 April 2010 (UTC)
Hooray! :D Thanks heaps. --Ilde 07:45, 23 April 2010 (UTC)

Quest namespace


We've talked for some time on Talk:Main_Page#Quest_pages about having a Quest namespace to solve issues with Special:Search and Special:Random picking up quest information. Also each quest could have a page with visible text that could be included hidden in the list pages, making quest editing and reading easier while preserving the ability to read a couple of lines only on the list pages.

As far as I can tell this would involve adding the first two following lines in the LocalSettings.php file and optionally modifying the last line so the pages in the new namespace are counted as articles. See also Manual:Using_custom_namespaces.

$wgExtraNamespaces[110] = "Quest";
$wgExtraNamespaces[111] = "Quest_talk";

$wgContentNamespaces[] = 110;

Using another existing namespace could work but it would probably be less optimal. The Help namespace could be used since there's only the Help:Contents page in it, but it would be less clear that they contain quest information.

So if you think it's a good idea and modify the LocalSettings.php file we can start moving pages to the new namespace and gradually transfer each quest into its own page.


--Frazyl 22:06, 25 March 2011 (UTC)


Argh, not got email on this box - if you haven't seen it yet, I just saw has something on the main page that you might want to be aware of. Zexium 08:40, 21 April 2011 (UTC)

Quest namespace again


Thanks for the new roles, I'll do my best to live up to them! It'll be nifty to deal with spammers. :)

By the way, I don't know if you've seen the above message for adding a Quest namespace to isolate quest information?

For this one I'm pretty sure we need you! :P

Thanks again!

--Frazyl 02:48, 2 May 2011 (UTC)

I had actually missed that one, but I have done exactly as you have instructed! I presume it has had some sort of effect, or at the very least has not broken anything. Drakkos 16:26, 2 May 2011 (UTC)

Mmmm it doesn't seem to have worked for some reason. :(
It doesn't show up in the interface and I tried to move a page and it stayed in the (Main) namespace.
The manual says changes to LocalSettings.php should apply immediately...
So after thinking for a bit trying to find a reason it isn't working I've thought of:
- Maybe there's another LocalSettings.php somewhere that's being used instead?
- The manual says that on "wiki farm" configurations the file CommonSettings.php may be used instead. Probably doesn't apply.
- Not sure what else. I suppose the position of the lines in the file but it should be next to where the "Research" namespace is already defined. If we follow the manual the lines should go near the end after everything except the $wgDefaultSkin variable...
--Frazyl 00:05, 3 May 2011 (UTC)

Extensions to fight spam


There are still many spammers that regularly modify pages on the wiki, which need to be reverted. I think that adding some extensions would greatly diminish the undesirable edits.

The TitleBlacklist extension prevents creation of users and new pages according to regexp rules. Once setup this should prevent most of the current edits once the pattern is blocked unless the spammers mimic normal users too closely.

For the second line of defense it would also be useful to block edits based on the data entered. I think the best extension for this is AbuseFilter (which requires AntiSpoof), since in addition to blocking based on keywords it also permits actions based on many different conditions, for example if a user is moving a User or User_talk page, new users adding links, etc.

The User Merge and Delete extension would allow us to get rid of the spambot users (merging them into Anonymous and deleting).

The CheckUser extension would allow permitted users to see the ips used by (spam) users and users using some ips to ban ip ranges if all else fails.

I hope it is agreeable and not too much trouble to install theses extensions.


--Frazyl 10:46, 18 November 2011 (UTC)

We could really use the AbuseFilter extension right now to prevent the current deluge of vandalism and spam by bots!

--Frazyl 04:47, 18 December 2011 (UTC)