User talk:Dr ishmael/extensions

Comments
I never liked the RSS widget, mainly because it doesn't really leave data on the wiki.

I'd like to add mw:Extension:Widgets and then replace our video and RSS extensions with widgets for them, that's a more flexible solution. (See http://www.mediawikiwidgets.org/Main_Page ). It might even be possible to make skill bars a widget.

Do we need the &lt;verbatim> tag? It*'s not standard, but I think the widgets would work as well.

Revision delete needs to be enabled, and assigned to bureaucrats. We'd also want to have the CheckUser extension, and maybe some spam fighting extensions (rangeblock? title blacklist? content blacklist?)

I don't know about Special:EditCount.

I would also love to have mw:Extension:OpenID, if every wiki had it it would make using multiple wikis hosted differently much easier.

Then there's the code for Wikia account verfication that Derik came up with.

-- ◄mendel► 23:56, October 14, 2010 (UTC)


 * You said you wanted a list of extensions we use, not extensions you think would be nice to have. >.> Why did I even bother doing this then.....
 * Oh, something's been bugging me - on IRC, you first said you didn't know which extension &lt;verbatim> was coming from... then when I pointed it out on Wikia's SVN, you said you'd already downloaded it earlier today. Huh?  &mdash;Dr Ishmael Diablo_the_chicken.gif 00:59, October 15, 2010 (UTC)
 * No, I pulled a complete release branch - 50,000 files. I just made the connection at the time that because of that, I do have the file locally (and could have searched for it).
 * What we need is not a list of extensions we use, but rather of the ones we want to install on the forked wiki. There's of course considerable overlap. ;-P Some of the extensions we are using won't be coming with us, most likely. -- ◄mendel► 02:22, October 15, 2010 (UTC)


 * Oh, that's what you meant. IRC was all fast'n'furious at that point, it's no wonder I misunderstood.
 * For the most part, we do need the extensions that provide direct functionality on pages, because without them, those pages will break. Thus, we would want to install all of them.  (Not all the ones currently listed fall under this, of course - CheckUser, DissmissableSiteNotice, and Editcount, for example.)
 * Since we will be getting shell access, allowing us to install extensions whenever we want, I thought it would be easier to simply get the extensions we need installed off the bat, then we can add stuff from our "wishlist" later. &mdash;Dr Ishmael Diablo_the_chicken.gif 02:43, October 15, 2010 (UTC)


 * Of course, if you just want to talk wishlist, that's fine. I've got a few of my own.
 * The Semantic Bundle includes a number that would be very useful, and not just for SMW. It includes ParserFunctions, which we'll already have, as well as Widgets.  Other ones I like:
 * Extension:Admin Links - would replace the "command center" I currently have in the sidebar (function add_bar in my monobook.js)
 * Extension:ArrayExtension - yet another option for performing complex calculations in templates (but based on your reaction to VariablesExtension, you probably won't like this either)
 * Extension:Semantic Drilldown - was planning on requesting it here, this will allow users to build their own "categories" using our semantic-aware pages
 * Extension:Semantic Result Formats - I want this specifically for the 'outline' format, which would make Nick's location checklist very easy to build
 * Extension:Semantic Internal Objects - an alternative to using Type:Record for semantic properties, this would allow us to store multi-valued data points for articles, e.g. how much of which material is required to craft something, or how many of which trophy does a collector collect
 * Extension:RegexParserFunctions - can't recall any specifics now, of course, but I know there have been times where I've been frustrated that the standard ParserFunctions can't do regex
 * Extension:TitleBlacklist - might be a useful companion to SpamBlacklist (which I added to the main list; it's not on Special:Version for some reason)
 * Extension:ConfirmEdit - I didn't include this on the main list since it's not used directly, but it is enabled here, and I'm sure it helps cut down on a lot of spam
 * OpenID is also a good idea. &mdash;Dr Ishmael Diablo_the_chicken.gif 04:29, October 15, 2010 (UTC)
 * Using the Semantic Bundle makes a lot of sense, since that simplies installing and maintaining those extensions in the bundle somewhat. I'd prefer installing that right off to installing the extensions separately and switching over later. I do know that arrays can be useful as data structures when working with SMW.
 * I agree that title blacklist could come in useful (maybe just put some russian characters in there for a start?); I'm less confident about ConfirmEdit since it discourages anon edits, and thus tones down the appeal of the wiki. (We'd have to see how much spambots we'd get without it, and whether there are better ways to handle them. Ideally, there should be an extension that puts up a captcha when an anon tries to edit a half-protected page.) With the RegEx and all that SMW stuff we'll have to monitor server performance closely. -- ◄mendel► 12:51, October 15, 2010 (UTC)


 * "russian characters" -> exactly what I was thinking. :) &mdash;Dr Ishmael Diablo_the_chicken.gif 13:33, October 15, 2010 (UTC)


 * I believe you can tweak confirmedit to only trigger on certain edits, like adding links. --JonTheMon 14:02, October 15, 2010 (UTC)


 * Yes, you can set  for that.  That's on by default, and the other default settings trigger when creating an account and after 3 failed login attempts.  The 'edit' trigger, which captcha's on everything, is off by default.  You can also configure specific user groups to always skip captcha.
 * It shouldn't be too hard to add a new setting to make it trigger whenever a page is protected. &mdash;Dr Ishmael Diablo_the_chicken.gif 15:12, October 15, 2010 (UTC)