Re: [WikimediaMobile] Wikipedia for iOS named an Editor's Choice

[Toby Negrin]

This is really impressive and represents a lot of great work.
Congratulations to the iOS team!

-Toby

On Sat, Oct 28, 2017 at 06:36  wrote:

> Way to go team iOS ! 🍾
>
>
> On Oct 27, 2017 at 4:00 PM, > wrote:
>
> Congrats!!!🎊
>
> On Fri, Oct 27, 2017 at 3:58 PM, Ramsey Isler 
> wrote:
>
>> Excellent! Congrats to everyone involved. :)
>>
>>
>> On Saturday, October 28, 2017, Joshua Minor  wrote:
>>
>>> Hello mobile Wikimedians,
>>>
>>> Today Apple named the official Wikipedia app an Editor's Choice. This is
>>> the highest level of recognition for an app by Apple, and gets us a special
>>> badge and placements in the App Store. In their email to me about the
>>> change they explained that they wanted to recognize the great improvements
>>> to the app on iOS and particularly our work on accessibility over the last
>>> couple years.
>>>
>>> This is great recognition for the team's and volunteer contributor's
>>> work, but more importantly, puts Wikipedia in its rightful place as a first
>>> class citizen on the App Store. Its an honor to build an app for something
>>> as beloved and awesome as Wikimedia, and we're so gratified to see our
>>> efforts to make the Wikipedia app beautiful, and usefu,l to iOS users
>>> acknowledged like this.
>>>
>>>
>>> [image: Inline image 1]
>>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
>
> --
> Cooltey Feng
> Software Engineer
> Readers
> Wikimedia Foundation
> cf...@wikimedia.org
> ___ Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
-- 
-Toby
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikipedia v5.6.0 for iOS released to TestFlight

[Toby Negrin]

Thanks iOS team!

A few of the nice touches in this release:

   1. Night/sepia mode
   2. Roll of the dice for Random
   3. Timeline is super interesting -- I can see a lot of rabbit-holing[1]
   here :)

-Toby

[1] https://commons.wikimedia.org/wiki/File:Rabbit_hole_illustration.png

On Mon, Jul 24, 2017 at 2:39 PM, Joshua Minor  wrote:

> Hello mobile Wikimedians,
>
> Today we've released a beta of the Wikipedia app to TestFlight which
> includes our most requested feature: dark reading mode!
>
> Its just one of several new appearance options, including dark and sepia
> color modes, image dimming and convenient screen brightness control.
>
> This release also includes a new "On this day" card in the Explore feed
> for four initial languages (English, German, French and Swedish). On this
> day is built on the rich anniversary pages[1] and selected anniversaries[2]
> available on many Wikipedias, to highlight important events that occurred
> on this date. Tap through for a timeline view and swipe back through
> history!
>
> The beta also includes a small sticker pack for iMessage. We worked with
> the Wikimedia Foundation's Communications team to create a set of public
> domain stickers[3], so you can send wiki memes in texts. Now you can tell
> your friends "citation needed!" in a group chat :) These stickers will be
> coming to other social media platforms as well, but iOS beta testers get to
> try them out first!
>
> Thanks again to all our testers. If you'd like to become a tester please
> sign-up here:
> https://docs.google.com/forms/d/e/1FAIpQLSfW7zFnUDYABvHLWlFclZ7O
> JEK82WjVIjs_dSzwIDM0Hnz31A/viewform
>
> Thanks,
> Josh Minor
> PM, Wikipedia app for iOS
>
>
> [1] - https://en.wikipedia.org/wiki/List_of_historical_anniversaries
> [2] - https://en.wikipedia.org/wiki/Wikipedia:Selected_anniversaries/All
> [3] - https://commons.wikimedia.org/wiki/Category:Wikipedia_digita
> l_stickers
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Image recognition app scans paintings to act like Shazam for art

[Toby Negrin]

Thanks Andy -- I'll bump Alex Stinson who works with museums and other
institutions. It might have some interesting intersections with structured
data on commons.

-Toby

On Fri, Mar 3, 2017 at 3:34 AM, Andy Mabbett 
wrote:

> This is interesting, and something we could emulate, given the amount
> of artworks on Commons/ Wikidata:
>
> https://www.newscientist.com/article/2123373-image-
> recognition-app-scans-paintings-to-act-like-shazam-for-art/
>
> --
> Andy Mabbett
> @pigsonthewing
> http://pigsonthewing.org.uk
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Analytics] Readership metrics for the timespan until December 4, 2016

[Toby Negrin]

Thank you so much for this Zareen! It's really great to see this report --
so much interesting data to think about!

-Toby

On Mon, Dec 12, 2016 at 5:45 PM, Zareen Farooqui  wrote:

> Hi all,
>
> This resumes the usual look
>  at
> our most important readership metrics. This time we can report that daily
> pageviews are up 4.8% (since the last report), with an interesting recent
> peak which meant that November’s pageviews surpassed those of November 2015
> (coincidentally also) by 4.8%, after October had already seen a 2.1%
> year-over-year increase. The iOS Wikipedia app saw increased downloads,
> while the Android app’s install base has stopped its previous downward
> trend.
>
> As laid out earlier
> ,
> the main purpose is to raise awareness about how these metrics are
> developing, call out the impact of any unusual events, and facilitate
> thinking about core metrics in general. As always; feedback and discussion
> welcome. Week-over-week and month-over-month changes are now being recorded on
> the Product page
>  at
> MediaWiki.org. This edition of the report covers a timespan of eighteen
> weeks.
>
> Some other recent items of interest, in case they didn’t already catch
> your attention:
>
>-
>
>The WMF Reading team published its quarterly review presentation
>
> 
>for Q1 2016-17 (July-September), which includes lots of traffic and usage
>data.
>-
>
>At the Foundation’s August metrics meeting
>
> ,
>the Reading team gave an update on longer-term traffic trends since 2013.
>(TL;DR: Overall pageviews have been flat to slightly declining, mobile has
>been steadily rising but recently slowed down, desktop has declining during
>these three years. However, total pageviews have been slightly increasing
>year-over-year in the last few months.) See the chart below, updated with
>data until November:
>
> [image: Wikimedia monthly pageviews (desktop+mobile), 2013-2016 (version
> December 2016).png]
>
> In particular, as mentioned, the number of total pageview saw
> year-over-year increases of +2.1% for October and +4.8% in November, in
> contrast to e.g. the -10.5% we had for May 2015-May 2016.
>
> Now to the usual data. (All numbers below are averages for August
> 1-December 4, 2016 unless otherwise noted.)
>
> Pageviews
>
> Total: 529 million/day (+4.76% from the previous report timeframe, with
> corrected numbers for anomalously high traffic on some main pages
> )
>
>
> Context (April 2015-December 2016):
>
>
>
> See also the Vital Signs dashboard
> 
>
> (Small caveats: iOS app’s pageviews were undercounted by about 1.6
> million/day from mid September to early November due to a bug
> .)
>
> Overall pageviews increased steadily during the timespan of this report
> aside from the week ending October 30th (right before Halloween) and the
> end of November. There appears to be a peak in pageviews in November.
>
> To facilitate our understanding of which traffic movements are seasonal
> and which may indicate lasting changes, here is a chart overlaying the
> total pageview numbers back to May 2013 (the earliest time for which we
> have data according to the current pageview definition):
>
> The blue line indicates a non-seasonal rise peaking around November 12. We
> checked whether this peak came from a particular country and were able to
> exclude that possibility.
>
> Wikimedia Daily Pageviews from US
>
>
> Pageviews in US do not show any drastic changes (even around the time of
> the US elections).
>
>
> Wikimedia Daily Pageviews from Mexico
>
>
> In Mexico, there seems to been a huge drop starting October 27th (perhaps
> some sort of local outage).
>
>
> Wikimedia Daily Pageviews from Ecuador
>
>
> Ecuador shows a huge spike on October 30th, followed by a drop for several
> days.
>
> Desktop: 54.1% ​(previous report: ​54.1%)
>
> Mobile web: 44.8% ​(previous report: 44.6%)
>
> Apps: 1.1% ​(previous report: ​1.3%) (missing some iOS pageviews, cf.
> above)
>
> Context (December 2015 - December 2016):
>
> Overall mobile percentage is similar to the last report, but we did see a
> small increase (besides one week in August) until late September.  As a
> reminder, mobile already has a solid majority in terms of unique devices,
> cf. below.
>
>
>
> Global North ratio: 75.3% of total pageviews (previous report: 75.5%)
>
> Context (January - December 2016):
>
>
>
> There is a slight increase in Glo

Re: [WikimediaMobile] [Wmfall] Accessibility Sprint

[Toby Negrin]

Hi Josh and iOS team and volunteers and Volker!

This is wonderful -- thank you for organizing and taking the time for this
work.

-Toby

On Wed, Nov 2, 2016 at 3:32 PM, Joshua Minor  wrote:

> Just a reminder that the Wikipedia accessibility brownbag will be
> *tomorrow* at 1:15 PDT. Join us either in person in the Chip Deubner
> Lounge in SF, or via YouTube:
> https://www.youtube.com/watch?v=GsE0PpQkBcI
>
> I'll be giving a brief intro on the basics of accessibility for the
> visually impaired, and the work the iOS team has been doing this week, and
> Volker Eckl,  Sr. UX Engineer from the WMF Editing team will talk about
> efforts on OOjs UI for the web.
>
> And huge thanks to the volunteers who showed up in Philly this weekend to
> hack on the app with Corey, Joe and Austin (https://twitter.com/wild37/
> status/792485190924955648). We're working through your pull requests.
>
> Thanks,
> Josh
>
> On Thu, Oct 27, 2016 at 1:44 PM, Joshua Minor 
> wrote:
>
>> Hello,
>>
>> We all know the vision: All the knowledge. Every single human being.
>>
>> To achieve this, we need to support users across geographies and
>> languages, but also people with different physical abilities.
>>
>> The iOS team, along with others at the foundation, are taking the next
>> week to focus on how we can make our app, and projects, easier for people
>> with visual impairments. We're working with an expert blind developer named
>> Austin Seraphin[1] to make sure we get it right, but we also need your help!
>>
>> Check out our wiki: https://www.mediawiki.org/wiki
>> /Accessibility/2016_sprint
>>
>> Some highlights of special events you can participate in over the next
>> week:
>>
>>- *If you are in the Philadelphia area this Saturday *join engineers
>>from the WMF iOS team for an in person hack-a-thon to make the app more
>>accessible [2]
>>- Tune in one week from today, or join us in SF, for a *brownbag
>>about progress and challenges *of making OOjs UI and the iOS
>>Wikipedia app accessible [3]
>>- *Contribute code*, testing or comments for our accessibility tasks
>>for iOS[4], or across the projects[5]
>>
>> If you're not able to join us this week, Corey from the iOS team has also
>> proposed a related session for the Tech Summit. Check it his proposal here
>> [6]
>>
>> [1] Check his TedX talk on how mobile phones have enabled the blind:
>> https://www.youtube.com/watch?v=0EQOZRIA-nA
>> [2] https://www.mediawiki.org/wiki/Accessibility/2016_sprint
>> /Side_Project_Saturday
>> [3] Event is at 1:15 PST in the 5th floor common space, and will be
>> broadcast and archived on YouTube. Streaming link will be posted on the
>> wiki shortly. For staff, this event is on the Staff and Learning and Fun
>> calendars.
>> [4] Get started contributing by checking out our github:
>> https://github.com/wikimedia/wikipedia-ios  Our work will happen on this
>> phab board for the next release: https://phabricator.wikimedia.
>> org/project/board/2281/
>> [5] There's no shortage of tasks for the web, apps and even internal
>> tools: https://phabricator.wikimedia.org/tag/accessibility/
>> [6] https://phabricator.wikimedia.org/T148435
>>
>> Thanks,
>> Josh Minor
>> PM for Wikipedia app for iOS
>>
>
>
> ___
> Wmfall mailing list
> wmf...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] editing smaller headings

[Toby Negrin]

Hi Amir -

I can't speak to the specifics of the edit button but we are investigating
mobile editing in the app along with the collaboration team this quarter[1]
for wikidata descriptions.

This will include work on some fundamental issues (notifications for one)
that will (hopefully) open the door to more mobile editing functionality in
the app.

-Toby

[1]
https://m.mediawiki.org/wiki/Wikimedia_Engineering/2016-17_Q2_Goals#Reading

On Wednesday, October 5, 2016, Jon Robson  wrote:

> Interestingly due to a bug we do show them on English Wikipedia and I was
> wondering myself whether that was the right behaviour or not.
>
> https://phabricator.wikimedia.org/T130898#2675368
>
> On Wed, 5 Oct 2016, 7:45 a.m. Stephen Niedzielski, <
> sniedziel...@wikimedia.org
> > wrote:
>
>> I think this might be a question for design (cc'd). We do have long press
>> to edit text anywhere within the article.
>>
>> On Wed, Oct 5, 2016 at 8:14 AM, Amir E. Aharoni <
>> amir.ahar...@mail.huji.ac.il
>> > wrote:
>>
>>> Hi,
>>>
>>> I've been asked by a Hebrew Wikipedia editor: Why is it only possible to
>>> have the edit button at the top headings (==), but not smaller headings
>>> (===, etc.)?
>>>
>>> This should be in https://www.mediawiki.org/wiki/Wikimedia_Apps/Android_
>>> FAQ#Editing :)
>>>
>>> --
>>> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
>>> http://aharoni.wordpress.com
>>> ‪“We're living in pieces,
>>> I want to live in peace.” – T. Moore‬
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> 
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> 
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] New Android production release

[Toby Negrin]

Second that - great work Android team and volunteers - the app just gets
better and better!

-Toby

On Monday, October 3, 2016, Jon Katz  wrote:

> Congratulations, team! It looks great.
>
> On Fri, Sep 30, 2016 at 1:26 PM, Dmitry Brant  > wrote:
>
>> Hi everyone,
>>
>> We're excited to bring you an updated version of the Wikipedia Android
>> app ,
>> rolling out now to the Google Play Store! [1]
>>
>> This version contains the following updates:
>> - Access your favorite features more easily with bottom navigation:
>> quickly jump between the Explore feed, your reading lists, your
>> recently-viewed articles, and pages nearby you.
>> - When reading an article, the bottom toolbar now provides access to the
>> most popular actions (save to reading list, share, change language, find in
>> page, and table of contents).
>> - Reading lists and their contents are now searchable.
>> - A number of minor bug and crash fixes.
>>
>> Want to help make the app even better? Read our getting-started
>> 
>> guide, and start contributing!
>>
>> [1] For devices without Google Play services, you may download
>> 
>> the app directly.
>>
>>
>> Cheers,
>>
>> --
>> Dmitry Brant
>> Senior Software Engineer / Product Owner (Android)
>> Wikimedia Foundation
>> https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> 
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Wikipedia for iOS 5.0.5 released to App Store

[Toby Negrin]

Congrats iOS folks -- a good day for apps indeed!

-Toby

On Thu, Jul 28, 2016 at 1:30 PM, Joshua Minor  wrote:

> Hello mobile wikimedians,
>
> Big day for Wikipedia apps. First, big congrats to the Android team on
> today's awesome update!
>
> On iOS, after a long beta testing period[1], focusing on improving
> performance and reducing crashes and instability, we've released the 5.0.5
> version of Wikipedia to the App Store.
>
> We expect users will see:
>  - less hangs or failures to load on the Explore feed
>  - full AuthManager support and stable account log in and creation
>  - use less device resources, espeically when backgrounded and in our
> backups
>  - most importantly, less crashes!!
>
> We also fixed over a two dozen other bugs and usability issues, large and
> small.
>
> Thanks to our volunteers (particularly thanks to huayu0723, bart-kneepkens
> and gregggreg2 for their code contributions, and josve05a for his
> invaluable help with OTRS and testing). I also want to thank our beta
> testers, who put in extra effort on this version to help us find and
> diagnose stability issues.
>
> Thanks,
> Josh
>
> [1] - You can read about the changes we made and the reason behind the
> long beta in previous announce post here:
> https://lists.wikimedia.org/pipermail/mobile-l/2016-June/010254.html
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Android Wikipedia beta app release (2.3.148-beta-2016-07-18)

[Toby Negrin]

Congratulations Android team! The feed is an awesome addition to the app.
I'm looking forward to the production release!

-Toby

On Tue, Jul 26, 2016 at 1:29 PM, Orsolya Gyenes <
gyenes.orso...@wiki.media.hu> wrote:

> WOW!
>
> You guys deserve a BIG applaud, this is definitely amazing!
>
> We've been waiting for something like this for so long!
>
> I love it, especially the Trending feed.
>
> I'm wondering if there's a possibility to change language on Trending? I
> see our results of hu.wiki but I'd like to know what's trending on other
> wikis?
>
> Thank you very much for your hard work!
>
> 🙋🍸💯🎉
>
> *~Orsolya*
>
> 2016-07-19 0:02 GMT+02:00 Stephen Niedzielski 
> :
>
>> Introducing the Explore Feed: a new way to discover Wikipedia content!
>>
>> We've redesigned the home screen of the app, which now shows a feed of
>> featured content from Wikipedia, as well as personalized reading
>> suggestions based on your reading history in the app[0]. See Wikipedia
>> articles about current events, today's trending articles, today's featured
>> article and featured picture from Commons, and more[1]. Scroll down in the
>> feed to see featured content from previous days.
>>
>> Since this is a significant departure from the previous experience in the
>> app, we especially welcome the feedback of our Beta users. Let us know if
>> you see any issues or bugs, or if you have any suggestions for making it
>> even better.
>>
>> This version includes a volunteer contribution from repeat contributor
>> Amir Aharoni[2]. Good work! You too can help make it better! Read our
>> getting started guide[3]. We can't wait for your contributions!
>>
>>
>> -The WMF Android team
>>
>> [0] Note: your reading history is only stored locally on your device.
>> [1] "In the news" and "Today's featured article" are currently limited to
>> English Wikipedia only.
>> [2] Wikipedia User:Amire80, IRC and Twitter: aharoni
>> [3]
>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Mobile Wikipedia, Commons, Wikidata, and Pokémon

[Toby Negrin]

Hi Pine -- did you have any specific ideas? I spent some time in the gaming
industry and am familiar with Ingress, the game that Pokeman Go is based
on, as well as the theories behind mechanics/compulsion loops that mobile
games use.

I'll share one general thought -- the research-edit-publish loop is a great
mechanism -- it's quick and easy and very gratifying, especially combined
with a google search.

However, we've generally found that the notion that we use gaming mechanics
to encourage people to read or edit wikipedia does not have broad support
in our communities.

-Toby



On Thu, Jul 14, 2016 at 2:26 PM, Pine W  wrote:

> Hi WMF Mobile and Research,
>
> I'm wondering if we (mostly meaning "you" but perhaps with external
> collaborators) have considered how the Wikipedia mobile apps, Wikipedia
> mobile web, the Wikidata game, and/or the Commons app could borrow some
> design ideas or features from Pokémon Go to make Wikimedia offerings more
> appealing, particularly to younger audiences. This would apply to content
> consumption and contribution, as well as community aspects of Wikimedia
> experiences, particularly on mobile platforms.
>
> Thanks,
>
> Pine
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Cross-post: Today's CREDIT showcase - video

[Toby Negrin]

Thanks Adam and all who demo'd. Great to see some community members on here
as well.

-Toby

On Thu, May 12, 2016 at 6:39 PM, Adam Baso  wrote:

> In case you don't follow wikitech-l.
>
> -Adam
>
>
> -- Forwarded message --
> From: Adam Baso 
> Date: Thu, May 12, 2016 at 8:34 PM
> Subject: Today's CREDIT showcase - video
> To: Wikimedia developers 
>
>
> Here's video from today's 12-May-2016 CREDIT showcase
> .
>
> https://www.youtube.com/watch?v=GwTDDWjxoek&feature=youtu.be&t=7
>
> https://commons.wikimedia.org/wiki/File:CREDIT_-_May_2016.webm
>
> == Contents ==
>
> * Derk-Jan Hartman: Video.js progress
> * Dmitry Brant: Wikidata infoboxes in Android app
> * Joaquin Hernandez: Vicky chat bot
> * Baha: mobile printing for offline reading
> * Monte: "smart random" content service endpoint
> * Erik: Geo boosting search queries
> * Julien: Maps for Wikivoyage
>
> Thanks!
> -Adam
>
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] iOS Release Candidate

[Toby Negrin]

Hi Sjoerd -- just a quick note; your translations have been submitted to
the app store with 5.0.1. Thanks again!

-Toby

On Fri, Mar 4, 2016 at 5:21 AM, Sjoerd de Bruin 
wrote:

> Hello,
>
> I've just did some translations and I'm worried these won't be included in
> the version that will go live in the App Store. Is that true?
>
> Greetings,
>
> Sjoerd de Bruin
> sjoerddebr...@me.com
>
> Op 3 mrt. 2016, om 02:21 heeft Joshua Minor  het
> volgende geschreven:
>
> Hello mobile Wikimedians,
>
> I'm excited to announce that we submitted a release candidate of our major
> update today, and plan to release publicly on Wednesday March 9th.
>
> If you are in the beta you should be able to install the release now from
> TestFlight.
>
> We are working with Communications on next week's public release, and I'm
> getting our on wiki docs updated, so expect to hear more soon.
>
> On behalf of the iOS team at the WMF, I also particularly want to thank
> our testing volunteers and those who submitted code to the project.
>
> Thanks,
> Josh
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Someone please announce/explain T119235 (RESTBase for Wiktionary)

[Toby Negrin]

To keep the archives happy, Nemo has asked that we provide some
documentation to REST API for en-wiktionary and I asked that we get it
scheduled.

-Toby

On Sat, Feb 13, 2016 at 11:16 AM, Federico Leva (Nemo) 
wrote:

> All my requests were ignored:
> https://phabricator.wikimedia.org/T119235#1951362
> https://phabricator.wikimedia.org/T123142#2025816
>
>
> https://en.wiktionary.org/api/rest_v1/?doc#!/Page_content/get_page_definition_term
> appeared but nobody bothered to tell people and plans for the thing seem to
> be unknowable (or secret).
>
> Nemo
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] MobileFrontend+Wikibase security patch

[Toby Negrin]

Thanks for the quick response everybody.

-Toby

On Thu, Feb 4, 2016 at 10:58 AM, Jon Robson  wrote:

> A security vulnerability has been discovered in MediaWiki setups which
> use both Wikibase and MobileFrontend.
>
> All projects in the Wikimedia cluster have been since patched but if
> you use these two extensions please be sure to apply the fix.
>
> Patch file and issue are documented on
> https://phabricator.wikimedia.org/T125684
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] New iOS app: "Curiosity Shows You Useful Wikipedia Articles Right When You Need Them"

[Toby Negrin]

Thanks Tilman. It's nice to see apps using Wikipedia data. My personal
favorite is FieldTrip[1] which is basically the same thing as Curiousity
but with more data sources[2].

Since Curiousity is charging for the app, it would be nice to see them
contribute back to projects in some way.

-Toby

[1] http://www.fieldtripper.com/
[2] Interestingly, the same people who made field trip went on the make
Ingress which proves a virtual world is more interesting than the real
world ;)

On Tue, Dec 29, 2015 at 12:19 AM, Tilman Bayer  wrote:

> Launched on December 8. See
>
> http://lifehacker.com/curiosity-shows-you-useful-wikipedia-articles-right-whe-1748791446
>
> http://9to5mac.com/community/curiosity-by-tamper-a-beautiful-context-aware-wikipedia-reader-for-iphone/
>
>
> Features (from https://tamper.io/curiosity/ ):
>
> "
> Nearby
> [...] Curiosity uses your location to find interesting articles nearby.
>
> Popular
> [...] Curiosity displays the most popular articles for a given day,
> week, or month all in one place.
>
> Explore
> [...] Receive articles from hand-picked categories that adapt to
> factors such as time, location, and current events. Learn about Famous
> Inventors, Movies Filmed Nearby, or many other categories being added
> and updated regularly.
>
> Bookmarks & History [...]
>
> Search [...]
>
> Read & Share [...]
> "
>
> It's *almost* like they saw
> https://commons.wikimedia.org/wiki/File:IOS_Wikipedia_App_5.0_Update.pdf
> ;)
>
>
> --
> Tilman Bayer
> Senior Analyst
> Wikimedia Foundation
> IRC (Freenode): HaeB
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Mobile web and the curious case of the peacock butterfly

[Toby Negrin]

Thanks Pine -- we're taking a look.

-Toby

On Tue, Dec 15, 2015 at 2:21 PM, Pine W  wrote:

> This page [1] isn't updating in mobile web even with the purge command.
> The desktop version of the page is current. Any ideas of what's happening
> here?
>
> Thanks,
> Pine
>
> [1]
> https://en.m.wikipedia.org/wiki/Wikipedia:Featured_picture_candidates/Peacock_butterfly
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Reading department planning for next quarter

[Toby Negrin]

Thanks Pine -- the team appreciates public discussion on our plans!

1. Budgeting: You can see how we map strategic goals against the teams from
the Roadmap document above and then refer to the annual plan docs to get an
idea of relative investment. A couple of caveats -- sometimes the
activities don't totally matchup with the teams; for example some folks
from Android are working on services. Also, while we have general metrics
for the various strategic goals, we are still working on more specific
metrics and targets so we can be clearer on expected and actual impact for
investments. (It's a good question and probably something we should be more
specific about moving forward)

2. Mobile Editing: We work closely with the Editing team and they are
investigating mobile editing features for the following quarters. I'm
afraid I don't have the goals URL handy but they should be posting shortly.
However, we realize that editors are also readers and we will also
opportunistically identify activities that help editors (user profiles on
mobile for example).

-Toby

On Wed, Dec 9, 2015 at 11:08 PM, Pine W  wrote:

> Hi Moushira,
>
> Thank you for these updates. It's great to see a team pushing out their
> goals for the next quarter for public review.
>
> Two questions:
>
> 1. How are budgets / resourcing aligned with the tasks shown here?
> 2. Are there also improvements planned for mobile web and mobile app
> *editing* for Q3 and Q4?
>
> Thanks!
>
> Pine
>
>
> On Wed, Dec 9, 2015 at 3:58 AM, Moushira Elamrawy  > wrote:
>
>> Hello Everyone,
>>
>> Hope you are enjoying the approach of the end of the year.  In the last 3
>> months the reading team has worked on a process for open strategy planning
>> [0], in order to define priorities, and align tests and products that the
>> team works on, with broader movement goals.
>>
>> Given the strategy work, planning for Q3 (the next quarter: Jan - March)
>> is different; the team is sharing its roadmap for Q3 and Q4 [1], as well as
>> the actions planned for Q3 [2] early on. Despite of the strategy work and
>> planning, these documents are still work in progress; adaptations and
>> changes are likely to take place, given the time frame and tests included.
>> However, the team is sharing early in order to accommodate feedback.  You
>> can also add suggestions for Q4 (Apr - Jun), as long as they align with the
>> roadmap.
>>
>> This is the first team the team shares its plans early and openly, and
>> allows room for feedack and suggestions in future planning. We trust that
>> the open process will help with better engagement and more lessons to learn
>> on best practices.
>>
>> Enjoy December!
>>
>>
>> All the best,
>> M
>>
>>
>> [0]
>> https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Testing
>> [1] https://www.mediawiki.org/wiki/Reading/Roadmap
>> [2] https://www.mediawiki.org/wiki/Reading/Quarterly_Planning/Q3
>> [3] https://www.mediawiki.org/wiki/Reading/Quarterly_planning/Q4
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Android application]Project WikiJourney

[Toby Negrin]

Hi Paul -- Are you asking for some sort of code or architecture review for
your application?

Best,

-Toby

On Fri, Dec 4, 2015 at 1:26 AM, Paul Arzelier  wrote:

> Hi,
>
> I'm currently developing, with some friends, an application called
> WikiJourney to promote « free » (as in a speech) tourism. For now, it can
> locate an android user on a map, display points of interests extracted from
> wikidata and show the user the associated wikipedia articles.
>
> The application will shortly be able to create touristic « tours », but
> currently, we need some feedback from people, and not just user-related
> feedback...
> We feel our code (https://github.com/WikiJourney/wikijourney_app/) is a
> bit messy, but don't know if there's a precise « coding convention » here
> at Wikimedia.
>
> What do you think of it?
>
> Thanks by advance for your feedback,
>
> The WikiJourney Team
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Reading goals for the quarter.

[Toby Negrin]

Hi Everyone --

Our goals for Fiscal Year Q2 (Oct - Dec) are up on the wiki. Apologies for
this taking so long.

https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals#Reading

Please let us know if you have any questions.

-Toby
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] New Android production release

[Toby Negrin]

Totally -- very excited to see the community input! Thanks all.

Also happy to see iteration on link preview -- interested to see if that
improves the experience for our readers.

Nice work everyone!

-Toby

On Wed, Oct 28, 2015 at 9:00 AM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:

> Wohooo! :)
>
>
>
> Florian
>
>
>
> -Original-Nachricht-
>
> Betreff: [WikimediaMobile] [Apps] New Android production release
>
> Datum: Wed, 28 Oct 2015 16:35:18 +0100
>
> Von: Dmitry Brant 
>
> An: mobile-l 
>
>
>
>
>
>
> Hi all,
>
> We're pleased to announce our latest update to the Wikipedia Android
> app[1][2], available now on the Google Play store! Here are the highlights
> from this update:
>
> * More consistent article language display for multilingual users.
> * Fixed occasional abnormal CPU usage.
> * Improved crash reporting.
> * Added preference to enable/disable link previews.
> * Improved link preview design and text.
> * Display system notification after saving an image.
> * Various other bug fixes and design enhancements.[3]
>
> We'd also like to thank the following volunteers for their excellent
> contributions:
> * Daniel Rey (@DanReyLop)
> * Wikinaut (@Wikinaut)
> * Asad Salman (asadpsalman)
> * You?[4]
>
> Cheers,
>
> --
> Dmitry Brant
> Product Owner (Android), Mobile Apps Team
> Wikimedia Foundation
> https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
>
> [1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
> [2]
> https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.1.133-releasesprod-2015-10-26.apk
> [3] https://phabricator.wikimedia.org/T116922
> [4]
> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Wmfall] Tilman is joining the Reading Team!

[Toby Negrin]

Welcome Tilman! We're excited to have you on the team! (and I love the
report :)

On Thu, Oct 15, 2015 at 6:26 PM, Stephen Niedzielski <
sniedziel...@wikimedia.org> wrote:

> Congrats!
>
> On Thu, Oct 15, 2015 at 6:47 PM, Jacob Rogers 
> wrote:
>
>> Congratulations, Tilman!
>>
>> On Thu, Oct 15, 2015 at 5:46 PM, Joe Sutherland <
>> jsutherl...@wikimedia.org> wrote:
>>
>>> Congrats Tilman! A coup for the Reading team :)
>>>
>>> Joe
>>>
>>> On 16 October 2015 at 01:45, Anna Stillwell 
>>> wrote:
>>>
 Congratulations, Tilman.

 On Thu, Oct 15, 2015 at 5:10 PM,  wrote:

> Welcome Tilman! Look forward to working together more.
>
> On Oct 15, 2015, at 5:07 PM, Jon Katz  wrote:
>
> Hi Everyone,
>
> I’m happy to announce that, as of today, Tilman Bayer has officially
> joined the Reading product team as a Senior Analyst. He will increase our
> capacity for understanding our users and the impact of our efforts through
> data analysis. Tilman is responsible for:
>
>-
>
>generating our primary metrics and communicating them
>-
>
>consulting on, analyzing and communicating the results of
>feature-specific instrumentation
>-
>
>driving best practices within the team with regard to analysis
>(aided by his background in mathematics)
>
>
> Tilman has been shadowing the team for about a quarter, and has ramped
> up his involvement dramatically over the last month.  During this period,
> Tilman has moved quickly and is already owning the analysis of a
> significant number of our ongoing projects.
>
> Tilman’s weekly reading metrics report (example
> )
> is currently being sent out to the Mobile-l mailing list (which serves as
> the Reading team’s primary public mailing list). We are still gathering
> feedback from the subscribers of that list and once we have a sustainable
> and stable format, we hope to share more widely.
>
> Tilman has been working with us since July 2011, and has been a
> Wikipedian since 2003. He was an analyst on the Communications team until
> Erik Moeller asked him to join Product & Strategy at the beginning of this
> year. Tilman will be moving out of his current role in Terry’s department
> where he is right now wrapping up the current round of quarterly reviews
> and preparation of the organization-wide quarterly report for Q1.
>
> Best,
>
> Jon
>
> ___
> Wmfall mailing list
> wmf...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
> ___
> Wmfall mailing list
> wmf...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>


 --
 Anna Stillwell
 Major Gifts Officer
 Wikimedia Foundation
 415.806.1536
 *www.wikimediafoundation.org *


 ___
 Wmfall mailing list
 wmf...@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wmfall


>>>
>>>
>>> --
>>> *Joe Sutherland*
>>> Communications Intern [remote]
>>> m: +44 (0) 7722 916 433 | t: @jrbsu  | w:
>>> JSutherland 
>>>
>>> ___
>>> Wmfall mailing list
>>> wmf...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>>
>>>
>>
>>
>> --
>>
>> Jacob Rogers
>> Legal Counsel
>> Wikimedia Foundation
>>
>> NOTICE: This message might have confidential or legally privileged
>> information in it. If you have received this message by accident, please
>> delete it and let us know about the mistake. As an attorney for the
>> Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice
>> to, or serve as a lawyer for, community members, volunteers, or staff
>> members in their personal capacity. For more on what this means, please see
>> our legal disclaimer
>> .
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Some interesting stuff from Google

[Toby Negrin]

Hi Luis --

I honestly don't see a lot of difference between Google, Twitter and
Facebook, since they are all ad supported entities with a fiscal
responsibility to track their users and sell the data. Apple's a bit
different on the surface since they have a different business model. I
agree that these are bad for the internet but so are incredibly slow web
pages that make apps essentially required for a good experience.

On the analytics, this would probably not include their use of our content
in the knowledge graph or elsewhere and also might be troublesome for those
who prefer google not to track their reading.

Bryan's ticket is a good embarkation point for thinking about supporting
new clients; Reading is also planning some Reading infrastructure work for
the summit which could relate[1]

-Toby

[1] https://phabricator.wikimedia.org/T114542









On Thu, Oct 8, 2015 at 2:02 PM, Luis Villa  wrote:

> Toby -
>
> I'm generally 1000% on-board with slow follower for anything user-facing.
> The only reason I might make an exception here is because the competitors
> you mention are all pretty awful for the web generally, and this has uptake
> already from Google and Twitter. (Two isn't great, but two + slim
> opportunity for growth is way better than the guaranteed
> never-greater-than-1 we'll see from FB's option.)
>
> The other reason this intrigues me is that if Google builds in some
> analytics, it might give us a better sense of their current usages for us
> than we currently have. Not much, obviously, but at least something.
> (Remember that in this scenario - direct access from Google properties -
> they already have all that information, the only question is whether it
> gets shared with us so that we can do something useful with it.)
>
> That said, if implementing it is non-trivial, it doesn't make sense to
> spend a huge number of cycles to fast-follow. Hopefully some of the
> improvements Bryan mentions will make it easier in the future - it
> certainly doesn't look like we're in a world where the number of front ends
> is going to get smaller any time soon.
>
> Luis
>
> On Thu, Oct 8, 2015 at 1:25 PM, Toby Negrin  wrote:
>
>> Thanks Bryan and Pine.
>>
>> My feeling is that there are many many new interfaces and form factors
>> emerging right now and we should be cautious about adoption. For example
>> Facebook's instant articles, apple news and even snapchat have similar
>> offerings the AMP.
>>
>> They all seem to be focusing on article speed in a landscape where most
>> pages are larded up with a variety of trackers, ads and other scripts
>> (which we don't have, although we have our own challenges on performance)
>> with the ultimate goal of owning the delivery platform.
>>
>> I'm nervous about picking winners in such a landscape although I'm
>> excited about prototypes like things like the Apple Watch app that came out
>> of the Lyon hackathon. I feel like a slow follower model where we see which
>> solution if any becomes widely used is more appropriate for us.
>>
>> -Toby
>>
>>
>> On Thursday, October 8, 2015, Pine W  wrote:
>>
>>> Hi Bryan,
>>>
>>> Ah, I was thinking of the 2 different mobile web editing experiences
>>> (not 2 different apps) for Android depending on form factor. My
>>> understanding is that tablets have VE enabled on mobile web now (I have yet
>>> to try it) while phones do not have VE enabled on mobile web yet.
>>>
>>> Pine
>>> On Oct 8, 2015 12:56 PM, "Bryan Davis"  wrote:
>>>
>>>> On Thu, Oct 8, 2015 at 1:32 PM, Pine W  wrote:
>>>> > We currently have at least 6 channels, I believe:
>>>> >
>>>> > 1. Desktop Web
>>>> > 2. Mobile Web
>>>> > 3. Android phone
>>>> > 4. Android tablet
>>>>
>>>> I don't think that we have separate native apps for the phone and
>>>> tablet form factors.
>>>>
>>>> > 5. IPhone
>>>> > 6. Legacy Android phone
>>>> >
>>>> > I'm no expert on mobile developmemt, but perhaps WMF could experiment
>>>> with
>>>> > Google's idea on just one channel to start?
>>>>
>>>> AMP would only be appropriate for the mobile web channel from the list
>>>> above. Implementing it would be a matter of placing some sort of
>>>> translating proxy between MediaWiki and the requesting user agent that
>>>> downgraded the HTML produced by MediaWiki to AMP's restricted HTML
>>>&

Re: [WikimediaMobile] Some interesting stuff from Google

[Toby Negrin]

Thanks Bryan and Pine.

My feeling is that there are many many new interfaces and form factors
emerging right now and we should be cautious about adoption. For example
Facebook's instant articles, apple news and even snapchat have similar
offerings the AMP.

They all seem to be focusing on article speed in a landscape where most
pages are larded up with a variety of trackers, ads and other scripts
(which we don't have, although we have our own challenges on performance)
with the ultimate goal of owning the delivery platform.

I'm nervous about picking winners in such a landscape although I'm excited
about prototypes like things like the Apple Watch app that came out of the
Lyon hackathon. I feel like a slow follower model where we see which
solution if any becomes widely used is more appropriate for us.

-Toby

On Thursday, October 8, 2015, Pine W  wrote:

> Hi Bryan,
>
> Ah, I was thinking of the 2 different mobile web editing experiences (not
> 2 different apps) for Android depending on form factor. My understanding is
> that tablets have VE enabled on mobile web now (I have yet to try it) while
> phones do not have VE enabled on mobile web yet.
>
> Pine
> On Oct 8, 2015 12:56 PM, "Bryan Davis"  > wrote:
>
>> On Thu, Oct 8, 2015 at 1:32 PM, Pine W > > wrote:
>> > We currently have at least 6 channels, I believe:
>> >
>> > 1. Desktop Web
>> > 2. Mobile Web
>> > 3. Android phone
>> > 4. Android tablet
>>
>> I don't think that we have separate native apps for the phone and
>> tablet form factors.
>>
>> > 5. IPhone
>> > 6. Legacy Android phone
>> >
>> > I'm no expert on mobile developmemt, but perhaps WMF could experiment
>> with
>> > Google's idea on just one channel to start?
>>
>> AMP would only be appropriate for the mobile web channel from the list
>> above. Implementing it would be a matter of placing some sort of
>> translating proxy between MediaWiki and the requesting user agent that
>> downgraded the HTML produced by MediaWiki to AMP's restricted HTML
>> dialect. That sort of translation might be possible in MobileFrontend
>> but it would likely be accomplished much more easily using some other
>> tech stack that had good support for manipulation of HTML like a
>> node.js service. It might be an interesting prototype project for a
>> volunteer to experiment with a frontend app that consumed the RESTBase
>> provided Parsoid HTML (e.g.
>> https://en.wikipedia.org/api/rest_v1/page/html/NOFX) and spit out AMP
>> compliant documents.
>>
>> The only other option really to produce alternate HTML from MediaWiki
>> would require swapping out the existing layer that translates an
>> article's wikitext to HTML with a version that spoke AMP instead. That
>> would be related to https://phabricator.wikimedia.org/T114194.
>>
>> Bryan
>> --
>> Bryan Davis  Wikimedia Foundation> >
>> [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
>> irc: bd808v:415.839.6885 x6855
>>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Readership metrics for the week until September 13, 2015

[Toby Negrin]

Hi Tilman --

Thank you for sending this out! I appreciate the hard work that you put
into it and I'm excited to have these metrics close at hand.

-Toby

On Thu, Sep 17, 2015 at 12:44 PM, Tilman Bayer  wrote:

> Hi all,
>
> with this email we are starting a weekly look at our most important
> readership metrics.
>
> The main purpose is to raise awareness about how these are developing,
> call out the impact of any unusual events in the preceding week (e.g. the
> media promotion for the Android app this time) and facilitate thinking
> about core metrics in general.
>
> We will iterate on the presentation (e.g. to better take seasonality into
> account, in particular including year-over-year comparisons) and eventually
> want to create dashboards for those which are not already available in that
> form already. Feedback and discussion welcome.
>
> (All numbers below are averages for September 7-13, 2015 unless otherwise
> noted.)
>
> Pageviews:
>
> Total: 546 million/day
>
> Context (April 2015-September 2015):
>
> [image: Wikimedia daily pageviews, all vs. mobile (April 2015-).png]
>
> After the drop in June, which by now looks not merely seasonal but likely
> to be at least partially connected to the rollout of HTTPS-only access
> begun on June 12, overall pageviews are slightly rising again recently.
> (Notably, the recent drop
>  in comScore’s
> numbers - also in their pageview estimates for Wikimedia sites, not
> reproduced in that report card - is not consistent with our own traffic
> data; these discrepancies are being looked into.)
>
> Desktop: 58.8%
>
> Mobile web: 39.9%
>
> Apps: 1.2%
>
>
> Global North ratio: 77.5% of total pageviews
>
> Context (April 2015-September 2015):
>
> [image: Wikimedia pageviews, Global South vs. Global North (April
> 2015-).png]
>
>
> Unique app users
>
> Android: 1.136 million /day
>
> Context (January 2015-September 2015):
>
> While this number is slightly higher than in the preceding week, there’s
> no noticeable effect visible yet from the media promotion for the Android
> app (blog post
> 
> on September 10, media coverage
> 
> on September 10, 11 and 13).
>
>
> iOS: 290k / day
>
>
> Context (January 2015-September 2015):
>
> New app installations
>
> Android: 40,168/day (Daily installs per device, from Google Play,
> September 7-11)
>
> Context (September 2014-September 2015):
>
> Unfortunately, the stats function of the Google Play is having issues
> currently and data for recent days has been delayed. (They “expect to
> resolve the issue shortly”, but the September 11 only became available this
> morning and I’m sending this report out now, a fuller assessment of the
> impact of the media campaign will need to wait.) The first two days after
> the blog post went out on September 10 did not yet show a marked increase:
>
> 20150911
>
> 40648
>
> 20150910
>
> 39862
>
> 20150909
>
> 39927
>
> 20150908
>
> 39981
>
> 20150907
>
> 40420
>
>
> iOS: 5,262/day (download numbers from App Annie)
>
> Context (September 2014-September 2015):
>
> We seem to have a slight upwards trend in recent weeks, but it’s still way
> below the download rate a year ago.
>
> 
>
> For reference, the queries and source links used are listed below (access
> is needed for each). I’ll also see to upload charts to Commons.
>
> hive (wmf)> SELECT SUM(view_count)/700 AS avg_daily_views_millions
> FROM wmf.projectview_hourly WHERE agent_type = 'user' AND
> CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-09-07"
> AND "2015-09-13";
>
> hive (wmf)> SELECT year, month, day,
> CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date,
> sum(IF(access_method <> 'desktop', view_count, null)) AS mobileviews,
> SUM(view_count) AS allviews FROM wmf.projectview_hourly WHERE year=2015 AND
> agent_type = 'user' GROUP BY year, month, day ORDER BY year, month, day
> LIMIT 1000;
>
> hive (wmf)> SELECT SUM(IF (FIND_IN_SET(country_code,
> 'AD,AL,AT,AX,BA,BE,BG,CH,CY,CZ,DE,DK,EE,ES,FI,FO,FR,FX,GB,GG,GI,GL,GR,HR,HU,IE,IL,IM,IS,IT,JE,LI,LU,LV,MC,MD,ME,MK,MT,NL,NO,PL,PT,RO,RS,RU,SE,SI,SJ,SK,SM,TR,VA,AU,CA,HK,MO,NZ,JP,SG,KR,TW,US')
> > 0, view_count, 0))/SUM(view_count)  FROM wmf.projectview_hourly WHERE
> agent_type = 'user' AND
> CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-09-07"
> AND "2015-09-13";
>
> hive (wmf)> SELECT access_method, SUM(view_count)/7 FROM
> wmf.projectview_hourly WHERE agent_type = 'user' AND
> CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-09-07"
> AND "2015-09-13" GROUP BY access_method;
>
> hive (wmf)> SELECT SUM(IF(platform = 'Android',unique_count,0))/7 AS
> avg_Android_DAU_last_week, SUM(IF(platform = 'iOS',unique_count,0))/7 AS
> avg_iOS_DAU_last_week FROM wmf.mobile_apps_uniques_daily WHERE
> 

Re: [WikimediaMobile] Fwd: [reading-wmf] interesting topic readouts

[Toby Negrin]

Hi Jon --

I created a ticket to track your request. (
https://phabricator.wikimedia.org/T106451) -- we have some directional data
from a 2104 study that indicates that users read articles that focus on
entertainment (http://www.dcs.gla.ac.uk/~mounia/Papers/wiki.pdf)

As far as the taxon counts -- there are a few wikis that are more open than
others to automatically created articles. I don't think there's much of a
relationship beyond that.

-Toby



On Mon, Jul 20, 2015 at 10:33 AM, Jon Robson  wrote:

> So basically as a project grows the percentage of taxon articles go down?
> :)
> It would be interesting to see equivalents of these for readership.
> Are there any initiatives to measure page views based on wikidata
> instance of property value? I'd love to know whether readership
> figures reflect content available.
>
> On Thu, Jul 16, 2015 at 2:34 PM, Adam Baso  wrote:
> > Fun visualizations!
> >
> > -- Forwarded message --
> > From: Toby Negrin 
> > Date: Thu, Jul 16, 2015 at 11:58 AM
> > Subject: [reading-wmf] interesting topic readouts
> >
> > 
> >
> > https://www.wikidata.org/wiki/Wikidata:Statistics/Wikipedia
> >
> >
> > ___
> > Mobile-l mailing list
> > Mobile-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
>
>
>
> --
> Jon Robson
> * http://jonrobson.me.uk
> * https://www.facebook.com/jonrobson
> * @rakugojon
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] New Android production release

[Toby Negrin]

Hi Pine --

Thanks for the suggestion! We are in fact planning on running a test where
we prompt app installations via banner to a small audience -- we'd like to
understand how effective these banners are and will they continue to use
the app once it is installed.

It's important for us to understand how our readers will react to such
banners before we make larger scale commitments.

-Toby

On Wed, Jul 15, 2015 at 4:06 PM, Pine W  wrote:

> Hi Dmitry,
>
> How about promoting the app to Mobile Web users and on the desktop site
> with occasional watchlist notices? Also, perhaps Fundraising or Research
> would let you send occasional emails (quarterly at most) to their email
> lists?
>
> Pine
>
> Pine
>
>
> On Wed, Jul 8, 2015 at 12:58 PM, Dmitry Brant 
> wrote:
>
>> Hi Pine,
>>
>> We usually work with Comms when we have a significant new feature in the
>> apps that we want to promote, and Comms has done a great job so far of
>> notifying all the various tech news outlets to pick up the story (for
>> example[1]).  The app is also fairly easily discoverable within the Play
>> Store itself, although we could probably benefit from some SEO to make the
>> app rank higher for different search terms.
>> Are there additional venues for spreading the word about the apps that
>> you would suggest?
>>
>> [1]
>> http://techcrunch.com/2015/01/15/wikipedia-rolls-out-a-redesigned-mobile-app/
>>
>>
>>
>> On Wed, Jul 8, 2015 at 2:34 PM, Pine W  wrote:
>>
>>> Thanks Dmitry. Is WMF Comms going to market product updates like this?
>>> One item of feedback on the Strategic Plan was a request for a Wikipedia
>>> app, suggesting a lack of public awareness about the existing apps.
>>>
>>> Pine
>>> On Jul 8, 2015 7:30 AM, "Dmitry Brant"  wrote:
>>>
 Hi everyone,

 We've released a new version of the production Wikipedia Android app
 [1][2], which is currently rolling out to all Play Store users today. This
 is mostly a maintenance release, with a few welcome visual enhancements.
 Here's an abridged list of the updates in this release:

 * Enlarged images when browsing articles
 * Improved "read more" suggestions at the bottom of articles
 * Enabled "Search Wikipedia" when sharing text from other apps
 * Added system language support & Chinese dialects to Wikipedia
 language picker
 * Improved appearance and consistency of article lists (History, Saved
 Pages, etc.)
 * Improved text alignment for mixed left-to-right and right-to-left
 languages
 * Improved page caching
 * Added link to app FAQ in the "More" menu
 * Various miscellaneous fixes and enhancements [3]

 Stay tuned for future updates! We have some big things in store for our
 next release. You won't want to miss it!

 Best,

 Dmitry Brant
 Mobile apps team (Android)
 Wikimedia Foundation
 https://www.mediawiki.org/wiki/Wikimedia_Apps/Team

 [1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
 [2]
 https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.0.105-releasesprod-2015-06-30.apk
 [3] https://phabricator.wikimedia.org/T103788


 ___
 Mobile-l mailing list
 Mobile-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/mobile-l


>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikipedia apps pre-installations

[Toby Negrin]

Thanks Adam.

Hi Pine -- we'll be as open as we can about such partnerships but keep in
mind that the world of carriers and device manufacturers is very different
in terms of communications than ours. It's unlikely that any partner we
have will allow us to share information before the press release is out.
It's unfortunate but that's how that world works.

-Toby

On Wed, Jul 15, 2015 at 7:56 AM, Adam Baso  wrote:

> Hi Pine,
>
> Thanks for the message. I'll link you up with a contact in partnerships
> who may be able to respond to your question.
>
> Thanks again!
> -Adam
>
> On Tue, Jul 14, 2015 at 9:24 PM, Pine W  wrote:
>
>> Hi Mobile folks,
>>
>> Any progress on this, particularly with any of the largest phone and
>> tablet manufacturers and resellers?
>>
>> Thanks,
>> Pine
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] deep-linking in apps

[Toby Negrin]

Thanks for quick answers folks!

Brian -- is there a phab ticket for the iOS work?

-Toby

On Mon, Jul 13, 2015 at 8:47 AM, Dmitry Brant  wrote:

> For the Android app, we do indeed. If you look at the HTML of any wiki
> article, you'll notice an "alternate" link in the  tag that looks
> like this:
>
> 
>
> This is a deep link that tells Google that it's possible to open this page
> in our Android app.
>
>
> On Mon, Jul 13, 2015 at 11:28 AM, Toby Negrin 
> wrote:
>
>> Do we support any deep-linking[1] scheme for our apps? I know that we've
>> made some steps in integrating with google search on this but I don't know
>> what our general approach.
>>
>> thanks,
>>
>> -Toby
>>
>> [1] https://en.wikipedia.org/wiki/Mobile_deep_linking
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] deep-linking in apps

[Toby Negrin]

Do we support any deep-linking[1] scheme for our apps? I know that we've
made some steps in integrating with google search on this but I don't know
what our general approach.

thanks,

-Toby

[1] https://en.wikipedia.org/wiki/Mobile_deep_linking
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Mobile-Apps' "Unbreak now" tasks in Phabricator

[Toby Negrin]

Thanks Brian -- I just pinged Monte since his name was on them.

-Toby

On Mon, Jul 6, 2015 at 3:40 PM, Brian Gerstle 
wrote:

> I closed the iOS ones, which were already in the "Done" column in Phab 2
> sprints ago.  Sorry for the confusion, still grappling w/ task state
> transitions vs. columns.
>
> On Mon, Jul 6, 2015 at 6:10 PM, Andre Klapper 
> wrote:
>
>> Hi,
>>
>> could the Apps Team please update their open tasks with "Unbreak Now!"
>> priority [1] in Phabricator's "Mobile-App-Sprint-58-iOS" project?
>>
>> https://phabricator.wikimedia.org/maniphest/query/40ps.K.br_Ri/#R
>>
>> That Sprint ended one month ago and all remaining tasks are in the
>> "Done" column.
>>
>> Thanks in advance,
>> andre
>>
>> [1] "Something is broken and needs to be fixed immediately" as per
>>
>> https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities
>> --
>> Andre Klapper | Wikimedia Bugwrangler
>> http://blogs.gnome.org/aklapper/
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>
>
>
> --
> EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle
> IRC: bgerstle
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android app bug report template

[Toby Negrin]

Should we link from the app itself?

On Mon, Jul 6, 2015 at 12:19 PM, Bernd Sitzmann  wrote:

> Toby,
>
> This is on mobile-l. Did you have any other distribution list in mind?
>
> Cheers,
> Bernd
>
> On Mon, Jul 6, 2015 at 1:14 PM, Toby Negrin  wrote:
>
>> Nice Bernd -- is this appropriate to share with community?
>>
>> -Toby
>>
>> On Mon, Jul 6, 2015 at 10:56 AM, Jon Katz  wrote:
>>
>>> awesome, Bernd!
>>>
>>> On Mon, Jul 6, 2015 at 10:07 AM, Bernd Sitzmann 
>>> wrote:
>>>
>>>> https://phabricator.wikimedia.org/T104086 is a bug report template for
>>>> Android issues.
>>>> The easiest way to file a new bug is to go there and click on the link
>>>> to file a pre-populated Phab ticket. Most of the time the "regular" one is
>>>> what you need. If you fill out bugs coming from OTRS or crash reports then
>>>> use the second one.
>>>>
>>>> You can also find this template in the last column of our Android
>>>> workboard[1].
>>>>
>>>> Cheers,
>>>> Bernd
>>>>
>>>> [1] https://phabricator.wikimedia.org/tag/wikipedia-android-app/
>>>>
>>>>
>>>>
>>>> ___
>>>> Mobile-l mailing list
>>>> Mobile-l@lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>>
>>>>
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android app bug report template

[Toby Negrin]

Nice Bernd -- is this appropriate to share with community?

-Toby

On Mon, Jul 6, 2015 at 10:56 AM, Jon Katz  wrote:

> awesome, Bernd!
>
> On Mon, Jul 6, 2015 at 10:07 AM, Bernd Sitzmann 
> wrote:
>
>> https://phabricator.wikimedia.org/T104086 is a bug report template for
>> Android issues.
>> The easiest way to file a new bug is to go there and click on the link to
>> file a pre-populated Phab ticket. Most of the time the "regular" one is
>> what you need. If you fill out bugs coming from OTRS or crash reports then
>> use the second one.
>>
>> You can also find this template in the last column of our Android
>> workboard[1].
>>
>> Cheers,
>> Bernd
>>
>> [1] https://phabricator.wikimedia.org/tag/wikipedia-android-app/
>>
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [reading web] Phabricating in Q1

[Toby Negrin]

I don't have a ton of direct feedback on this except that the documentation
is great. I still need to go ask people about where to find things and I
can imagine if I'm confused, other people, particularly in the community
are confused as well.

It's hard to balance the needs of developers with being transparent and
easily understood; the docs are a good start.

-Toby

On Wed, Jul 1, 2015 at 4:24 AM, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:

> And here's a "stop, laugh, relax" break email:
>
> https://media1.giphy.com/media/u75DtEmmyS0fK/200.gif
>
> https://media0.giphy.com/media/sYHOVHt74OWas/200.gif
>
> On Wed, Jul 1, 2015 at 1:20 PM, Joaquin Oltra Hernandez <
> jhernan...@wikimedia.org> wrote:
>
>> Regarding Jon's caveats (responses inline):
>>
>> * Anyone can edit the priority field. I don't know of any cases of
>>> someone switching from some kind of priority to 'needs triage' ever
>>> happens though so this shouldn't be a problem.
>>>
>>
>> That's true for everything we do because everything is public. Most
>> intervention I see from external stakeholders is commenting, adding related
>> projects and occasionally editing description and title (which of those,
>> the edit is usually good).
>>
>> The good things we get by making priority field a part of our workflow
>> are:
>>
>>- Phab integration: Querys, batch edits, colors on cards.
>>- Integration with the rest of the organization (which to my
>>understanding use priorities heavily).
>>- Any changes by anybody are logged in the task. You can see who did
>>what.
>>
>> All these are things we don't have with *only columns and sorting
>> columns*. Well we get column changes logged in the task, but we don't get 
>> *sort
>> order* changes logged in the card, which is what worries me the most.
>>
>> Anybody can change the sort order of the columns and nothing is logged.
>> There is no way to see if a task was not important but it is now. Or the
>> reverse.
>>
>> To me *only* relying in column sort order is just damaging to our
>> process. A combo of priority and column sort would seem ideal to me.
>>
>> * Some tasks may get lost when they are not filed against an extension.
>>> eg. Adding a card in a sprint but not with the associated extension
>>> https://phabricator.wikimedia.org/maniphest/query/gdeZ0Re2Ekmh/#R
>>> OR Tasks in reading web but not in the extension pages
>>> https://phabricator.wikimedia.org/maniphest/query/BuWVMgcwb1kM/#R
>>> (but I think we can train ourselves to avoid that)
>>
>>
>> If I'm correct this is a problem we already have, and we don't have a
>> clear workflow for it.
>>
>> My proposal is having clear rules of where tasks are (in the software
>> project they belong) and stay vigilant in just *current sprint* and
>> *overview board* to move to needs triage+software project any tasks that
>> pop in there.
>>
>> In any case with, what we are doing now, we should probably set strict
>> rules about what get's added into the sprint and where to report bugs,
>> since we don't have any agreement now.
>>
>> ---
>>
>> Keep your minds open, I'm not actually proposing any huge changes, and
>> these "flows" should bring us closer to how the rest of the organization
>> works (if I'm not totally mistaken).
>>
>> On Wed, Jul 1, 2015 at 1:08 PM, Joaquin Oltra Hernandez <
>> jhernan...@wikimedia.org> wrote:
>>
>>> I thought we had come to a different conclusion: that we would continue
 with the existing system for a sprint cycle for you to see how the system
 works before you change it.  Maybe I am misunderstanding.

>>>
>>> I said *considering adopting* and no dates, which is compatible with
>>> what we talked about [image: 😄].
>>>
>>>
 If I'm not misunderstanding, please remember Kristen is a stakeholder
 on this and it impacts how she does her job, so any changes really do need
 her buy-in.
>>>
>>>
>>> I've contacted KL and asked her for further thoughts, so that we can
>>> keep the conversation rolling. She's always on my mind [image: 😜]
>>>
>>> ---
>>>
>>> Seriously though, there aren't any super-radical changes or anything
>>> crazy. Just clearly stablishing the workflow and trying to do our jobs the
>>> best we can.
>>>
>>> The biggest philosophical change would be having mobile's product
>>> backlog on mobile frontend and gather's product backlog on Gather, which
>>> we've already done in the past and worked fine.
>>>
>>> On Tue, Jun 30, 2015 at 10:49 PM, Jon Robson 
>>> wrote:
>>>
 Hi Joaquin
 I'm still not 100% sure how the query will work for us but I'm all for
 trying this out.

 A few caveats to be aware of:
 * Anyone can edit the priority field. I don't know of any cases of
 someone switching from some kind of priority to 'needs triage' ever
 happens though so this shouldn't be a problem.
 * Some tasks may get lost when they are not filed against an extension.
 eg. Adding a card in a sprint but not with the associated extension
>

Re: [WikimediaMobile] Skins Usage Data

[Toby Negrin]

And just to be clear -- everybody who has browsed the site but has not
logged in (i.e. the vast majority of our readers) will be using Vector?

thanks for putting this together.

-Toby

On Mon, Jun 29, 2015 at 2:47 PM, Gergo Tisza  wrote:

> On Mon, Jun 29, 2015 at 11:16 AM, Adam Baso  wrote:
>
>> I think it was Joaquin, Sam, and Bryan with whom I discussed relative
>> skins usage on some popular skins, in the context of which skins Reading is
>> on the hook for in the sense of full maintenance or high priority fixes
>> (even if only coordinating) when issues arise. Here's that data, based on
>> some queries Timo ran recently (thanks, Timo!).
>>
>> * en.wikipedia.org, users active since 2015-01-01, skin=cologneblue: 7k
>> users.
>> * en.wikipedia.org, users active since 2015-01-01, skin=monobook: 193k
>> users.
>> * en.wikipedia.org, users active since 2015-01-01: 3.1m users.
>>
>> * en.wikipedia.org, users active since 2015-03-01, skin=cologneblue: 6k
>> users.
>> * en.wikipedia.org, users active since 2015-03-01, skin=monobook: 179k
>> users.
>> * en.wikipedia.org, users active since 2015-03-01: 2.3m users.
>>
>> * commons.wikimedia.org, users active since 2015-03-01,
>> skin=cologneblue: 1k users.
>> * commons.wikimedia.org, users active since 2015-03-01, skin=monobook:
>> 59k users.
>> * commons.wikimedia.org, users active since 2015-03-01: 687k users.
>>
>
> Expect the ratio of users with obscure configuration settings to sharply
> rise when you look at groups with higher activity. E.g. a year ago, when I
> looked up various stats for the MediaViewer launch, non-Vector usage was 5%
> for users who edited Wikipedia in the last 30 days, and 15% for those who
> made at least 100 edits in the last 30 days. Non-Monobook usage also grows
> (over a percent for very active editors).
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [video club] RailsConf 2015 - Implementing a Strong Code Review Culture

[Toby Negrin]

Thanks for posting this Sam -- code review is one of the best parts of our
engineering culture, I'll definitely watch this when I get a chance.

-Toby

On Mon, Jun 29, 2015 at 7:59 AM, Sam Smith  wrote:

> Hey y'all,
>
> I watch a lot of talks in my downtime. I even post the ones I like to a
> Tumblr… sometimes [0]. I felt like sharing Derek Prior's "Implementing a
> Strong Code Review Culture" from RailsConf 2015 in particular because it's
> relevant to the conversations that the Reading Web team are having around
> process and quality. You can watch the talk on YouTube [1] and, if you're
> keen, you can read the paper that's referenced over at Microsoft Research
> [2].
>
> I particularly like the challenge of providing two paragraphs of context
> in a commit message – to introduce the problem and your solution – and
> trying to overcome negativity bias in written communication* by offering
> compliments whenever possible and asking, not telling, while providing
> critical feedback.
>
> I hope you enjoy the talk as much as I did.
>
> –Sam
>
> [0] http://sometalks.tumblr.com/
> [1] https://www.youtube.com/watch?v=PJjmw9TRB7s
> [2] http://research.microsoft.com/apps/pubs/default.aspx?id=180283
>
> * The speaker said "research has shown" but I didn't see a citation
>
> *Notes (width added emphasis)*
>
>- Code review isn't for catching bugs
>- "Expectations, Outcomes, and Challenges of Modern Code Review"
>- Chief benefits of code review:
>   - Knowledge transfer
>   - Increased team awareness
>   - Finding alternative solutions
>- Code review is "the discipline of explaining your code to your peers"
>- Process is more important than the result
>- Goes on to define code review as "the discipline of discussing your
>code with your peers"
>- If we get better at code review, then we'll get better at
>communicating technically as a team
>
> Rules of Engagement
>
>- As an author, provide context
>
>
>- "If content is king, then context is God"
>   - *In a pull request (patch set) the code is the content and the
>   commit message is the context*
>   - Provide sufficient context - bring the reviewer up to speed with
>   what you've been doing in the past X hours
>   - *Challenge: provide at least two paragraphs of context in your
>   commit message*
>   - This additional context lives on in the commit history whereas
>   links to issue trackers might not
>
>
>- As a reviewer, ask questions rather than making demands
>   - Research has shown that there's a negativity bias in written
>   communication. *Offer compliments whenever you can*
>   - *When you need to provide critical feedback, ask, don't tell*,
>   e.g. "extract a service to reduce some of this duplication" could be
>   formulated as "what do you think about extracting a service to reduce 
> some
>   of this duplication?"
>  - "Did you consider?", "can you clarify?"
>  - "Why didn't you just..." is framed negatively and includes the
>  word just
>   - Use the Socratic method: asking and answering questions to
>   stimulate critical thinking and to illuminate ideas
>
> Insist on high quality reviews, but agree to disagree
>
>- Conflict is good. *Conflict drives a higher standard of coding
>provided there's healthy debate*
>- Everyone has a minimum bar to entry for quality. Once that bar is
>met, then everything else is a trade-off
>- Reasonable people disagree all the time
>- Review what's important to you
>- SRP (Single Responsibility Principle) (the S from SOLID)
>   - Naming
>   - Complexity
>   - Test Coverage
>   - ... (whatever else you're comfortable in giving feedback on)
>
>
>- What about style?
>   - Style is important
>   - "People who received style comments on their code perceived that
>   review negatively"
>   - Adopt a styleguide
>
>
> Benefits of a Strong Code Review Culture
>
>- Better code
>- Better developers through constant knowledge transfer
>- Team ownership of code, which leads to fewer silos
>- Healthy debate
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] iOS Beta 4.1.5 available for testing

[Toby Negrin]

Hi Corey -- what's the version #? 4.1.5(143)?

On Thu, Jun 11, 2015 at 9:11 AM, Corey Floyd  wrote:

> Hey everyone, we have a new iOS release in the hopper. If you are part of
> the beta channel, you can download the new version using Apple's TestFlight.
>
> If you would like to be in the beta, just email me, Brian or Monte to get
> access.
>
> Here are the highlights of this release:
>
> * Lead images now load faster and fade in smoothly
> * More article layout improvements
> * More reliable loading of articles from the cache
> * Added a link to the FAQ in Settings > More
> * Fix crash on startup for some device languages (Like Norwegian)
> * Several other crash fixes
>
> Also of note: this our last "scheduled" iOS 6 release. After release, this
> version will be available for download indefinitely for our users who are
> unable to upgrade to iOS 7.
>
> For users who are running  iOS 7 or higher, this will allow us to support
> more great features in future versions of the iOS application.
>
> Thanks for testing and please send us any feedback you may have!
>
> --
> Corey Floyd
> Software Engineer
> Mobile Apps / iOS
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Task/bug naming conventions

[Toby Negrin]

I've always used "enhancement" for this purpose -- does phabricator
actually support this?

On Mon, Jun 8, 2015 at 10:33 AM, Gergo Tisza  wrote:

> Hi all,
>
> I would like to recommend a naming convention that clearly differentiates
> between existing and wanted behavior. This is something that has been
> confusing for me for a while - bugs and tasks are both in the indicative so
> I often have trouble deciding whether a ticket describes a situation that
> exists but should not or one that does not exist but should.
>
> Random example from current sprint board: "Anon users can access public
> view from main menu" with the associated description being "When anonymous
> and I click collections I am taken to the public view." Does this mean that
> anonymous users should not be able to access the public view but somehow
> they can, or is this the description of a wanted feature? I can figure it
> out by digging up context, of course, but that takes time; ideally, this
> should be clear from just the task title (which I might be seeing in a list
> or on a workboard).
>
> I think it would be clearer if the title of the task would always
> reflected the situation at the time of creating the task, and titles
> describing a wanted but not currently existing state were phrased as
> imperatives. So if anons can see the public view right now and that's a bug
> the title would say "anons can access public view"; if they cannot access
> it currently but that's a feature we want, the title would say "anons
> should be able to access public view" or "make anons able to access public
> view".
>
> Thoughts?
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] iOS 4.1.4 is live

[Toby Negrin]

Nice work! Just downloaded and I'm impressed with the performance as well
as the polish. Keep up the good work!

-Toby

On Tue, Jun 2, 2015 at 11:16 AM, Corey Floyd  wrote:

> This version has a lot of visual updates, performance improvements, and
> bug fixes - we even tweaked the icon. Overall this is a pretty nice release
> that applies some much needed polish in a lot of places.
>
> Please check it out when you get a chance and let us know what you think.
>
> https://itunes.apple.com/us/app/wikipedia-mobile/id324715238?mt=8
>
> --
> Corey Floyd
> Software Engineer
> Mobile Apps / iOS
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [iOS][Apps] Wikipedia Mobile 4.1.3 for iOS

[Toby Negrin]

Congrats team -- great work.

-Toby

On Wed, May 13, 2015 at 2:44 PM, Corey Floyd  wrote:

> Hey everyone…
>
> The latest for iOS is live on the app store. You can download it here:
> https://itunes.apple.com/us/app/wikipedia-mobile/id324715238?mt=8
>
> We are continuing our quest to squash bugs and tighten up the screws, but
> you’ll see a few new features in there as well.
>
> This also represents our 3rd release in just over a month after a nearly 4
> month drought - our release pipeline in full effect! Automated builds +
> Crash Reporting + Phabricator Tasks FTW!
>
> Please check it out if you get a chance and let us know what you think -
> mailing list, in app feedback, or an app store review - all are appreciated!
>
> Thanks for reading!
>
> --
> Corey Floyd
> Software Engineer
> Mobile Apps / iOS
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Wikipedia Lite app?

[Toby Negrin]

Hi Dan -- did you get a chance to write up your findings?

thanks,

-Toby

On Fri, Feb 6, 2015 at 1:46 PM, Tomasz Finc  wrote:

> I'll be eager to see you guys write up your findings after the spikes are
> over.
>
> thanks for moving that forward.
>
> --tomasz
>
> On Tue, Feb 3, 2015 at 3:05 AM, Gautam Chandna  wrote:
> > OEMs care about the size of their OS, as this is stored in a restricted
> > read-only area (unless a device is rooted). Once the device is running,
> > those limitations don't apply as an app has tons of space to update
> itself.
> >
> > Quite like the network installer concept for desktop applications, OEMs
> > prefer if the pre-install is a small package that in itself doesn't
> > necessarily do much other than download the real app.
> >
> >
> >
> > On Tue, Feb 3, 2015 at 12:48 AM, Yuri Astrakhan <
> yastrak...@wikimedia.org>
> > wrote:
> >>
> >> Don't preload apps still get over-the-air updates, often the whole app
> >> re-download?
> >>
> >> On Tue, Feb 3, 2015 at 12:39 AM, Carolynne Schloeder
> >>  wrote:
> >>>
> >>> Hi, yes app size and yes optimization :-)
> >>>
> >>> App size does matter
> >>> OEM's are sensitive to the size of the app for preload. They were
> >>> satisfied with our last version that was under 3MB; we'll find out
> what they
> >>> will tolerate. And we will likely push appstore promotion as part of
> our
> >>> deep dive.[1]
> >>>
> >>> Couple of thoughts on optimization:
> >>> Yuri already worked to compress images on mobile web, only deployed on
> >>> zero partners so far. Rolling out the image compression could be an
> easy
> >>> start to reduce the page load.
> >>>
> >>> In a couple of weeks, we will get into Facebook/Ericsson's network
> >>> simulation lab in Menlo Park, where we can experience our UX on low end
> >>> devices and slow networks.
> >>>
> >>> Dan and Maryana, can you help me organize who should go to the lab?
> >>>
> >>> Thanks --
> >>>
> >>> Carolynne
> >>>
> >>> [1] The Wikipedia Zero team is getting together with product, UX, comms
> >>> and GLEE to go deep in one country, to understand the context for
> Wikipedia
> >>> usage and how we can unlock growth in underserved market segments -
> beyond
> >>> just making data free. More info in our QR notes.
> >>>
> >>>
> >>> On Mon, Feb 2, 2015 at 1:59 PM, Dan Garry 
> wrote:
> >>>>
> >>>> On 1 February 2015 at 14:48, Toby Negrin 
> wrote:
> >>>>>
> >>>>> Dan -- can you please limit the scope to sizing the android app? I
> >>>>> think that's more relevant to reaching people in the developing
> world.
> >>>>
> >>>>
> >>>> I think that depends. In a world where we're focussing on preloads,
> the
> >>>> size of the app is pretty immaterial as the user isn't paying the
> cost for
> >>>> downloading it. In that world, the best optimisations to make are
> probably
> >>>> reducing network traffic and improving performance on slower devices,
> things
> >>>> where there's lot of room for improvement in our code base. Also, our
> >>>> Android app is also an order of magnitude smaller than Facebook's
> Android
> >>>> app, so that's less of an issue for us. Facebook evidently decided to
> TACKLE
> >>>> ALL THE THINGS with Facebook Lite.
> >>>>
> >>>>> Also, can you see what percent of our GS traffic uses 2.3? Google has
> >>>>> it at about 10% globally but we need to understand our target market
> better.
> >>>>> You might also want to check in with your new contact at App Annie
> to see if
> >>>>> they have useful GS data.
> >>>>
> >>>>
> >>>> Absolutely.
> >>>>
> >>>> Dan
> >>>>
> >>>> --
> >>>> Dan Garry
> >>>> Associate Product Manager, Mobile Apps
> >>>> Wikimedia Foundation
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Carolynne Schloeder
> >>> Director Global Mobile Partnerships
> >>> Wikimedia Foundation
> >>> +14154077071
> >>> skype: cschloeder
> >>>
> >>> ___
> >>> Mobile-l mailing list
> >>> Mobile-l@lists.wikimedia.org
> >>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>
> >>
> >>
> >> ___
> >> Mobile-l mailing list
> >> Mobile-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>
> >
> >
> >
> > --
> > Gautam Chandna | Director - Technical Partner Management |
> gaut...@opera.com
> > | +47-4567-1789
> >
> > ___
> > Mobile-l mailing list
> > Mobile-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Luis van Ahn/crowdsourcing

[Toby Negrin]

Luis is also reaching out. Could you see where he's at?


> On Feb 6, 2015, at 13:52, Tomasz Finc  wrote:
> 
> I spoke with them at Google I/O many months back and they would love
> to talk more. Let me reach out again.
> 
> --tomasz
> 
>> On Thu, Jan 29, 2015 at 9:39 AM, Maryana Pinchuk  
>> wrote:
>> We've been talking about this guy for ages (and I think roughly half the
>> mobile team uses Duolingo at this point) – wasn't someone going to try to
>> put us in touch? :)
>> 
>>> On Thu, Jan 29, 2015 at 9:37 AM, Toby Negrin  wrote:
>>> 
>>> Some interesting links from one of the early crowdsourcing people:
>>> 
>>> http://en.wikipedia.org/wiki/Luis_von_Ahn
>>> 
>>> http://www.ted.com/talks/luis_von_ahn_massive_scale_online_collaboration?language=en
>>> 
>>> His current gig:
>>> 
>>> https://www.duolingo.com/
>>> 
>>> -Toby
>>> 
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>> 
>> 
>> 
>> --
>> Maryana Pinchuk
>> Product Manager, Wikimedia Foundation
>> wikimediafoundation.org
>> 
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>> 

___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Wikipedia Lite app?

[Toby Negrin]

Dan -- can you please limit the scope to sizing the android app? I think
that's more relevant to reaching people in the developing world.

Also, can you see what percent of our GS traffic uses 2.3? Google has it at
about 10% globally but we need to understand our target market better. You
might also want to check in with your new contact at App Annie to see if
they have useful GS data.

-Toby



On Sun, Feb 1, 2015 at 11:15 AM, Carolynne Schloeder <
cschloe...@wikimedia.org> wrote:

> Creating a separate app to optimize sounds like a good idea. We will check
> the market stats on Android versions, and I'll get the scoop from Facebook
> on their learning.
>
> I was somewhat surprised that most OEM's we've talked to are shipping
> Android 4.x even on low-priced models targeted for developing markets. But
> I'll clarify what's happening and circle back with Dan on the distribution
> plan (preload vs. appstores). I'll also catch up with Kim.
>
> I do love to see this attention given to our lower end handset users,
> thank you!
>
> Carolynne
>
> On Sun, Feb 1, 2015 at 9:30 AM, Lila Tretikov  wrote:
>
>> Dan,
>>
>> I think this is really important and thank you for highlighting this.
>>
>> Could you do rough sizing on what it would take to get something like
>> this out? What if we did this with a pre-load?
>>
>> Carolynne -- I recommend you start reaching out to Kim as you
>> re-formulate your W0 strategy.
>>
>> Lila
>>
>> On Sat, Jan 31, 2015 at 2:36 AM, Florian Schmidt <
>> florian.schmidt.wel...@t-online.de> wrote:
>>
>>> +1 for this idea. I still have an Android 2.3 device, but the Wikipedia
>>> app (and others too) is very slow and becomes more and more unusable, while
>>> it's agreat user experience on my Android 4.4 device.
>>>
>>> If dropping 2.3 support means a faster development of the main Wikipedia
>>> app and the <2.3 users still have access to Wikipedia through a lite app
>>> (which will be faster and more usable) i would say: do it, it has
>>> advantages for both sides :)
>>>
>>> Florian
>>>
>>> Gesendet mit meinem HTC
>>>
>>> - Reply message -
>>> Von: "Dan Garry" 
>>> An: "mobile-l" , "Carolynne Schloeder" <
>>> cschloe...@wikimedia.org>, "Toby Negrin" , "Lila
>>> Tretikov" 
>>> Betreff: [WikimediaMobile] [Apps] Wikipedia Lite app?
>>> Datum: Sa., Jan. 31, 2015 06:45
>>>
>>> Hi everyone,
>>>
>>> Those of you who were at the Mobile quarterly review heard me mention
>>> Facebook Lite, an app that's designed especially for the developing world.
>>>
>>> Notably, their app has a lot of optimisations which make it good for
>>> users in developing world:
>>>
>>>- It's only 252kB, good for limited data plans.
>>>- It supports down to Android 2.2, good for older devices.
>>>- It's data-efficient, good for 2G connections and for people on
>>>limited data plans.
>>>
>>> From a development perspective, some advantages are:
>>>
>>>- You no longer have to support older versions of Android in your
>>>main app.
>>>- You can tailor the performance of the lite app to the older
>>>devices so it's faster.
>>>- You can tailor the features of the lite app to the developing
>>>market.
>>>
>>> So obviously there are a lot of advantages for our users if we do this.
>>> And, selfishly, I can't stress enough how much dropping Android 2.3 from
>>> our current app would speed up development. As an example, almost all of
>>> the edge cases with lead images occurred on 2.3 devices, and they required
>>> quite a lot of investigation and hacking to fix them up. Obviously we've
>>> not dropped 2.3 so far because it's a very strategically important part of
>>> our user base, which I'm sure Carolynne can attest to!
>>>
>>> I'd say that we should put some serious thought into whether we'd prefer
>>> to have a Wikipedia Lite app for the developing world, rather than our
>>> current "one app to rule them all".
>>>
>>> Comments? Questions?
>>>
>>> Dan
>>>
>>> --
>>> Dan Garry
>>> Associate Product Manager, Mobile Apps
>>> Wikimedia Foundation
>>>
>>
>>
>
>
> --
> Carolynne Schloeder
> Director Global Mobile Partnerships
> Wikimedia Foundation
> +14154077071
> skype: cschloeder
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Luis van Ahn/crowdsourcing

[Toby Negrin]

Yes -- we tried to connect him and Lila at some conference but it didn't
happen. We shall continue to try...

On Thu, Jan 29, 2015 at 9:39 AM, Maryana Pinchuk 
wrote:

> We've been talking about this guy for ages (and I think roughly half the
> mobile team uses Duolingo at this point) – wasn't someone going to try to
> put us in touch? :)
>
> On Thu, Jan 29, 2015 at 9:37 AM, Toby Negrin 
> wrote:
>
>> Some interesting links from one of the early crowdsourcing people:
>>
>> http://en.wikipedia.org/wiki/Luis_von_Ahn
>>
>> http://www.ted.com/talks/luis_von_ahn_massive_scale_online_collaboration?language=en
>>
>> His current gig:
>>
>> https://www.duolingo.com/
>>
>> -Toby
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
>
> --
> Maryana Pinchuk
> Product Manager, Wikimedia Foundation
> wikimediafoundation.org
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Luis van Ahn/crowdsourcing

[Toby Negrin]

Some interesting links from one of the early crowdsourcing people:

http://en.wikipedia.org/wiki/Luis_von_Ahn
http://www.ted.com/talks/luis_von_ahn_massive_scale_online_collaboration?language=en

His current gig:

https://www.duolingo.com/

-Toby
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

[Toby Negrin]

Let's give the database the time it needs to replicate and perform needed
validation before we start troubleshooting other issues. I'm concerned that
too many things are going on here.

Thanks to everyone who is working on this right now.

-Toby


On Wed, Apr 30, 2014 at 3:17 PM, Jon Robson  wrote:

> I've not seen any events logged on this table since 26th April. I know
> for sure there have been some since then as I triggered some on the
> 27th (I saw them in the network tab)...
> I'm using stat1003
> I just want to rule out schema validation errors.
>
> ___
> Analytics mailing list
> analyt...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Definition of Pageview for the API

[Toby Negrin]

yes -- I should say we need to give Oliver some space until Thursday to get
the data in a presentable state. But we look forward to working with you
more closely on this in the near future.

-Toby


On Mon, Apr 28, 2014 at 1:38 PM, Oliver Keyes  wrote:

> Sounds good. I'm already handling the two-API-requests problem (they
> request different sections, so it's trivial to uniformly exclude one kind).
>
>
> On 28 April 2014 13:36, Toby Negrin  wrote:
>
>> + Maryana/Oliver
>>
>> We're pulling some data for the Metrics meeting this Thursday that you
>> should be aware of. It's one of the first steps in unraveling how to define
>> a pageview (or other engagement/reach metrics)
>>
>>
>> https://meta.wikimedia.org/wiki/Research:Mobile_Metrics#Datasets_and_deliverables
>>
>> Specifically
>>
>> https://meta.wikimedia.org/wiki/Research:Mobile_Traffic/Implementation
>>
>> -Toby
>>
>>
>>
>>
>> On Mon, Apr 28, 2014 at 1:32 PM, Adam Baso  wrote:
>>
>>> Yuvi, Monte, Toby, ideas?
>>>
>>> -Adam
>>>
>>>
>>> On Mon, Apr 28, 2014 at 1:11 PM, Tomasz Finc wrote:
>>>
>>>> Adam, lets move this to a public list and engage Yuvi, Monte, and Toby
>>>> to answer your questions.
>>>>
>>>> --tomasz
>>>>
>>>> On Fri, Apr 25, 2014 at 4:55 PM, Adam Baso  wrote:
>>>> > The article loads for iOS and Android apps will no[w] both be in the
>>>> web logs.
>>>> > But I can't tell if the pageview counting code is still accurate;
>>>> also,
>>>> > there are two action=mobileview hits per page load in the apps, so it
>>>> seems
>>>> > like it may be inaccurate from my read of it.
>>>> >
>>>> > How can Analytics be engaged to straighten out the relevant section
>>>> of code?
>>>> > I think the app release dates may have been pushed out a bit more, so
>>>> it may
>>>> > not be an emergency, but I wanted to check on next steps.
>>>> >
>>>> > Here's the relevant code from my understanding:
>>>> >
>>>> >
>>>> https://github.com/wikimedia/kraken/blob/master/kraken-generic/src/main/java/org/wikimedia/analytics/kraken/pageview/PageviewFilter.java#L113
>>>> >
>>>> > I don't think action=view and action=query qualify as pageviews
>>>> anymore (at
>>>> > least without even further qualification), if they ever were. It's
>>>> possible
>>>> > the pageview counting code in the link above is only an intermediate
>>>> step in
>>>> > the qualification of hits, but until we dig into it, it's an unknown.
>>>> >
>>>> > I wonder if asking Analytics for action=view and action=query to be
>>>> removed,
>>>> > and then to disqualify 1 of the 2 URL types for the apps would make
>>>> sense.
>>>> > Or rather, asking them if it sounds okay and if we should then run it
>>>> by the
>>>> > engineering mailing list for further refinement.
>>>> >
>>>> > -Adam
>>>>
>>>
>>>
>>
>
>
> --
> Oliver Keyes
> Research Analyst
> Wikimedia Foundation
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Definition of Pageview for the API

[Toby Negrin]

+ Maryana/Oliver

We're pulling some data for the Metrics meeting this Thursday that you
should be aware of. It's one of the first steps in unraveling how to define
a pageview (or other engagement/reach metrics)

https://meta.wikimedia.org/wiki/Research:Mobile_Metrics#Datasets_and_deliverables

Specifically

https://meta.wikimedia.org/wiki/Research:Mobile_Traffic/Implementation

-Toby




On Mon, Apr 28, 2014 at 1:32 PM, Adam Baso  wrote:

> Yuvi, Monte, Toby, ideas?
>
> -Adam
>
>
> On Mon, Apr 28, 2014 at 1:11 PM, Tomasz Finc  wrote:
>
>> Adam, lets move this to a public list and engage Yuvi, Monte, and Toby
>> to answer your questions.
>>
>> --tomasz
>>
>> On Fri, Apr 25, 2014 at 4:55 PM, Adam Baso  wrote:
>> > The article loads for iOS and Android apps will no[w] both be in the
>> web logs.
>> > But I can't tell if the pageview counting code is still accurate; also,
>> > there are two action=mobileview hits per page load in the apps, so it
>> seems
>> > like it may be inaccurate from my read of it.
>> >
>> > How can Analytics be engaged to straighten out the relevant section of
>> code?
>> > I think the app release dates may have been pushed out a bit more, so
>> it may
>> > not be an emergency, but I wanted to check on next steps.
>> >
>> > Here's the relevant code from my understanding:
>> >
>> >
>> https://github.com/wikimedia/kraken/blob/master/kraken-generic/src/main/java/org/wikimedia/analytics/kraken/pageview/PageviewFilter.java#L113
>> >
>> > I don't think action=view and action=query qualify as pageviews anymore
>> (at
>> > least without even further qualification), if they ever were. It's
>> possible
>> > the pageview counting code in the link above is only an intermediate
>> step in
>> > the qualification of hits, but until we dig into it, it's an unknown.
>> >
>> > I wonder if asking Analytics for action=view and action=query to be
>> removed,
>> > and then to disqualify 1 of the 2 URL types for the apps would make
>> sense.
>> > Or rather, asking them if it sounds okay and if we should then run it
>> by the
>> > engineering mailing list for further refinement.
>> >
>> > -Adam
>>
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Analytics] Mobile and CheckUser (Was [mobile-l] Wikipedia App User Agents)

[Toby Negrin]

Hey folks -- we aren't considering changing any of the data that goes into
checkuser. That tool will be unchanged.

This discussion only concerns backend logging EventLogging and page view
analytics.

thanks,

-Toby


On Thu, Mar 27, 2014 at 3:30 PM, Dan Garry  wrote:

> Note: I speak in this thread as a volunteer checkuser, not as the product
> manager for platform. Not sending from my volunteer email address because I
> don't want to subscribe to this list on two separate email addresses. :-)
>
> The originally proposed spec (user agent to include device type and app
> version) would have been very disruptive to the workflow of checkusers,
> which relies in part on user agent data. Your proposed update (including a
> client-specific identifier with the user agent for CU), is sensible, and
> lets checkuser do their jobs of dealing with people abusing our sites
> without unnecessarily divulging personally identifying information to the
> checkusers.
>
> If any interested parties have improvements to propose, let's hear them!
>
> Thanks,
> Dan
>
>
>
>
>
>
> On 27 March 2014 14:30, James Alexander  wrote:
>
>> Speaking in my capacity as both a long term volunteer checkuser (though
>> not currently because of my work requirements) a very active work related
>> owner/user of checkuser in the LCA team [probably the most active within
>> staff], and a strong advocate for saving as little info as possible I think
>> your proposed adjustment makes sense.
>>
>> That (assuming it's done for all logged actions as you suggest) seems
>> like it would fit in to the CU requirements well while saving as little
>> information as needed on readers.
>>
>> You say that the 2nd 'edit' user agent will be sent as a separate header,
>> I imagine that would still be recorded in the read logs then, is it just
>> that it wouldn't be saved long term after the logs are processed in some
>> way to remove other headers? [That would make sense to me, but if it's
>> going to be kept in the logs as long as the user agent in the first place I
>> don't know why we wouldn't just switch was was being sent 'as' the user
>> agent].
>>
>> James
>>
>> James Alexander
>> Legal and Community Advocacy
>> Wikimedia Foundation
>> (415) 839-6885 x6716 @jamesofur
>>
>>
>> On Thu, Mar 27, 2014 at 1:45 PM, Yuvi Panda  wrote:
>>
>>> Forking since I think there are two conversations - one about the
>>> format of UA for the mobile apps and one about CheckUser requirements
>>> for anything that does edits. Having them separate would be useful.
>>>
>>> For those who do not know what CheckUser means, I recommend reading
>>> https://en.wikipedia.org/wiki/Wikipedia:CheckUser.
>>>
>>> IP address and UA are amongst the two most important pieces of info
>>> CUs have in helping prevent abuse. IP is already sortof useless with
>>> mobile networks - a lot of providers do NAT and similar things that
>>> mean that we can not remotely close to reasonably assume 1 IP = 1
>>> User, or anything remotely similar to that. UA provides more
>>> fingerprinting ability, but CU isn't the only thing that consumes UA -
>>> other parts of the infrastructure do as well.
>>>
>>> So what we need, is a way to preserve the ability to fingerprint only
>>> users making edits (no read actions!) for CU. I am sure that can be
>>> implemented without having to have a very fingerprintable UA, with
>>> simple hooks on both the App's side and on Extension:CheckUser.
>>>
>>> We could generate a simple fingerprint that's unique per device (and
>>> disconnected completely from every other device identifier) that we
>>> send only with edits (and other 'POST' actions) as a separate header.
>>> This can be processed by CU (perhaps with a hook that
>>> Extension:MobileApp can hook into) and then used by CheckUsers. This
>>> data will be treated with the same data retention / privacy policy
>>> that applies to CUs now, and regular UA data can be consumed by other
>>> consumers without too much fingerprinting concerns.
>>>
>>> I talked to hoo and he said the CU hook shouldn't be too much of a
>>> problem, and the app side of the issue is rather simple too. Deskana
>>> (speaking solely as a volunteer CU) says that this solution is
>>> acceptable to him. Thoughts other people?
>>>
>>> On Thu, Mar 27, 2014 at 10:43 PM, Oliver Keyes 
>>> wrote:
>>> > Repost, because filtering; there might be a point of confusion here
>>> that's
>>> > causing the problem. As I understand it, the user agent sanitisation is
>>> > expected to apply to EventLogging data, and data in the Analytics
>>> pipeline,
>>> > but not data streaming into MediaWiki proper - namely, the cu_changes
>>> table.
>>> > Nuria, is that the case?
>>> >
>>> >
>>> > On 27 March 2014 08:16, Nuria Ruiz  wrote:
>>> >>
>>> >> >Rather than having an ethical debate over it, we could always test
>>> the
>>> >> > actual usefulness with Science. That way we'd be able to see how
>>> much
>>> >> > granularity each additional component adds to the data.
>>> >> I kind 

Re: [WikimediaMobile] [Analytics] X-Analytics

[Toby Negrin]

Thanks Arthur


On Thu, Mar 13, 2014 at 2:36 PM, Arthur Richards wrote:

> I've responded.
>
>
> On Thu, Mar 13, 2014 at 10:36 AM, Jon Robson  wrote:
>
>> Does anyone know the answer to this question on the extension talk
>> page? If so could you reply?
>>
>> -- Forwarded message --
>> From: MediaWiki Mail 
>> Date: Thu, Mar 13, 2014 at 9:35 AM
>> Subject: MediaWiki discussion - New thread: X-Analytics/mobile tracking?
>> To: Jdlrobson 
>>
>>
>> Hi Jdlrobson,
>>
>> this is a notification from MediaWiki that a new thread on Extension
>> talk:MobileFrontend, 'X-Analytics/mobile tracking?',
>> was created on 13 March 2014 at 16:35 by Kchurch05
>>
>> You can see it at
>> <
>> http://www.mediawiki.org/w/index.php?title=Extension_talk:MobileFrontend&offset=20140313163541&lqt_mustshow=40781#X-Analytics.2Fmobile_tracking.3F_40781
>> >
>>
>> The text is:
>> We're using Piwik and Google Analytics, and currently the only way we
>> can determine whether a visitor used our wiki on a mobile device is
>> via the browser model, since we don't have a mobile URL -- and even
>> then it's not 100% accurate, since some people prefer to use the
>> desktop version of the site instead of the mobile version.
>>
>> I did a search and saw
>> [https://wikitech.wikimedia.org/wiki/X-Analytics this article] on
>> [[Analytics/Kraken/Data Formats|X-Analytics]]. I'm not a MW expert so
>> I'm not 100% clear on what X-A does, and from the code linked it seems
>> to only track whether a user is in alpha or beta mode.
>>
>> We're currently running MW 1.21 so the X-Analytics doesn't seem to be
>> included in that MobileFrontend version. Hopefully we'll upgrade ASAP,
>> but I wanted to see if this was a way to get better data on mobile
>> usage of our wiki.
>>
>> Thanks all!
>>
>>
>> --
>> Jon Robson
>> * http://jonrobson.me.uk
>> * https://www.facebook.com/jonrobson
>> * @rakugojon
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>
>
>
> --
> Arthur Richards
> Software Engineer, Mobile
> [[User:Awjrichards]]
> IRC: awjr
> +1-415-839-6885 x6687
>
> ___
> Analytics mailing list
> analyt...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Browser statistics for mobile

[Toby Negrin]

Cards are fine -- the wiki doc just tries to pull it all together.

thanks,

-Toby


On Thu, Nov 14, 2013 at 5:05 PM, Tomasz Finc  wrote:

> On Thu, Nov 14, 2013 at 4:58 PM, Toby Negrin 
> wrote:
> > Feedback on the report formats/contents would be great. We're reasonably
> > close to getting the data feeds in place.
>
> I made my edits in the cards. If you need edits elsewhere then do let
> know. I just want to make sure to keep everything in one place to
> minimize confusion.
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Browser statistics for mobile

[Toby Negrin]

Thanks Tomasz -- for reference, we're using this wiki page to track the
mobile data requests.

https://www.mediawiki.org/wiki/Analytics/Epics/Metrics_about_Mobile_Usage

Feedback on the report formats/contents would be great. We're reasonably
close to getting the data feeds in place.

thanks,

-Toby


On Thu, Nov 14, 2013 at 4:40 PM, Tomasz Finc  wrote:

> We brought this up in the annual review and Toby and I flagged two
> stories which will automate this and device breakdowns.
>
> https://mingle.corp.wikimedia.org/projects/analytics/cards/1227
>
> https://mingle.corp.wikimedia.org/projects/analytics/cards/1228
>
> Take a spin through both and modify as needed. I want us to not have
> to melt our laptops to get at this data.
>
> --tomasz
>
> On Sun, Jul 28, 2013 at 5:00 PM, Juliusz Gonera 
> wrote:
> > On 07/24/2013 02:24 PM, Tomasz Finc wrote:
> >>
> >> Tell me a little more about where they break down. --tomasz
> >
> >
> > As an example all iPhones are in one bag, be it Safari 3 or Safari 7.
> >
> > --
> > Juliusz
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l