Since our current Squid stats  don't look very accurate or precise, I
decided to generate something myself based on the logs we have. I
analyzed a week's worth of logs, from 2013-06-10 to 2013-06-16. I
generated three sets of data:
* minor: browsers grouped by their minor version, e.g. all Androids 4.2
go together, all Safaris 5.1, etc.
* major: browsers grouped by their major version, e.g. all Androids 4 go
together, all Safaris 5, etc.
* vendor: browsers grouped by their name only, e.g. all Androids go
together, all Safaris, etc.
Each group has also an additional file with all the unknown user agents
logged (they are logged as "Other" in the main files). Everything is
Most of it looks like I expected, the market is shared mostly among
mobile Safari and Android. What I hadn't expected is that Android 2.3 is
still the most popular Android at 9.79%. That's a lot. I started
thinking what we could do about this. After some googling I found lots
of Android 2.x users frustrated by the fact that Chrome is not available
for Android older than 4 and they're stuck with a crappy browser.
I tried looking for an alternative and I found it rather quickly:
Firefox. Mobile Firefox is a sad 0.26% of our users, even less than
desktop Firefox (0.29%)! I tried installing it on the first Google Nexus
and hey, maybe it's not superfast, but it's better than the stock
Android 2.3 browser and supports both photo uploading and our new editor
really well (stock Android 2.3 doesn't support uploads and the editor
is... quite wonky). So, my suggestion is: let's show a banner or a call
to action for Android 2.x users telling them about this and encouraging
them to try Firefox. It's free open software and I think it's better
than what stock Android 2.x browser is. What do you think? Wikimedia
Foundation <3 Mozilla Foundation? ;)
Unrecognized browsers are mostly bots with one notable exception,
NativeHost, which is probably the Windows Phone app (I'm guessing ).
We had shelved my patch, patch 64629 <https://gerrit.wikimedia.org/r/64629>,
in hopes that an earlier patch, patch
35233 <https://bugzilla.wikimedia.org/show_bug.cgi?id=35233>), would
resolve the issue naturally as Google re-indexed. But it appears Google has
re-indexed and yet the .zero.wikipedia.org URLs are still present in
Google's index, instead of the <language>.wikipedia.org URLs.
I have thus resubmitted patch 64629 <https://gerrit.wikimedia.org/r/64629> for
re-review. We will need to further discuss whether it is appropriate to
have Google completely remove .zero.wikipedia.org links from their cache,
or if perhaps we need to open a support thread with Google about canonical
On Tue, May 28, 2013 at 1:13 PM, Kul Wadhwa <kwadhwa(a)wikimedia.org> wrote:
> Adam Baso (copied on this email) is working on it and a fix is ready.
> He'll do some testing to make sure it's resolved.
> On Tue, May 28, 2013 at 10:22 AM, Tomasz Finc <tfinc(a)wikimedia.org> wrote:
>> Looping Dan Foy in who's managing the Zero backlog.
>> On Mon, May 27, 2013 at 8:01 AM, MZMcBride <z(a)mzmcbride.com> wrote:
>> > K. Peachey wrote:
>> >>Can you please file this in bugzilla <https://bugzilla.wikimedia.org>?
>> > https://bugzilla.wikimedia.org/show_bug.cgi?id=48856
>> > MZMcBride
>> > _______________________________________________
>> > Wikimedia-l mailing list
>> > Wikimedia-l(a)lists.wikimedia.org
>> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>> Wikimedia-l mailing list
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> Kul Wadhwa
> Head of Mobile
> Wikimedia Foundation
I've updated the Commons iOS app in the beta area on TestFlight --
everybody who's already signed up except for the last couple of additions
should be able to install from there (and should have an email pointing to
Unfortunately we can't submit the update to the App Store right now, as
parts of the Apple Developer Center that we need are still offline after a
hack at Apple last week. We'll get it in the review queue when it's
available again... ['iTunes Connect' for the actual app submission is
theoretically online, but won't let us upload until we confirm the latest
developer agreement update, which requires access to the 'Member Center'
which is offline. :P]
This update (1.0.6) includes a HUGE amount of UI improvements that Monte
has been working on the last few weeks, with input from Vibha and May on
the design team. Y'all have a lot to be proud of, the app's getting really
I've been exploring a mystery of why users get logged out of the mobile
site without doing anything. I thought I'd narrowed it down to a 'bug' in
that if you log out you get logged out on all devices (see
Sadly however after 48 hours I have been logged out of the mobile site
despite not logging out of desktop or mobile during this time.
I'm not sure what happened but I am going to check my chrome history for
some clues to double check if I did log out. I also need to check my login
status on desktop to see if that has been effected.
Thus the plot thickens. I need a new theory.
This makes me very sad.
Any ideas welcomed...