Showing posts with label mobile. Show all posts
Showing posts with label mobile. Show all posts
Saturday, May 09, 2015
#Reasonator on #mobile
Reasonator has been for a long time the only way to get information out of Wikidata. Magnus decided to improve on it even more and for good reason; traffic from mobile phones is more and more relevant. The latest update makes Reasonator usable on a mobile.
What I like is that you can collapse sections of information so you can see only that part of the information that you care for. In the example I used the International Prize for Arabic Fiction and, I show the timeline prominently.. For the people who care about such thing, there is a winner for 2015.
Thanks,
GerardM
Monday, April 27, 2015
#Google - thank you for pushing #mobile #phone support
Putting your money where your mouth is is a wonderful thing. Google just did that again. Not by serving notice that support for mobile phones is important but by giving it teeth.
Recently it did it with Fi. A new product that will shake up an industry.
From now those websites that are not providing proper support for mobile phones are out of luck. Google does it where it hurts them most; it is in their ranking.
When you "google" (the verb), you will see those web sites first that are ranked the highest. Websites that do not function properly on mobile phones will go the way of the dodo as their ranking will plummet; they will not get the same results and providing quality support for mobile phones is how damage may be repaired.
Wikipedia is said to have a problem here. It is not exactly a mobile friendly website. For that it has a special subdomain and, that does not count. So all the things we know that make life better for the one area where we are growing.
It is no longer a zero sum game. We will be hurt in our prime objective when we do not ensure that Wikipedia and all the sister projects. We rely heavily on the Google ranking. It is no longer a matter of personal preference and making noises to stop progress in its track. It is about the very essence of what we do: sharing in the sum of all knowledge.
It is great to know that our software is at a stage where it is quite good at supporting mobile phones. I am grateful for the forward thinking of the WMF to get us here. The next step is to bring it to all our projects and pages.
For old fogeys like me, we could have https://en.of.wikipedia.org so that we can live in our past.
Thanks,
GerardM
Recently it did it with Fi. A new product that will shake up an industry.
From now those websites that are not providing proper support for mobile phones are out of luck. Google does it where it hurts them most; it is in their ranking.
When you "google" (the verb), you will see those web sites first that are ranked the highest. Websites that do not function properly on mobile phones will go the way of the dodo as their ranking will plummet; they will not get the same results and providing quality support for mobile phones is how damage may be repaired.
Wikipedia is said to have a problem here. It is not exactly a mobile friendly website. For that it has a special subdomain and, that does not count. So all the things we know that make life better for the one area where we are growing.
It is no longer a zero sum game. We will be hurt in our prime objective when we do not ensure that Wikipedia and all the sister projects. We rely heavily on the Google ranking. It is no longer a matter of personal preference and making noises to stop progress in its track. It is about the very essence of what we do: sharing in the sum of all knowledge.
It is great to know that our software is at a stage where it is quite good at supporting mobile phones. I am grateful for the forward thinking of the WMF to get us here. The next step is to bring it to all our projects and pages.
For old fogeys like me, we could have https://en.of.wikipedia.org so that we can live in our past.
Thanks,
GerardM
Sunday, March 22, 2015
#Wikidata - Gaston's war
Gaston's war is a "1997 film" according to the automated description in Reasonator. At the time of the Wikimedia Foundation Metrics 3.5.2015 there was no description in English. Since then somebody added the description in English Hurray!!... Eh not really.
It is only Hurray, when you only care about English. In contrast the automated description was there already for most other languages. As relevant, when an item is updated with statements it may reflect in automated descriptions in all languages while a fixed description became stale maybe even wrong.
In the Metrics meeting it was mentioned that images might exist in the article.. Actually, Wikidata often has images where a Wikipedia article has not.
PS there is an API to create the automated description.. Why not use it?
Thanks,
GerardM
It is only Hurray, when you only care about English. In contrast the automated description was there already for most other languages. As relevant, when an item is updated with statements it may reflect in automated descriptions in all languages while a fixed description became stale maybe even wrong.
In the Metrics meeting it was mentioned that images might exist in the article.. Actually, Wikidata often has images where a Wikipedia article has not.
PS there is an API to create the automated description.. Why not use it?
Thanks,
GerardM
Saturday, February 07, 2015
#Wikidata descriptions are not best of breed
In a Wikimedia mobile application they are going to use Wikidata descriptions. I really wonder why they did this because it is easy to recognise why it is substandard.
Take Mr Robert E. Hanson for instance. According to the description he is an "American politician", the description exists only in English and it does not recognise that he died.
Take Mrs Татьяна Михайловна Лебедева for instance; she died as well and there is not even a description.
At the same time there are descriptions available for both of them in any language based on the availability of statements and labels. For Mr Hansen it is "Amerikaans politicus (1947–2015) ♂" in Dutch and for Mrs Лебедева it is "Mens (1944–2015) ♀". These descriptions could easily have been in Arabic, Chinese, Zulu, Javanese or any of the other languages the WMF supports.
It has been obvious for a long time that descriptions are flawed and will not be useful in most languages supported by the WMF. It has been as well known that automated descriptions are more useful in more languages. The developers may have created a best of breed solution but it is still very much a dog.
Thanks,
GerardM
Take Mr Robert E. Hanson for instance. According to the description he is an "American politician", the description exists only in English and it does not recognise that he died.
Take Mrs Татьяна Михайловна Лебедева for instance; she died as well and there is not even a description.
At the same time there are descriptions available for both of them in any language based on the availability of statements and labels. For Mr Hansen it is "Amerikaans politicus (1947–2015) ♂" in Dutch and for Mrs Лебедева it is "Mens (1944–2015) ♀". These descriptions could easily have been in Arabic, Chinese, Zulu, Javanese or any of the other languages the WMF supports.
It has been obvious for a long time that descriptions are flawed and will not be useful in most languages supported by the WMF. It has been as well known that automated descriptions are more useful in more languages. The developers may have created a best of breed solution but it is still very much a dog.
Thanks,
GerardM
Friday, November 21, 2014
#Wikimedia - first #standardisation, then #specialisation
The hardware and software used by the Wikimedia Foundation is increasingly standardised. It uses the same software and the configuration is centrally maintained. Good news; it makes for a stable platform. A stable platform allows us to share in "the sum of all available knowledge".
With this process well under way, special attention can be given to special projects. It has probably escaped your attention that the WMF now has a "Services group". They are the engineers that support the standalone software components that often run on their own machines and have very specific jobs, such as "generate a PDF from this article".
Wonderful news. When it did not escape your attention, did you notice that Stas Malyshev is getting up to speed on the Wikidata Query Service[1], figuring out what we need to do to make it suitable for widespread deployment of WikiGrok[2])?
Effectively it means that Magnus's query tool will be used by an updated version of the Games [3]. Now is that not sweet; Wikidata data being USED to leverage our community to improve Wikidata even more.
Thanks,
GerardM
With this process well under way, special attention can be given to special projects. It has probably escaped your attention that the WMF now has a "Services group". They are the engineers that support the standalone software components that often run on their own machines and have very specific jobs, such as "generate a PDF from this article".
Wonderful news. When it did not escape your attention, did you notice that Stas Malyshev is getting up to speed on the Wikidata Query Service[1], figuring out what we need to do to make it suitable for widespread deployment of WikiGrok[2])?
Effectively it means that Magnus's query tool will be used by an updated version of the Games [3]. Now is that not sweet; Wikidata data being USED to leverage our community to improve Wikidata even more.
Thanks,
GerardM
Friday, April 18, 2014
#Reasonator - #Taxonomy, picture this
When you are are on a train, a bit bored, it helps when your railway company provides you with free Wifi, mine does. It is the perfect setting to add pictures of species to Wikidata. To do this the latest tool by Magnus is really good.
The "Wikidata species images on Commons" is the perfect companion for those idle moments. All you do is look at pictures and decide what pictures shows off a species best. When you do not like any of them, that is fine too. You also have the option to add range maps for a species.
The result of all this can be experienced in the Reasonator.
Thanks,
GerardM
The "Wikidata species images on Commons" is the perfect companion for those idle moments. All you do is look at pictures and decide what pictures shows off a species best. When you do not like any of them, that is fine too. You also have the option to add range maps for a species.
The result of all this can be experienced in the Reasonator.
Thanks,
GerardM
Friday, October 04, 2013
#Mobile, a #Wikimedia #investment paying off
To measure if a project executed by the Wikimedia Foundation is paying off, it is not the financials that are to be studied. For the WMF to be more successful, it has to increase its reach and bring more information to more people.
As more people are moving towards "mobile" devices, it is important to be credible on all devices that are categorised as mobile. That takes different technology and all new technology needs to be implemented without disrupting the main business.
The numbers look great; 74% growth YoY. This includes the wonderful growth due to Wikipedia Zero, it is obvious that the quality needed to support mobile devices is increasingly relevant.
There are many components to MediaWiki being developed and there must be a roadmap to bring much of it together. It does include everything from making sure that content in all the languages can be read on a mobile to adding and editing content.
What makes the achievement of this roadmap so hard are all these little DIY projects that paid off so well for its users. They hate to lose their tools. As technology shifts, they invariably will suffer. The main goal however is to get more people to use, interact, edit with all the Wikimedia content. It is hard work, a struggle and it is continually a work in progress.
Thanks,
GerardM
As more people are moving towards "mobile" devices, it is important to be credible on all devices that are categorised as mobile. That takes different technology and all new technology needs to be implemented without disrupting the main business.
The numbers look great; 74% growth YoY. This includes the wonderful growth due to Wikipedia Zero, it is obvious that the quality needed to support mobile devices is increasingly relevant.
There are many components to MediaWiki being developed and there must be a roadmap to bring much of it together. It does include everything from making sure that content in all the languages can be read on a mobile to adding and editing content.
What makes the achievement of this roadmap so hard are all these little DIY projects that paid off so well for its users. They hate to lose their tools. As technology shifts, they invariably will suffer. The main goal however is to get more people to use, interact, edit with all the Wikimedia content. It is hard work, a struggle and it is continually a work in progress.
Thanks,
GerardM
Saturday, January 05, 2013
The growth in traffic of #Wikipedia from #mobile phones
A growth of 44% compared with the previous month and a growth of 142% compared to the previous year is exceptional. The traffic of 3,709 M in December 2012 is up from 372 M in July 2010 in other words there has been a tenfold growth in less than 2 years.
It does vindicate the effort that goes in making MediaWiki look good on mobile phones.
Thanks,
GerardM
Thursday, May 03, 2012
#Font subsets
A font with all the characters for the Latin or Cyrillic script is big. Over a mega byte big. This is considered too big for use in a web font particularly when mobile devices are targeted as well. For this reason, moves are under way to split mega fonts in subsets.
At SIL they are working on font subsets. Their criteria is to include all the characters used in a given "region". In this way they explicitly target a range of languages. It does reduce the size and one font can be used as a web font for all these languages. When they are to be used on Wikipedia, it will still be necessary to identify the specific language and have the language associated with a particular region.
Typically a font does not include all characters anyway. It is created with a language in mind and when another language needs extra characters, it is tough. Many languages do use the same subset of characters and when a font is identified as complete for one language, it follows that it is complete for all other languages as well.
SIL needs a way to subset its existing fonts. Google in contrast provides many fonts as web fonts that provide subsets of the Latin script. As it is not made obvious if these fonts support languages like German, French or Dutch, it is not really attractive when English is not your language.
Both Google and SIL provide solutions. The key question they do not explicitly answer is: does it support my language.
Thanks,
GerardM
At SIL they are working on font subsets. Their criteria is to include all the characters used in a given "region". In this way they explicitly target a range of languages. It does reduce the size and one font can be used as a web font for all these languages. When they are to be used on Wikipedia, it will still be necessary to identify the specific language and have the language associated with a particular region.
Typically a font does not include all characters anyway. It is created with a language in mind and when another language needs extra characters, it is tough. Many languages do use the same subset of characters and when a font is identified as complete for one language, it follows that it is complete for all other languages as well.
SIL needs a way to subset its existing fonts. Google in contrast provides many fonts as web fonts that provide subsets of the Latin script. As it is not made obvious if these fonts support languages like German, French or Dutch, it is not really attractive when English is not your language.
Both Google and SIL provide solutions. The key question they do not explicitly answer is: does it support my language.
Thanks,
GerardM
Friday, April 27, 2012
Duh; a three letter challenge to #Google #Android
Many a #Wikipedia is written in a language that is known by its three letter ISO-639-3 code. All these languages do not have a two letter equivalent like English (en) or Dutch (nl) have. These languages have their own localisation. This includes localisation for the Wikipedia mobile application.
Many people of us want to use this localisation on their Android phone. This is not that straight forward; you have to install an app that allows you to use a user interface in stead of the Android user interface itself.
There is a problem. Android is not ready to support languages that are only known by their three language code. It is probably an oversight and possibly because all the "big" languages have two character equivalents. However there is no language bigger than the language you grew up with.
NB duh is the code for Dungra Bhil, a language from India.
Thanks,
GerardM
Many people of us want to use this localisation on their Android phone. This is not that straight forward; you have to install an app that allows you to use a user interface in stead of the Android user interface itself.
There is a problem. Android is not ready to support languages that are only known by their three language code. It is probably an oversight and possibly because all the "big" languages have two character equivalents. However there is no language bigger than the language you grew up with.
NB duh is the code for Dungra Bhil, a language from India.
Thanks,
GerardM
Tuesday, March 13, 2012
#Wikimedia #Mobile Frontend is opening up
The mobile frontend of #Wikipedia achieved 9.5% of the total traffic. It is growing rapidly. Having a strategy to support your wiki on mobile platforms is really important. There was a bit of good news on the Wikitech mailing list:
Thanks,
GerardM
[Wikitech-l] First steps at making MobileFron tend usable beyond the WMF infrastruc ture
Over the last couple of weeks, I've taken a few steps to remove some of theWMF-specific bits of the MobileFrontend code base:https://bugzilla.wikimedia.org/show_bug.cgi?id=34144https://bugzilla.wikimedia. org/show_bug.cgi?id=34145
Also, now if you view an article with "useformat=mobile" in the URL's querystring, MobileFrontend will keep the mobile view enabled as you browse pageto page until you explicitly exit the mobile view.
While MobileFrontend has now been generalized enough to be used beyond theWMF cluster, there are still quit a few things that could be done toimprove the ease of out-of-the-box usage. For instance, adding configurableWURFL support (which I believe should be fairly straightforward - this isout of date but the same idea should still work:http://lists.wikimedia.org/pipermail/wikitech-l/2012- January/057478.html)or making it possible to use path-based modifiers to signify mobile view(eg http://mywiki.com/wiki/Article -> http://mywiki.com/wiki/m/ Article -https://bugzilla.wikimedia. org/show_bug.cgi?id=35178).
It would be great if anyone can help test/provide feedback for the changesthat have been made, and especially if anyone wants to help add thefeatures mentioned above!There are many organisations large and small who use MediaWiki. Many of them stand to gain a lot of traffic with out of the box support for mobile devices. The great thing of this effort is that the MobileFrontend will be supported in the next releases; it is what the WMF uses itself.
Thanks,
GerardM
Wednesday, February 29, 2012
DYK #Wiktionary does #mobile
To my complete surprise, the "other" Wikimedia projects are now supported by the Wikipedia Mobile software. It is a bit of a hack because you may get a security message on some browsers stating "wikipedia" as the target with you having requesting your project in stead.
Having a menu on the English Wiktionary featuring "unflappable" as the word of the day is appropriate.
When there is no main page for your Wiki yet, you want to read the instructions on the creation of a mobile main page here. The tags available are very much appropriate for a Wikipedia but they can be used to suit your needs. Obviously for the best result you have to complete the localisation of the mobile application at translatewiki.net.
Thanks,
GerardM
Having a menu on the English Wiktionary featuring "unflappable" as the word of the day is appropriate.
When there is no main page for your Wiki yet, you want to read the instructions on the creation of a mobile main page here. The tags available are very much appropriate for a Wikipedia but they can be used to suit your needs. Obviously for the best result you have to complete the localisation of the mobile application at translatewiki.net.
Thanks,
GerardM
Have a #mobile, have a menu
When your #Wikipedia does not have a mobile main page yet, with some HTML trickery you can have one. One of the more recent projects to present a menu is the Kannada Wikipedia, I was also told that the Odia Wikipedia recently acquired a menu.
If you want to test if your project has a mobile main page, just include an m between the language code and the project code eg https://hi.m.wikipedia.org. When there is no mobile main page yet, you can find some instructions on the creation of a mobile main page here. Obviously for the best result you have to complete the localisation of the mobile application at translatewiki.net.
For languages like Odia and Kannada there is one additional bit of nuisance. It is the lack of support for the script used for the language in most browsers. It would be cool when the support of WebFonts is part of the mobile roadmap.
Thanks,
GerardM
If you want to test if your project has a mobile main page, just include an m between the language code and the project code eg https://hi.m.wikipedia.org. When there is no mobile main page yet, you can find some instructions on the creation of a mobile main page here. Obviously for the best result you have to complete the localisation of the mobile application at translatewiki.net.
For languages like Odia and Kannada there is one additional bit of nuisance. It is the lack of support for the script used for the language in most browsers. It would be cool when the support of WebFonts is part of the mobile roadmap.
Thanks,
GerardM
Tuesday, January 24, 2012
#Wikipedia for free in #Africa with #Orange
Orange is the first to sign up to Wikipedia zero. Our ambition is a world in which every single human being can freely share in the sum of all knowledge. It is really awesome that the 70.4 million customers of Orange will be able to access Wikipedia in 20 countries for free on their mobile phone. They are in Botswana, Cameroon, Central African Republic, Egypt, Equatorial
Guinea, Guinea Bissau, Guinea Conakry, Jordan, Ivory Coast, Kenya, Mali,
Madagascar, Morocco, Niger, Senegal, Tunisia, Uganda, Niger, Senegal, Congo and Vanuatu.
Obviously, many languages are spoken in all these languages. It will be particularly interesting to learn what the effect will be on the editor community. So far, most if not all editing is done on computers. With this new potential for growing our readers, the availability of content is what will limit our growth.
These are the languages spoken in Africa, the numbers however reflect global traffic. As you can see, the existing traffic for the languages native to Africa is still really small.
For the Wikimedians interested and involved in Africa, this is the time to write content for Africa. When this content is what people read, it now has much more of a potential to really make a difference in sharing the sum of all knowledge with every human being.
Thanks,
GerardM
Obviously, many languages are spoken in all these languages. It will be particularly interesting to learn what the effect will be on the editor community. So far, most if not all editing is done on computers. With this new potential for growing our readers, the availability of content is what will limit our growth.
These are the languages spoken in Africa, the numbers however reflect global traffic. As you can see, the existing traffic for the languages native to Africa is still really small.
For the Wikimedians interested and involved in Africa, this is the time to write content for Africa. When this content is what people read, it now has much more of a potential to really make a difference in sharing the sum of all knowledge with every human being.
Thanks,
GerardM
Labels:
Africa,
mobile,
traffic,
Wikipedia,
Wikipedia zero
Sunday, January 22, 2012
#Wikimedia #Netherlands #NewYear reception
The Dutch chapter organised its start of the New Year again in a Museum. What was not clear was that you had to register because there is a limit to how many people can have a tour at the same time. It was SO popular, that it was oversubscribed before this registered on most of us. The Teylers museum prepared a spectacular tour for us; it included a look at the first print of the Diderot and d’Alembert encyclopaedia.
For the Wikipedians this is obviously a treat: seeing the first Western encyclopaedia and knowing that Wikipedia is just the latest incarnation of what started in the Enlightenment is quite awesome.
At the reception it became clear how many of the regular Wikimedians were absent. However, when several of the people present participate in the Teyler's writing challenge, it will be proven well worth it.
Other subjects that were discussed were quite diverse as well;
For the Wikipedians this is obviously a treat: seeing the first Western encyclopaedia and knowing that Wikipedia is just the latest incarnation of what started in the Enlightenment is quite awesome.
At the reception it became clear how many of the regular Wikimedians were absent. However, when several of the people present participate in the Teyler's writing challenge, it will be proven well worth it.
Other subjects that were discussed were quite diverse as well;
- a Geograph project for the Netherlands and combining this with the Wikimedia smartphone apps
- statistics and whether the API data use is included
- having pictures of persons on the Internet with or without names
- ...
All in all a magnificent start of the year for Wikimedia Nederland.
Thanks,
GerardM
Labels:
Dutch chapter,
Geograph,
GLAM,
meeting,
mobile,
Netherlands,
Wikipedia
Tuesday, January 03, 2012
Preferential treatment
The latest #translatewiki.net localisation rally had a twist. To qualify, the localisation for the Kiwix and the Wikipedia Mobile applications had to be completed for the language before MediaWiki messages were accepted.
Our thinking was: the most used messages are typically already complete and at this time growth of our content is very much taking place off-line or on a mobile phone.
For mobile phone use we have statistics that show a growth of 144% compared with last year December. Our support for mobile phones and the support for different writing systems on mobile phones is improving. As more people buy increasingly sophisticated mobiles, this growth may even increase.
During the localisation rally 30 additional languages were completed for Kiwix bringing the total to 65. For Wikipedia Mobile we now support 68 languages completely. We hope that our December 2011 rally sets the stage for a wonderful 2012 with even more people sharing in the sum of all knowledge.
Thanks,
GerardM
Our thinking was: the most used messages are typically already complete and at this time growth of our content is very much taking place off-line or on a mobile phone.
For mobile phone use we have statistics that show a growth of 144% compared with last year December. Our support for mobile phones and the support for different writing systems on mobile phones is improving. As more people buy increasingly sophisticated mobiles, this growth may even increase.
During the localisation rally 30 additional languages were completed for Kiwix bringing the total to 65. For Wikipedia Mobile we now support 68 languages completely. We hope that our December 2011 rally sets the stage for a wonderful 2012 with even more people sharing in the sum of all knowledge.
Thanks,
GerardM
Tuesday, December 20, 2011
The new #Android
The new "ice cream sandwich" release for the Android smart phones has one feature that makes many Android users in India with a previous release wish for an upgrade..As you can see to the left, Android supports our WebFonts. Wikipedia articles can be read while other websites in for instance the Kannada language will show the infamous Unicode boxes.
Android is open source software and consequently it should be possible to figure out what it takes to make Webfonts work for the existing installed base. An alternative would be to add support by installing fonts locally on Android; this would be even better because all Indic languages websites become readable.
Thanks,
GerardM
Monday, December 12, 2011
Traffic from #mobile devices for the languages of #India
Increasingly people find their #Wikipedia on the mobile phone. The surprise is, that traffic from mobile devices for the Indic languages is doing spectacularly well. A year ago such traffic did hardly exist and now the yearly growth rate for Hindi for instance is 10804%.
Given that most mobile phones do not support the scripts used by the languages of India, the question is very much what devices they are. It will be equally interesting to learn what difference the implementation of WebFonts later today will make for other mobile devices.
These statistics for mobile traffic from India are updated every day; it will be interesting to learn not only what languages will benefit but also what devices are capable of supporting Unicode content with web fonts. When I am to buy a mobile phone, the ability of supporting my mother tongue would feature prominently as a must have item.
Thanks,
GerardM
Given that most mobile phones do not support the scripts used by the languages of India, the question is very much what devices they are. It will be equally interesting to learn what difference the implementation of WebFonts later today will make for other mobile devices.
These statistics for mobile traffic from India are updated every day; it will be interesting to learn not only what languages will benefit but also what devices are capable of supporting Unicode content with web fonts. When I am to buy a mobile phone, the ability of supporting my mother tongue would feature prominently as a must have item.
Thanks,
GerardM
Saturday, December 10, 2011
#Wikimedia #mobile has language support
Niklas has landed the first commit of localization data from TranslateWiki.net into the repository. The app now picks up the language in Android's locale and shows localized menus in most of the UI.We will be very interested to learn if there are Android devices with customised locales for the Indic languages.
It _should_ also default to the selected language for content on first launch.
There are a couple bugs yet:
* Changing locales while the app is running doesn't take effect
* Chinese locales don't work
We also have localizations for a number of languages that aren't necessarily in a default Android device's set of languages, such as Hebrew and various Indic languages. These *should* work on Android devices that have been customized with locales for those languages, but we'd appreciate testing!
-- brion
Thanks,
GerardM
Sunday, November 20, 2011
The #Wikipedia challenge for an AppStore
When an application has been developed, tested and ready, it gets into an AppStore. Except that a developer develops and when he is done it still needs to be localised.
As Wikipedia exists in over 270 languages, you can imagine that the localisation for any application is a continuous process at translatewiki.net. The challenge for all the AppStores; support this continuous stream of new localisations.
Even existing users of a Wikipedia application may be in need for new and improved localisations. Really how are these stores going to cope ??
Thanks,
GerardM
Subscribe to:
Posts (Atom)





















