Tuesday, August 28, 2012

The need for both #OpenID and #OAuth

Many words have been used on the merits of OpenID and OAuth. There are many misconceptions and many of those have everything to do with perspective. In order to get a better understanding I asked on the Wikitech mailinglist a use case for OAuth. The answer I received helps.
OpenID is an identity management system. It allows users to authenticate to one site using another site as their identity. A use case for this is, for example, using your Facebook account to log in to Wikipedia. This may be useful, as it would allow users to more easily register for Wikipedia
OAuth is a third-party authentication and authorization system that allows outside applications to do stuff on behalf of a user. The reason for this is because currently toolserver applications, etc. authenticate to Wikipedia using a plaintext username and password, which is extremely insecure for a number of reasons I will not elaborate on here.
When you read the answer, there are some observations to make. The most obvious is how do you assure that the software that is to use OAuth will be secure. Given the power of many Toolserver tools how do you make sure that only trusted people make use of the Toolserver functionality.

Enter OpenID, it does provide identity management. OpenID is able to provide more information than just "this is indeed the indicated identity" as part of the "OpenID Attribute Exchange". When the Wikimedia Foundation implements OpenID as a service, it will be possible to identify the users that have a "bot flag" on the user profile. 

As it is, the Toolserver tools are not necessarily secure. With OAuth it will become even less secure to run the software because it will be the software itself that includes the authorisation to run, never mind its configuration, never mind how it is used or by whom. When OpenID authenticates users, it becomes possible to ensure that only people with a bot flag can run Toolserver software on the production Wikimedia projects.

To make the use of the Toolserver tools secure, it is necessary to complement OAuth with OpenID. Oauth in isolation will make the Toolserver tools easier to use but it does not make them more secure to run.
Thanks,
      GerardM

Thursday, August 23, 2012

#Wikimedia Commons, a relevant history

A long long time ago when Commons the wiki was created, it was only a dream. The dream was to have one place where all the images could be shared freely among all the Wikimedia Foundation projects.

It was a dream with really practical implications. At that time sharing a picture meant uploading the same picture to another wiki. At that time removing a picture because of a copyright violation was removing it on one wiki and perhaps on one or more wikis as well. This was an inexact process with inadequate results. The dream of Commons was to store a file once and use it on any wiki. The dream of Commons was that administrative procedures would be significantly enhanced because everything could be done once and everything could be done right.

Commons was created and it took several months before pictures on Commons were available on the WMF projects.

Today Commons fulfils much of this promise. Media files are shared on all the WMF projects, you can even enable this functionality on external MediaWiki wikis. Most of the duplicate files have been deleted and a single copy only exist on Commons. Nowadays the administrative procedures are much more effective. Everybody involved in Commons will agree it is not perfect, far from it but, Commons is thriving nonetheless.

This notion of adventure that existed in the Wikimedia Foundation seems dead. I am convinced it should be revived. There are some signs that it is possible ... in things like moving towards agile development ...

More later
Thanks,
     GerardM

Tuesday, August 21, 2012

a #threat assessment for #Wikipedia

The people who take care of mail send to Wikipedia are often informed that Wikipedia is not secure; "everybody can edit Wikipedia". This is actually intentional because Wikipedia is the encyclopaedia that everybody can edit. The real risk is when people do not recognise they are invited to edit. This is a genuine issue and it is something that receives a lot of attention.

When you consider security for Wikipedia, the people most at risk are its editors. There are several threats they are exposed to. Several of these are issues computer security can deal with.
  • threat to the anonymity of a registered user
  • threat to user credentials
When the potential threats are evaluated, it is important to realise that the severity of these threats is not obvious. It matters considerably where you reside, what your ethnicity is or what your belief system is. It is important to minimise any threats because once people no longer feel free to contribute it will damage the "neutral point of view" that gives Wikipedia much of its relevance.

With the implementation of SSH it has become considerably more difficult to learn what a person is doing when working on Wikipedia. This has been a real improvement. However, user credentials and particularly passwords are considered not really secure. Read for instance what Wired had to say about them. It is explained that improvements can only be expected when changing the infrastructure of online security. This will probably do a whole lot more good than lecturing people about how they should change their behaviour.

The question is if the WMF is open for such considerations. So far the talk is about "Nascar" ?!?! to me this sounds remarkably like bikeshedding and is very much beside the point.
Thanks,
     GerardM

Monday, August 20, 2012

#OpenID for the USERS of #Wikipedia, PLEASE


Again a discussion about the use of OpenID for the Wikimedia projects flared up. From my perspective the one perspective missing is the one of a computer user who is fed up with the failed security that is provided by passwords.

The problem is that systemmanagers only consider security in isolation. It is the solution that is to be adopted for their system or systems. Obviously in a perfect world, a user will have a separate password for each website or program. The world is not perfect and most people use one or a few passwords for everything. The world is not perfect and passwords of many big websites have been uncovered by hackers. Consequently many passwords used by Wikimedia contributors can easily be guessed by the bad guy who are in the know.

The problem with passwords for a user is that they are unmanageable. Too many systems and websites, too many interfaces seriously impact the security wherever passwords are implemented to provide security. It is theatre and the fool is the part you have to play.

OpenID provides a serious alternative. It allows for a single place with a single password that authenticates to any and all websites and services that accept security in this way.  It is a serious alternative as long as any and all accept other OpenID. It will be really welcome when the WMF considers security for its 456 M users. It is obvious that a large percentage also frequent websites like LinkedIn and solidify the argument to implement OpenID.
Thanks,
     Gerard

Sunday, August 19, 2012

#Font support by #Google and #Wikimedia

The quality of the Amiri font has been recognised by the Wikimedia Foundation for some time; it has been provided in the Web Fonts extensionn for some time and recently in an other bit of "read the whole article to get to the good news" it became part of a Wikimedia supported jQuery library for web fonts.

Google has also recognised the Amiri font; they make Amiri available through their "early access" program. Google supports multiple (freely licensed) Arabic fonts as web fonts. The biggest difference for me between the two programs is that the WMF library has your server provide the fonts while the Google offering has the fonts provided through the Google infrastructure.

Both Google and WMF support fonts for many scripts. The question is what they will do when the font has technical requirements that are more than usual.

Recently the Tuladha Jejeg font for the Javanese script was given a free license and the Wikimedia Foundation will assess if they will include it in their Web fontd extension. There may be a technical problem; it makes use of the SIL Graphite technology. The question is to what extend do browsers support this technology.

When Google is serious in supporting the rare scripts, the opportunity to support the Javanese script through the Tuladha Jejeg font may be reason enough to put some extra effort in enabling support for SIL Graphite.

<grin> One may hope for Google to do more good, we know they can</grin> <seriously> For the WMF there is hardly another option when they are to support Javanese </seriously>
Thanks,
      GerardM

#Internationalisation is more than conversion of numbers

A friend read my last blogpost and pointed me to a recent presentation about the current best of breed internationalisation for JavaScript. He had been testing the new jQuery internationalisation library published by the Wikimedia Foundation and was astonished that the one thing "everybody" does was missing.

His question was: "where is the conversion of numbers and dates?". Obviously MediaWiki "does" the conversion of numbers and dates, it is just not part of the library that enables what is most crucial for us in Internationalisation; the translation of the messages in more than 280+ languages.

My friend Andrew was thinking of extending the library with the conversion of numbers and dates. It makes sense to have them included however, forking this really new library at this early time is "evilish". Talking to Santhosh, the developer of this library is the thing to do. It is, because in this way any future improvements in the existing 280+ languages or the missing 6000+ languages will be shared by anyone who updates to this library.

YES, I know jQuery is Java and not JavaScript. But I also know that my friends at the Wikimedia Foundation support the localisation of their JavaScript.
Thanks,
      GerardM

Friday, August 17, 2012

#jQuery and #Internationalisation of YOUR application

There has been a lot of good news about jQuery this week.
The news of this jquery.i18n library is wonderful news. As it is the same software as used for the internationalisation of MediaWiki, it represents the current knowledge of the 280+ languages that have their Wikipedia.

When your software is open source and when you adopt this library to implement internationalisation, you are that much closer to make use of that wonderful community at translatewiki.net. They are already doing a great job for many applications, why not yours?
Thanks,
      GerardM

Wednesday, August 01, 2012

Learning to type #Arabic; #Wikisource exercises

The one skill that makes it easy to use a computer is typing with ten fingers. Particularly when you learn a new script, you need to learn to type again. Learning this skill well means exercises.

I remember when I learned to type on a typing machine that I hated the futility of these exercises. Now that I need the skills to learn Arabic, I can think of exercises that are of use to everyone.

The WIKISOURCE for the Arabic language.

All Wikisources have the ProofreadPage extension installed. So all that is needed to tap in the vast pool of people that are learning to type Arabic is having pages ready using this tool.

My skill in Arabic is such that I can not easily find these. When I have, the Arabic Wikisource has its first volunteer that will exercise and do good at the same time.
Thanks,
     GerardM

Tuesday, July 31, 2012

Learning a new #script .. #Arabic

As I am learning a new language with a script that is new to me, I find the Internet not yet the resource it is in languages for the Latin script.

There are several obstacles; I have to configure my computing devices for the Arabic script and keyboard. I have to find the characters on my keyboard and only when I do will I get the facility that I need.

The one thing that would make my day is to have a typing tutor that is ready for an international public. This means that the instructions are available in multiple languages for the same input method for the same language. When these parts are separated from the code, there are three specific parts.
  • the user interface
  • the exercises
  • the input method or keyboard layout itself
This allows the same software to be used for multiple input methods and scripts / languages. The software can be localised at translatewiki.net and the typing tutor can be distributed with the input methods themselves. 
Thanks,
      GerardM

Wednesday, July 25, 2012

Multilingual cluefull bots


The #BBC writes that #Wikipedia without its bots is doomed. It is a good story, a happy story and well worth a read. Wikipedia as you know is not only the English language Wikipedia, there are over 280 Wikipedias in different languages. They are not all created equal; most of the smaller Wikipedias have less than 100.000 articles, a small community of editors and their own issues with people who think it funny to write penis wherever they can.

The BBC article writes about "Cluebot NG" and is said to reside on a computer somewhere. It would be a great project to move Cluebot NG to a Wikimedia server and make instances for all the other languages. First for the 40 something languages with more than 100.000 articles and when its lessons are learned there may be scope to expand.

There is a committee supervising the bot activities, it will be wonderful when it has the potential to expand its expertise as widely as possible.
Thanks,
       GerardM

Tuesday, July 24, 2012

Levels of competence for #Arabic in #Wikipedia III

Tools like #Google #Chrome use an engine to do the rendering for them. For Chrome it is Webkit. It is responsible to connect two items that are in separate HTML elements and make sure that the rules for the Arabic script are addressed.

What started as an observation in MediaWiki became a Chrome bug and is now a Webkit bug.

Webkit is used in multiple browsers.. This makes a fix relevant for Apple's Safari browser as well. The one question left is what will it take to bring a fix in production within those browsers in the near future.
Thanks,
       GerardM

Sunday, July 22, 2012

Levels of competence for #Arabic in #Wikipedia II

It does matter what browser you use. Google's Chrome browser is the reason why the Arabic Babel templates.

If you use Chrome to browse Arabic websites, you want to add your vote to fix this bug. You vote by marking the star that is at the bottom of the page.

I am really pleased how quickly this issue was analysed. It is now for Google to support its users who use languages in the Arabic script.
Thanks,
      GerardM

Levels of competence for #Arabic in #Wikipedia

As my competence in the Arabic language is growing, I added Arabic in my Babel information. To my amazement what I read is wrong. The "ba" is written on its own while it should be connected with the following "aliph". It is one of those peculiarities of the Arabic script that a character like the "ba" is expressed depending on its position in a word.

I had a look at translatewiki.net to understand why it is wrong; as you can see the "ba" or Ø¨ is 
connected to a wiki link and the word is not formatted after what is in the variable.

It is fun to learn other languages. What is really amazing is that I can find glaring issues like this one.
Thanks,
     GerardM

Thursday, July 19, 2012

European cranes want to be free

  

This wonderful video of European crane courtship is currently copyrighted and not freely licensed. The video comes with a button that allows you to embed it in a website and its article has a button where you can order the video.

The video is on the website of Stichting Natuurbeelden and they made a nice offer; 50 of their videos will become available under the CC-by-sa license. There are many great videos to choose from and for all kinds of reasons, the initial offering is to choose at most 50 of them. 

Organising this selection will not be easy and the relevance of some videos is very much in the context of nature in the Netherlands. European cranes are breeding again in the last few years. When the fifty videos are selected and when they are used in our projects, these videos will be seen quite often. At the moment when I write this, the number of views for this video is only 136.
Thanks,
     GerardM

Saturday, July 14, 2012

Can everybody read #Wikipedia?

A lot of effort goes into making "Wikipedia the encyclopaedia everybody can edit". The result is wonderful; there are Wikipedias in over 280 languages, a big effort is under way to make editing even easier and as so many people do edit, it became a rich almost authoritative resource. When Wikipedia goes off-line, students despair.

People do read Wikipedia, it is very popular but the notion that Wikipedia is hard to read is not really considered. Take for instance today's featured article.There are too many words on a line. For many people this makes it hard to read, some give up on an article or on Wikipedia.

Yes, you can change the way content is displayed on a computer screen. The problem is that people who have problems read websites in the default format.


The Wikimedia Foundation does have the expertise to consider these issues. The people who do have already too much on their plate to support the current software development. However, the proof of the pudding that is Wikipedia is in people READING its content and that makes this a key concern.
Thanks,
       GerardM

Tuesday, July 10, 2012

Something positive to say about #Apple

Apple is innovative, it routinely adds new functionality and quality to its products. Many people love Apple products and pay a healthy premium for the latest and greatest.

One of the recent innovations goes by the name of "retina display". It is a high resolution screen of such quality that the human eye does no longer see individual pixels. Innovations like the retina display add demand for high quality images and, it does stimulate the use of high quality images and the use of SVG or scalable vector graphics in WMF projects like Commons and Wikipedia.

The improved technology used in Apple hardware stimulates quality improvements at content providers. In this way Apple stimulates a healthy and innovating content ecosystem. As other hardware suppliers are continuously catching up with the leader of the pack, there is real value in buying Apple.

I did  it, nothing negative to read in this post about Apple.
Thanks,
        GerardM

#GLAM - About recognition

 Left Hand Bear, Oglala chief
This years #Commons picture of the year contest was different from last years. The many old images that were so lovingly restored and featured the Commons main page were not there any more.

A thread on the mailing list reminded me about all the hard work that gives images of the past a new lease of life. The image of Left Hand Bear, the Oglala chief is used a lot. As you can see below it is even used to make ties, mugs and buttons.

The image of Left Hand Bear has been lovingly restored by Adam Cuerden. The original of this image is at the Library of Congress and I owe a debt of gratitude to both Adam and the LoC.

Adam restored an image preserved at the Library of Congress. Knowing this, I am sure that this is indeed an image of Left Hand Bear. The image is obviously in the public domain and as such I am not required to acknowledge either the LoC or Adam. I may put the image on mugs, ties and buttons and sell them.

For both Commons and Wikipedia, acknowledging the LoC and Adam bring important benefits. Acknowledging the LoC provides provenance of the image, this is the equivalent of providing a source to a fact. Acknowledging Adam links the much improved image to the original. It recognises Adam for his work.

Acknowledging the LoC and Adam IS a best practice. It is a best practice promoted by organisations like Europeana. It is a best practice that is not a requirement, it is however something that we should aspire to.
Thanks,
      GerardM

Monday, July 02, 2012

#Kiwix - the interview

#Kiwix is the tool that allows you to read the content of a Wiki offline. It has been developed with Wikipedia in mind but is equally usable for Wikisource or Wikibooks. I am really happy to have interviewed Emmanuel who knows all the ins and outs of this wonderful piece of software.
Thanks,
     GerardM


What is Kiwix and what is it used for
Kiwix is a software that wants to enable people to read Web contents without internet connection. It's a reader which works with ZIM files containing all the content. It's used to access Wikipedia offline, by reading pre-packaged Wikipedia ZIM files. It's mainly used by people who want to have an encyclopedia, but are too poor to have access to the internet. It's also used,for example, by travelling people (plane, ship, train), prisoners and students at school. 

Can you tell us something about its popularity
We have users all over the world and the audience is increasing quickly: we have had 25.000 downloads of Kiwix in May. 

In how many languages is Kiwix supported 
Thank to the Translatewiki Web site andits community, Kiwix is localised in more than 80 languages. We also provide content (ZIM files), mainly Wikipedia, in around 25 languages. But we want to do more: thanks to a grant of WMCH soon we will offer ZIM files of Wikipedia in all languages. 

How do you support languages written in scripts like Malayalam, or Tibetan
Contents are Web contents and Kiwix itself is a sort of browser getting the Web pages from the ZIM file instead of the Web. So, we do not have special handling in Kiwix itself to render the contents. Everything should be well organised in the ZIM file, for example by using Web fonts. But, from the Kiwix fulltext search engine point of view, this is challenging. Natural languages have a lot of particularities. Kiwix uses the Xapian search engine and tries to integrate CLucene. We do our best with them to offer the smoothest user experience possible. 

Do you provide fonts with Kiwix for the languages that use these scripts
The Wikipedia ZIM files we are preparing still do not provide the Web fonts. Already for a few months, the integration of Web fonts has been a part of the Wikimedia projects, so we have to fix that ASAP, this is not a big challenge.

For some languages like Chinese and Serbian, we show the content in two scripts ... Can Kiwix do this as well ?
Kiwix does not provide any transliteration tool for now, but all the technology is already there in the soft. We use a powerful unicode library called ICU (http://site.icu-project.org/) which can do that. We
want to use it to allow users to do custom transliterations. C++ developer wanted there!

Kiwix uses the OpenZIM format ... can you tell us more about this format
The format is called ZIM. There is a volunteer driven project called openZIM  created a few years ago to specify the format and develop a standard library. The ZIM format allows to put millions of contents together, to compress a part of them, and add Metadata. In the end, you get only one file, which is, at the same time, extremely compressed and allows a constant and quick random access.

Nowadays, many publications are in the EPUB standard ... can Kiwix handle this as well
Kiwix is not able to deal with EPUB, but in the future it will. We think EPUB & ZIM format are complementary and we want Kiwix being able to perfectly deal with EPUB. Our plan is to integrate "Monocle" to do that. Also there, developers are wanted.

How do people find content available for Kiwix
Kiwix has its own content manager, so you can download content from Kiwix itself. But you may also download the ZIM file from the Kiwix Web site (http://www.kiwix.org) or using the Mediawiki Collection extension.


In the future, we want to have a platform (something like Itunes) to offer  really easy to find and download contents (both ZIM and EPUB files). We have started a project in that perspective. We need your support! 

What is your biggest challenge at this moment in time with Kiwix
Building Kiwix-mobile for Android. We will have a first release in autumn. But we have many other projects running at the same time and others for which we still need volunteers.

Thank you
Emmanuel

Saturday, June 30, 2012

#ImpactOCR - Digital publications and the national libraries

According to the #ISBN standard, the "format/means of delivery are irrelevant in deciding whether a product requires an ISBN". However, it is often assumed that a publication requiring an ISBN number is a commercial publication. In the USA and the UK for instance you have to buy your ISBN number or bar code while in Canada they are free because Canada stimulates Canadian culture.

When a standard is not universally applied, it loses application. When all publications are not registered a national library will have to maintain its own system when it is to collect a copy of all publications. As a result the ISBN is dysfunctional as a standard because it does not function as a standard.

When the Wikisourcerers finish the transliteration of a book, it deserves an ISBN number and, national libraries should be aware of these publications. This recognises and registered the work done in the Open Content world. When these books are registered, all the Open Content projects may know that they can concentrate on another book or source.

As the ISBN does not register all publications, it does not do what it is expected to do; function as a standard. 
Thanks,
       GerardM

Friday, June 29, 2012

Learning another language II

Learning to vocalise #Arabic can be done on the Internet. There are websites like Mount Hira where you find Arabic to the right, a transliteration to the left with an explanation in English underneath. What really helps is that you can listen to the recitation of a surah by line.

It is great but there is room for improvement. Improvement that can happen at Mount Hira but also at a Wikisource.
  • Show all the text as text and not as graphics
  • Allow for the Arabic text to be shown in fonts representing different writing styles
  • Allow for the explanations to be shown in a language that can be selected
Learning to vocalise what you read is one use case, learning Arabic is another and learning the Koran is a third. Wikisource has the potential to be a place for all three objectives.

There are always people who are interested in reading the source documents about a religion, any religion. The great thing of Wikisource is that you can include the wikilinks explaining the terms that are ambiguous or obscure.

Typically these source documents are readily available and out of copyright. Including them in Wikisource will gain it more public. Wikisource is an obvious place because it has a reputation to keep up; the reputation that original documents are original.
Thanks,
       GerardM