Re: [WikimediaMobile] Beta of Wikipedia 5.0.0 for iOS

[Sjoerd de Bruin]

Hi,

Is there going to be a new list of beta testers? I was subscribed before...

Greetings,

Sjoerd de Bruin

> Op 22 dec. 2015, om 00:34 heeft Joshua Minor  het 
> volgende geschreven:
> 
> Hello,
> 
> Since last quarter the WMF’s iOS team [1] (part of the Reading product group) 
> has been working on a major version update to our iOS app [2]. Rather than 
> adding new features to the existing app, the team took on the goal of 
> re-thinking our mobile readers, and how we could provide them with a 
> delightful, app-specific, experience that will keep them reading Wikipedia on 
> iOS.
> 
> After an extended alpha period we’re ready to share that work with you, and 
> we’re looking forward to your feedback! 
> 
> Sign up for the Beta by registering here: https://goo.gl/forms/hNxPJah57p 
> 
> Once we are approved by Apple, you will receive a notification to install the 
> beta via the TestFlight platform.
> 
> I will also be giving a walkthrough of the app, as a lighting talk tomorrow 
> at 11 PST. It will be one of several to the WMF’s monthly lightning talks for 
> Dec, which will stream here:
> http://www.youtube.com/watch?v=cIqhGxtXFbg 
>  
> 
> Thanks,
> Josh Minor
> Product Manager, Reading 
> 
> ==More info[3]==
> What’s New?
> Our aim was to give our users an easier and more inviting way to discover and 
> read Wikipedia on iOS, and find experiences to keep them engaged. So, there 
> are few new features or changes to the core features, but an all new 
> look-and-feel, and many changes to navigation around that core. 5.0 is a 
> complete overhaul from the ground up, but some major highlights include:
> 
> New Explore screen, a mobile-friendly way to enable that Wikipedia moment of 
> serendipity 
> “First time user experience” that helps users get oriented and configure the 
> app
> All new user interface look-and-feel 
> Tab based navigation for one tap access to your History and Saved pages
> Redesigned reader experience, with new page information and table of contents 
> Easy access to language switching while searching and reading
> 
> Why is the app so different than the previous one?
> Although the existing iOS app is well reviewed, and has been featured by 
> Apple, it has never been able to build a sizable audience. Compared to other 
> content sites on the internet, our official apps have not been able to keep 
> our iOS users engaged as they shifted from desktop browsers to mobile apps. 
> In order to “try again” to see if we could engage readers, and also keep them 
> engaged, we’re trying a totally new way of presenting ourselves on iOS. You 
> can read a lot more about this on our project wiki [2] and in this product 
> presentation [4].
> 
> What’s this Explore thing?
> The app’s Explore screen is a new, mobile friendly, way to experience the joy 
> of discovery on Wikipedia. It mixes community curated content (from the 
> en.wikipedia Main Page and Commons) with personally relevant content (based 
> on articles you’ve read and your device location). All this is compiled 
> locally on device and presented in a UI paradigm that is friendly to short, 
> touch based sessions for casual consumption of media. It is an attempt to 
> find a new way to engage, and re-engage, readers on a regular basis, by 
> providing them a wide variety of dynamically changing content, presented in a 
> familiar format. We think it can be very powerful way to enable mobile users 
> to have that magic Wikipedia moment of discovery.
> 
> Where’s my favorite old feature?
> Many features that were previously part of the “W” menu are now included in 
> the Explore page. Random articles and articles near your location can both be 
> found by exploring your feed. Other parts of the app now live in the main tab 
> bar (Recent and Saved pages), or in the upper bar (Settings). Not finding 
> something you loved? Fill out our feedback form and let us know [5]. 
> 
> What’s missing? Known issues?
>   - Feed language and site: Currently the Explore page takes its content from 
> your current “site”, based on your current search language. We will need to 
> add more nuance to our site and language controls. If you are a multilingual 
> user of the app, we’re particularly interested to get your feedback.
>  - The app can be overly aggressive about updating/refreshing content. We 
> erred on the side of getting the “latest” content.
>  - Some localizations and RTL language support are incomplete (especially on 
> iOS 8). We are actively working on this.
>  - Navigation issues: although the tab based main interface has been well 
> liked by users, the new navigation flows have introduced some inconveniences 
> for longer sessions and quickly accessing some less frequently used but much 
> loved features. We look forward to hearing from you about what you like, and 
> don’t, about the new navigation.
> 
> How can I give feedback?
> We have a feedback

Re: [WikimediaMobile] [Analytics] Stopping eventlogging events into MobileWikiAppShareAFact table

[Adam Baso]

Replacing mobile-tech with mobile-l (internal mobile-tech list
discontinued).

On Tuesday, December 22, 2015, Nuria Ruiz  wrote:

> Team:
>
> As part of our effort of converting eventlogging mysql database to the
> tokudb engine we need to stop eventlogging events from flowing into the 
> MobileWikiAppShareAFact
> table, we are using this one table to see how long the conversion will take
> in order to plan for a larger outage window.
>
>
> Let us know if data should be backfilled as it can be, we anticipate
> events will not flow into table for the better part of one day.
>
>
> Thanks,
>
> Nuria
>
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] MobileWikiAppShareAFact event stream was: [Analytics] Stopping eventlogging events into MobileWikiAppShareAFact table

[Nuria Ruiz]

Team:

This  schema MobileWikiAppShareAFact is sending a lot of events, maybe is
worth thinking whether we need that many. It is again a case where tables
are becoming huge and hard to query fast.

cc-ing Jon as schema owner.

Can this data be sampled at a higher sampling rate? I have filed a ticket
to this fact:
https://phabricator.wikimedia.org/T14

Thanks,

Nuria




On Tue, Dec 22, 2015 at 8:35 AM, Adam Baso  wrote:

> Replacing mobile-tech with mobile-l (internal mobile-tech list
> discontinued).
>
>
> On Tuesday, December 22, 2015, Nuria Ruiz  wrote:
>
>> Team:
>>
>> As part of our effort of converting eventlogging mysql database to the
>> tokudb engine we need to stop eventlogging events from flowing into the 
>> MobileWikiAppShareAFact
>> table, we are using this one table to see how long the conversion will take
>> in order to plan for a larger outage window.
>>
>>
>> Let us know if data should be backfilled as it can be, we anticipate
>> events will not flow into table for the better part of one day.
>>
>>
>> Thanks,
>>
>> Nuria
>>
>>
>>
> ___
> 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] MobileWikiAppShareAFact event stream was: [Analytics] Stopping eventlogging events into MobileWikiAppShareAFact table

[Jon Katz]

+ Dmitry

Hi Nuria,
I will ask Dmitry to confirm, but I think a pause is fine for the next
couple of days as long as we are given the timestamps for outage can note
it on the schema wiki page.  Is this a sudden increase or has it always
been sending to high of a volume?  Regardless, I imagine a higher sampling
rate can probably be applied.
-J

On Tue, Dec 22, 2015 at 9:58 AM, Nuria Ruiz  wrote:

> Team:
>
> This  schema MobileWikiAppShareAFact is sending a lot of events, maybe is
> worth thinking whether we need that many. It is again a case where tables
> are becoming huge and hard to query fast.
>
> cc-ing Jon as schema owner.
>
> Can this data be sampled at a higher sampling rate? I have filed a ticket
> to this fact:
> https://phabricator.wikimedia.org/T14
>
> Thanks,
>
> Nuria
>
>
>
>
> On Tue, Dec 22, 2015 at 8:35 AM, Adam Baso  wrote:
>
>> Replacing mobile-tech with mobile-l (internal mobile-tech list
>> discontinued).
>>
>>
>> On Tuesday, December 22, 2015, Nuria Ruiz  wrote:
>>
>>> Team:
>>>
>>> As part of our effort of converting eventlogging mysql database to the
>>> tokudb engine we need to stop eventlogging events from flowing into the 
>>> MobileWikiAppShareAFact
>>> table, we are using this one table to see how long the conversion will take
>>> in order to plan for a larger outage window.
>>>
>>>
>>> Let us know if data should be backfilled as it can be, we anticipate
>>> events will not flow into table for the better part of one day.
>>>
>>>
>>> Thanks,
>>>
>>> Nuria
>>>
>>>
>>>
>> ___
>> 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: pageviews.js—A JavaScript Client Library for the Wikimedia Pageviews API for Node.js and the browser

[Jon Robson]

I can report this was super easy to use and I've now incorporated it into
https://pushipedia.wmflabs.org/ - now I can keep up with what all the cool
kids are reading!

Sadly right now it just sends me the star wars episode 7 link every
morning... but I'm looking forward to the day the star wars buzz dies down
:)


On Tue, Dec 15, 2015 at 5:21 PM, Adam Baso  wrote:

> Interesting! Also, so is this:
>
> http://top.hatnote.com
>
>
> -- Forwarded message --
> From: *Thomas Steiner* 
> Date: Tuesday, December 15, 2015
> Subject: [Wiki-research-l] pageviews.js—A JavaScript Client Library for
> the Wikimedia Pageviews API for Node.js and the browser
> To: Research into Wikimedia content and communities <
> wiki-researc...@lists.wikimedia.org>
> Cc: Analytics List 
>
>
> Dear all,
>
> First and foremost, thanks for making the Wikimedia Pageviews API
> available; your work is highly appreciated and super useful! As a
> modest "thank you", I am happy to release the JavaScript client
> library pageviews.js for Node.js and the browser to make working with
> this API easy for JavaScript developers. Please find the code and all
> instructions at [1]. The library adds some convenience functions
> (getting batch pageviews and limiting the number of results) that were
> inspired by Dan Andreescu's Python library [2] and is Promise-based:
>
> ===
> var pageviews = require('pageviews');
>
> // Getting pageviews for a single article
> pageviews.getPerArticlePageviews({
>   article: 'Berlin',
>   project: 'en.wikipedia',
>   start: '20151201',
>   end: '20151202'
> }).then(function(result) {
>   console.log(JSON.stringify(result, null, 2));
> }).catch(function(error) {
>   console.log(error);
> });
>
> // Getting top-n items ranked by pageviews for multiple projects
> pageviews.getTopPageviews({
>   projects: ['en.wikipedia', 'de.wikipedia'], // Plural
>   year: '2015',
>   month: '12',
>   day: '01',
>   limit: 2 // Limit to the first n results
> }).then(function(result) {
>   console.log(JSON.stringify(result, null, 2));
> }).catch(function(error) {
>   console.log(error);
> });
> ===
>
> On a more technical note—trying to be a good citizen [3]—the client
> library sets an identifying User-Agent header in Node.js mode.
> However, trying to set the corresponding X-User-Agent (note the "X-")
> header from a browser context (XMLHttpRequest cannot override the
> browser's intrinsic User-Agent for security reasons), this fails with
> an error message "Request header field X-User-Agent is not allowed by
> Access-Control-Allow-Headers in preflight response". Maybe you could
> change your CORS settings and include X-User-Agent in your
> Access-Control-Allow-Headers?!
>
> Hope this is useful.
>
> Thanks,
> Tom
>
> --
> [1] pageviews.js: https://github.com/tomayac/pageviews.js
> [2] python-mwviews: https://github.com/mediawiki-utilities/python-mwviews
> [3] User-Agent requirement: https://wikimedia.org/api/rest_v1/?doc
>
> --
> Dr. Thomas Steiner, Employee (blog.tomayac.com, twitter.com/tomayac)
>
> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
> Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
> Registergericht und -nummer: Hamburg, HRB 86891
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.29 (GNU/Linux)
>
>
> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/
> -END PGP SIGNATURE-
>
> ___
> Wiki-research-l mailing list
> wiki-researc...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wiki-research-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] Stopping eventlogging events into MobileWikiAppShareAFact table

[Nuria Ruiz]

Stream of events to MobileWikiAppShareAFact table has been restored. Outage
of events was a bit less than 3 hours , please let us know if this data
needs to be backfilled.

Thanks,

Nuria

On Tue, Dec 22, 2015 at 8:30 AM, Nuria Ruiz  wrote:

> Team:
>
> As part of our effort of converting eventlogging mysql database to the
> tokudb engine we need to stop eventlogging events from flowing into the 
> MobileWikiAppShareAFact
> table, we are using this one table to see how long the conversion will take
> in order to plan for a larger outage window.
>
>
> Let us know if data should be backfilled as it can be, we anticipate
> events will not flow into table for the better part of one day.
>
>
> Thanks,
>
> Nuria
>
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Beta of Wikipedia 5.0.0 for iOS

[Joshua Minor]

Hi Sjoerd,

Thanks for your interest.

If you've previously registered, you do not need to register for this
update. However, we are prioritizing distribution to people who've signed
up specifically for this test. We will then back-fill in existing testers
until we reach Apple's limit.

So, helpful to give us your name and email on the new form (
https://goo.gl/forms/hNxPJah57p), but not required.

Cheers,
Josh

On Tue, Dec 22, 2015 at 1:36 AM, Sjoerd de Bruin 
wrote:

> Hi,
>
> Is there going to be a new list of beta testers? I was subscribed before...
>
> Greetings,
>
> Sjoerd de Bruin
>
> Op 22 dec. 2015, om 00:34 heeft Joshua Minor  het
> volgende geschreven:
>
> Hello,
>
> Since last quarter the WMF’s iOS team [1] (part of the Reading product
> group) has been working on a major version update to our iOS app [2].
> Rather than adding new features to the existing app, the team took on the
> goal of re-thinking our mobile readers, and how we could provide them with
> a delightful, app-specific, experience that will keep them reading
> Wikipedia on iOS.
>
> After an extended alpha period we’re ready to share that work with you,
> and we’re looking forward to your feedback!
>
> Sign up for the Beta by registering here: https://goo.gl/forms/hNxPJah57p
>
> Once we are approved by Apple, you will receive a notification to install
> the beta via the TestFlight platform.
>
> I will also be giving a walkthrough of the app, as a lighting talk
> tomorrow at 11 PST. It will be one of several to the WMF’s monthly
> lightning talks for Dec, which will stream here:
> http://www.youtube.com/watch?v=cIqhGxtXFbg
>
> Thanks,
> Josh Minor
> Product Manager, Reading
>
> ==More info[3]==
> What’s New?
> Our aim was to give our users an easier and more inviting way to discover
> and read Wikipedia on iOS, and find experiences to keep them engaged. So,
> there are few new features or changes to the core features, but an all new
> look-and-feel, and many changes to navigation around that core. 5.0 is a
> complete overhaul from the ground up, but some major highlights include:
>
>
>- New Explore screen, a mobile-friendly way to enable that Wikipedia
>moment of serendipity
>- “First time user experience” that helps users get oriented and
>configure the app
>- All new user interface look-and-feel
>- Tab based navigation for one tap access to your History and Saved
>pages
>- Redesigned reader experience, with new page information and table of
>contents
>- Easy access to language switching while searching and reading
>
>
> Why is the app so different than the previous one?
> Although the existing iOS app is well reviewed, and has been featured by
> Apple, it has never been able to build a sizable audience. Compared to
> other content sites on the internet, our official apps have not been able
> to keep our iOS users engaged as they shifted from desktop browsers to
> mobile apps. In order to “try again” to see if we could engage readers, and
> also keep them engaged, we’re trying a totally new way of presenting
> ourselves on iOS. You can read a lot more about this on our project wiki
> [2] and in this product presentation [4].
>
> What’s this Explore thing?
> The app’s Explore screen is a new, mobile friendly, way to experience the
> joy of discovery on Wikipedia. It mixes community curated content (from the
> en.wikipedia Main Page and Commons) with personally relevant content (based
> on articles you’ve read and your device location). All this is compiled
> locally on device and presented in a UI paradigm that is friendly to short,
> touch based sessions for casual consumption of media. It is an attempt to
> find a new way to engage, and re-engage, readers on a regular basis, by
> providing them a wide variety of dynamically changing content, presented in
> a familiar format. We think it can be very powerful way to enable mobile
> users to have that magic Wikipedia moment of discovery.
>
> Where’s my favorite old feature?
> Many features that were previously part of the “W” menu are now included
> in the Explore page. Random articles and articles near your location can
> both be found by exploring your feed. Other parts of the app now live in
> the main tab bar (Recent and Saved pages), or in the upper bar (Settings).
> Not finding something you loved? Fill out our feedback form and let us
> know [5].
>
> What’s missing? Known issues?
>  - Feed language and site: Currently the Explore page takes its content
> from your current “site”, based on your current search language. We will
> need to add more nuance to our site and language controls. If you are a
> multilingual user of the app, we’re particularly interested to get your
> feedback.
> - The app can be overly aggressive about updating/refreshing content. We
> erred on the side of getting the “latest” content.
> - Some localizations and RTL language support are incomplete (especially
> on iOS 8). We are actively working on this.
> - Navi