User talk:Dr ishmael/Archive 9

Well then
Time to clean house. &mdash;Dr Ishmael 21:49, 30 November 2010 (UTC)

looks great
Its eerily good, dude. Congrats to you and everyone else involved. JediRogue 17:19, 1 December 2010 (UTC)
 * Where the crap you beed, dawg? [[Image:Felix_Omni_Signature.png]] 19:03, 1 December 2010 (UTC)

Well done and thank you
Thank you for all the time and effort you have contributing to helping Guild Wiki arrive here safely and smoothly. — Tennessee Ernie Ford ( TEF ) 19:47, 1 December 2010 (UTC)
 * Thanks. I really appreciate it. Arnout aka The Emperors Angel 20:21, 1 December 2010 (UTC)

German interlanguage table
The German GuildWiki staff have provided a copy of their interwiki table at http://www.guildwiki.de/vorlage-en.txt. Do you think you could bot the reverse interlanguage links onto GuildWiki? --◄mendel► 15:03, 3 December 2010 (UTC)


 * Wow. o_o Yeah, I can do that, just can't promise when I'll have time for it.  Poke me if I don't get to it by next Friday.  &mdash;Dr Ishmael Diablo_the_chicken.gif 15:16, 3 December 2010 (UTC)


 * Okay, documenting the problem:
 * I can connect to the API, and action=query request work fine, but whenever I try action=edit&nocreate=1 (so it won't create a page that didn't previously exist), I get a 'missingtitle' error. When I leave nocreate undefined, the result is that the page Api.php gets created.
 * I can run action=edit&nocreate=1 on my local MediaWiki install successfully.
 * If $wgEnableWriteAPI is turned off on my local wiki, then I get a 'noapiwrite' error instead.
 * So it looks like the write API is enabled here, but something else is causing an error. I get the same results whether I'm using Perl's MediaWiki::API module or cURL.  &mdash;Dr Ishmael Diablo_the_chicken.gif 04:09, 4 December 2010 (UTC)


 * I'd forgotten that AWB actually uses the API as well. And so does pywikipedia, which I looked into last night.  Which means we are completely borked for automated editing right now.  There is an old Perl module that doesn't use the API, but it probably wouldn't work correctly with the current version of MW.  &mdash;Dr Ishmael Diablo_the_chicken.gif 19:01, 4 December 2010 (UTC)
 * Just a note because I saw you added the first of them: you might want to replace any underscore by a space when adding the interlanguage links to articles, MediaWiki will create the correct links but it will look nicer when viewing an article's source. ;)--Tera 23:00, 6 December 2010 (UTC)


 * Generally, this is complete, although I did have to skip a lot of stuff. I have all of these saved in separate files so someone can review them.
 * EN link was to an article section: 15
 * EN link was to GWW only: 268
 * EN link was to a redirect page: 487
 * EN link was to a missing page: 631
 * Multiple DE pages linked to the same EN page: 569
 * DE links created: 13,600
 * &mdash;Dr Ishmael Diablo_the_chicken.gif 18:00, 7 December 2010 (UTC)
 * Thanks a bunch! I've left a note over at guildwiki.de asking for help; could you upload those lists of links that need review (if they'd be linkified to point here or to :de: that'd be awesome)? --◄mendel► 05:45, 8 December 2010 (UTC)


 * /de &mdash;Dr Ishmael Diablo_the_chicken.gif 17:23, 8 December 2010 (UTC)
 * Thanks! I passed it on. --◄mendel► 18:42, 8 December 2010 (UTC)

Image redirects
Why don't they work? mw:Manual:$wgFileRedirects suggests that they ought to. --◄mendel► 16:48, 4 December 2010 (UTC)


 * "Removed in version: 	1.13.0" I've checked the source code - when parsing redirects, it specifically checks that the current namespace is not NS_FILE.  Wikia hacked the MW code to re-enable them, but we shouldn't follow their example.  &mdash;Dr Ishmael Diablo_the_chicken.gif 17:00, 4 December 2010 (UTC)

Humble Request
To celebrate the move here on Curse, i'd like to improve my userspace to higher standards: Can i borrow some code from your userpage to better customize mine? Sotaknuck 16:52, 4 December 2010 (UTC)


 * Of course. &mdash;Dr Ishmael Diablo_the_chicken.gif 17:33, 4 December 2010 (UTC)


 * Thank you! It looks and feels much better now! Sotaknuck 10:01, 5 December 2010 (UTC)

Images
Whenever you get the chance, upload your skill icons that have no borders to mediafire or something in a archive (.7z would be great, highest compression rate, and less loss), I don't need names. Just keep em sorted by skill ID#. It's actually easier because without names windows can't flip out @ forbidded characters in filenames :) Thanks :) (also: pick any profession) &mdash; Scythe   20:44, 5 Dec 2010 (UTC)


 * Archive compression doesn't matter much when you're dealing with pre-compressed image files, the best you can get is usually 10-15% compression. Anyway, have fun - http://www.mediafire.com/?w1a7572k46acvw0  &mdash;Dr Ishmael Diablo_the_chicken.gif 23:02, 5 December 2010 (UTC)
 * tyvm ishy, they're all uploaded as animations now :D &mdash; Scythe   0:27, 6 Dec 2010 (UTC)

Heyo
Want to start revamp'ing the infoboxes?– alistic 22:23, 5 December 2010 (UTC)


 * I was planning on doing that as the SMW project progressed. Next on my list is locations, since that ties in to the whole Nicholas project.  &mdash;Dr Ishmael Diablo_the_chicken.gif 02:16, 6 December 2010 (UTC)

A History of Violence
Just in case you didn't see on IRC: Wizardboy777 18:16, 7 December 2010 (UTC)


 * Yeah, I noticed that problem a few pages later with [ this page]. I fixed the problem and restarted from that point, but the page you found had already scrolled out of my DOS window's buffer, unfortunately.  &mdash;Dr Ishmael Diablo_the_chicken.gif 18:40, 7 December 2010 (UTC)

Dammit
You beat me to the move of Anything that is unrelated to elephants is irrelephant, and the talkpage message. Stop being faster than me --  Random Time  00:31, 12 December 2010 (UTC)


 * I suppose you're just irrelephant, then. :P &mdash;Dr Ishmael Diablo_the_chicken.gif 00:32, 12 December 2010 (UTC)
 * Haw haw --  Random Time  00:34, 12 December 2010 (UTC)

MediaWiki:TravelerUnknown
Does it still work? Should it become a Widget? --◄mendel► 23:26, 16 December 2010 (UTC)


 * I doubt it will work here, we don't have the necessary framework set up. Or do we?  I dunno.  &mdash;Dr Ishmael Diablo_the_chicken.gif 23:34, 16 December 2010 (UTC)


 * Moved to Widget:TravelerUnknown, and it works, mostly. $wgEnableMWSuggest has to be turned on in LocalSettings for the auto-complete feature to work (and that will also turn on auto-complete for the sidebar's search box).  &mdash;Dr Ishmael Diablo_the_chicken.gif 18:17, 18 December 2010 (UTC)

CurseFooter
The analytics and footer should probably be two separate extensions and where do I stick advertising~ --68.56.228.159 15:26, 18 December 2010 (UTC)

I forgot to log in. -- Bumble talk 15:27, 18 December 2010 (UTC)


 * Why do they need to be separate extensions? I can make them separate functions in the same extension, and set configuration parameters where you can enable/disable the footer or the trackers individually.  Under that framework, ads would just be a third function.  &mdash;Dr Ishmael Diablo_the_chicken.gif 18:17, 18 December 2010 (UTC)


 * It would be awesome if the editors (= logged in users) would be exempt from ads, since they're the ones creating the content. If you would run some statistics and see whether you can afford that, it'd be great (I'd forego gimmicks and gadget rewards if I could have that); it would also allow those of us who are curse.com premium users site the luxury of no ads. (Or do you check that differently?) --◄mendel► 18:25, 18 December 2010 (UTC)

Armor Gallaries Question
Are the guidelines for displaying armor very strict and inflexible? Specifically, if an armor gallery is perfect but "enable post-effects" is on/enabled, does that part need to be retaken and replaced? Or is it "good enough"?--BladeHanover2 15:39, 20 December 2010 (UTC)


 * User:Rose Of Kali is the one who really oversees the armor galleries project, so you should probably ask her for a final opinion. Personally, I find post-processing effects to be annoying because they create a huge glare spot on the armor that washes out the color/details in that area.  You could avoid that by turning the character away from the sun, but then you have the opposite problem of everything being dark and washed out.  Lack of anti-aliasing is also a bit of a bother, leaving jagged edges around the character that are kinda distracting.  So I always recommend turning PP off and setting AA to 4x.  &mdash;Dr Ishmael Diablo_the_chicken.gif 16:05, 20 December 2010 (UTC)
 * Also, see here. &mdash;Dr Ishmael Diablo_the_chicken.gif 16:06, 20 December 2010 (UTC)

ConfirmEdit
Hey doc, aren't we supposed to have that installed/running? --JonTheMon 15:12, 23 December 2010 (UTC)


 * No, mendel said it would "tone down the appeal of the wiki" by "discouraging anon edits," so we didn't have it installed. I'll push it to the repository, hopefully Bryan will check in today so we can get it pushed live.  &mdash;Dr Ishmael Diablo_the_chicken.gif 15:42, 23 December 2010 (UTC)


 * Think that's going to stop the spammers/vandals much? Or rather stop anon edits? I know that on minor changes, if I'd run into those, I'd say "sod it" more often than not. --◄mendel► 15:43, 23 December 2010 (UTC)
 * At the very least, confirm edit can kick into gear for things like urls for anons. --JonTheMon 15:50, 23 December 2010 (UTC)


 * ConfirmEdit can be configured - we've already had this discussion. &mdash;Dr Ishmael Diablo_the_chicken.gif 15:57, 23 December 2010 (UTC)


 * I'm actually going to go with the reCAPTCHA extension, which is the same thing (it includes the ConfirmEdit code and simply builds on it) with a much stronger captcha. Bots could easily recognize and respond to plain-text math questions, which is the default in ConfirmEdit.  The other options in ConfirmEdit mostly require additional server-side configuration, which we should avoid.
 * reCAPTCHA uses the same trigger settings as ConfirmEdit, and the defaults in the current version are as follows:

$wgCaptchaTriggers['edit']         = false; // Would check on every edit $wgCaptchaTriggers['create']       = false; // Check on page creation. $wgCaptchaTriggers['sendemail']    = false; // Special:Emailuser $wgCaptchaTriggers['addurl']       = true;  // Check on edits that add URLs $wgCaptchaTriggers['createaccount'] = true; // Special:Userlogin&type=signup $wgCaptchaTriggers['badlogin']     = true;  // Special:Userlogin after failure


 * I don't see any reason to change these. Also, I changed group permissions for Users and (all) to remove the writeapi permission, since vandal-bots could easily use that vector to bypass all our other protection mechanisms.  &mdash;Dr Ishmael Diablo_the_chicken.gif 18:02, 23 December 2010 (UTC)
 * Which groups should the captcha trigger for? By default I believe it's anons, new users and auto-confirmed. --JonTheMon 18:06, 23 December 2010 (UTC)


 * I'm setting it for anons only. We trust our registered users (and they're easier to block).  &mdash;Dr Ishmael Diablo_the_chicken.gif 18:07, 23 December 2010 (UTC)


 * I just wonder if it'd help to have captcha true on say page creation and edits... Well, would that help against vandalisms and at least autobots? Ariyen 18:08, 23 December 2010 (UTC)


 * Take that up with mendel, he doesn't want to scare away potential editors. &mdash;Dr Ishmael Diablo_the_chicken.gif 18:11, 23 December 2010 (UTC)


 * Speaking as a potential editor of other sites:
 * I am 5% less likely to contribute the occasional edit to a site that requires confirmation (that goes up to 10% if CAPTCHA is the requirement rather than 4+5=...).
 * I am 1% more likely to register as a user for the same site if I find myself contributing more than X edits in Y weeks.
 * I am 70% less likely to contribute to the same site if I perceive it to be unable to handle vandalism.
 * So, while I agree with Mendel that we should err on the side of openness for anons, I don't think that adding a minor hurdle is going to scare aware well-intentioned folks. — Tennessee Ernie Ford ( TEF ) 19:51, 23 December 2010 (UTC)