Posts Tagged mediawiki

MediaWiki’s new discussion system in testing on Wikimedia Labs

I’m very excited to announce that LiquidThreads, the next-generation discussion system that I’ve spent the last few months developing for the Wikimedia Foundation, is now in beta testing on liquidthreads.labs.wikimedia.org.

Sample of the LiquidThreads interface

Sample of the LiquidThreads interface

Read the rest of this entry »

, , ,

3 Comments

Improving Wikimedia’s Discussion System

Hi all,

Some of you might have already seen my blog posts about LiquidThreads, Wikimedia’s in-development discussion system.

For those who haven’t, this is a quick primer on what LiquidThreads is, and what it’s going to do for Wikimedia’s communities.

Currently, Wikimedia’s discussion system sucks. Here’s why:

  • It’s not easily usable by the average user. It isn’t obvious how to leave a comment on a talk page, or how to reply to a comment. The indenting we use now is ad-hoc and unsustainable for long discussions.
  • Signatures are done manually and we have to jump on poor unsuspecting newbies who don’t know this (or write bots…)
  • Archiving is done unevenly by bots, which are maintained by users and therefore of very uneven quality. Archives are something of a black hole — they aren’t searchable, easily maintainable or easily accessible. You can’t resurrect an archived discussion easily, nor can you view its history.
  • It’s stored as plain wikitext, which is opaque to any sort of automated process.
  • You can’t move a thread to a different discussion page and preserve its history.
  • There’s no encouragement, mechanism or incentive for quoted, point by point inline replies like we’re all used to with e-mail.
Imagine being a new user and trying to figure out how to add your comment to this.

Imagine being a new user and trying to figure out how to add your comment to this.

Enter LiquidThreads. LiquidThreads is a system that makes MediaWiki’s discussion system behave like a forum or comments thread, while still maintaining the unique refinements that make wikis work. It was originally designed by a Google Summer of Code student, David McCabe, and I’ve been making incremental improvements to make it work for Wikimedia.

Overview of the new LiquidThreads interface

Overview of the new LiquidThreads interface

So, what’s changed?

  • Comments are separated from each other in the wikitext, so there are no more edit conflicts in discussions, and the usability is vastly improved.
  • Instead of indenting, each comment is in its own box, along with its replies. It makes it much easier to follow each post and its replies, and it’s much nicer on the horizontal whitespace. Hopefully, it will be the death of the ‘arbitrary section break’!
  • Each post has its own history page, making it easy to see what’s going on with individual threads without trying to navigate the history of a whole page.
  • It’s easy to move threads between pages, preserving the page history.
  • Discussions  are never ‘archived’. Instead, older discussions fall to the bottom of the page, and eventually they drop off entirely, to hit a new page. If you missed the chance to have your say, just reply to a discussion and it’ll be bumped right up to the top of the page again!
  • Discussions with recent changes are at the top of the page. Discussions that have fallen dormant fall to the bottom. It’s easy to find out what’s happening!
  • You can watch individual threads of a discussion, and even get an email when they’re replied to.
  • It’s easy to link to a discussion, and the links are permanent unless the discussion is deleted. There’s no need to point to an archive or to an old revision ID.

If you’re interested, I’ve put together a test setup for you to play with it.

As always, questions, comments and suggestions are more than welcome, in the comments or elsewhere.

, , ,

8 Comments

First usability release, Acai, is now available.

Screenshot-Editing July 1 Wikipedia

The first usability release, Acai, hit Wikipedia and sister projects this afternoon. The new skin, Vector, and the enhanced toolbar can be turned on from the user preference under “Appearance” and “Editing”. Search result page now has a new layout with less daunting information. Vector is only available for left-to-right languages at a moment due to IE6 incompatibility. However, the enhanced toolbar can be selected from all languages and the new search result page is enabled globally. We could not roll out two features we had planned. First, warning messages for unsaved changes when a user switches away from the edit tab did not work properly thus they are disabled. So please be careful when you switch away from the edit tab. Secondly importing language specific configuration for special characters were not graceful, so we disabled special character function from the toolbar. We are working on the fixes and plan to roll them out as soon as we have stable solutions. The usability project wiki has Vector and the new toolbar as a default, so if you prefer to check them out without changing your preferences it is a good place to visit first. Let us know what you think. We would love to hear from you.

Best,

Naoko

, ,

No Comments

First usability release is coming up soon.

Screenshot of enhanced toolbar

Screenshot of enhanced toolbar

I am happy to announce that the first set of usability improvements is scheduled to be integrated in MediaWiki and will be enabled as one of user preferences in Wikipedia in the first week of July. The nickname for this release is called Acai. The release names will follow the names of tropical fruits in alphabetical order. The description of features are found in this release page. The major improvements are; 1) reorganized tabs which clearly indicates the state of “Read” and “Edit”, 2) enhanced edit toolbar which is expandable based on users’ needs, 3) search result page which hides the clutter and make search results more visible, and etc. We are still combating with IE6 bugs , but come and play with the prototypes and let us know your feedback. On the localization front, we have introduced a set of new texts for localization. If you are a MediaWiki translator, your collaboration on localization is greatly appreciated as always.

Naoko Komura

Wikipedia Usability Initiative

, ,

3 Comments

Chinese-language search fixes for MediaWiki

Search is an important part of any web app like a wiki, but search is harder than it looks — especially in a multilingual environment.  MediaWiki has to support not just your standard Western languages like English and Spanish, but many more with special requirements:

  • Some can be written in multiple scripts (such as Serbian in Cyrillic or Latin), and searches should match text written either way.
  • Some languages don’t use word spacing, like Chinese and Japanese. To let the search index know where word boundaries are, we have to internally insert spaces between some characters:

维基百科 -> 维 基 百 科

Then to add insult to injury, we need to fudge the Unicode characters to ensure things work reliably with older and newer versions of MySQL:

维 基 百 科 -> u8e7bbb4 u8e59fba u8e799be u8e7a791

For a long time, this word segmentation wasn’t being handled correctly for Chinese in our default MySQL search backend, so searching for a multi-character word often gave false matches where the characters were all present, but not together.

This is now fixed for MediaWiki 1.16; the intermediate query representation passed to the search backend now internally treats your multi-character Chinese input as a phrase, which will only match actual adjacent characters:

维基百科 -> +”u8e7bbb4 u8e59fba u8e799be u8e7a791″

Note that Wikimedia’s sites such as Wikipedia run on a fancier, but more demanding, search backend with a separate Java-based engine built around Apache Lucene. Sometimes we have to remind ourselves that third-party users will mostly be using the MySQL-based default, and oh boy it still needs some lovin’! :)

, , , ,

No Comments

The Wikipedia Usability Initiative is still hiring.

The Wikipedia Usability Initiative has extended the application deadline for the Software Developer position till May 30th. We are recruiting two candidates for this position. Both local applicants to the San Francisco Bay Area and remote applicants are encouraged to apply. Please help spread the word.

http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(project)

Naoko Komura
Wikipedia Usability Initiative

, ,

No Comments