Okay. So, to summarise: 1. Android uses sections=all for refreshes 2. iOS uses sections=all for pageviews, generally 3. iOS is shortly to also use sections=all for refreshes
...1, 2 and 3 will all look the same, minus UA differences between (1) and (2,3) IOW, there is shortly to be no visible difference, from server-side, between a "refresh" and a "pageview", for iOS users. Do I understand correctly? If so, I have some ideas for how we could mitigate this problem and make pageviews viable again *purses fingers*. On 19 March 2015 at 21:26, Adam Baso <[email protected]> wrote: > Oh, and the patch that introduced the sections=all stuff...here's the change > from what I recall. > > https://gerrit.wikimedia.org/r/#/c/176491/2/wikipedia/Networking/Fetchers/ArticleFetcher.m > > +Bernd, Dmitry, in case they weren't added on earlier email from some > reason. Please see below. +Monte > > > On Thu, Mar 19, 2015 at 6:18 PM, Adam Baso <[email protected]> wrote: >> >> I've added Dmitry and Bernd to this thread. Guys, you probably want to get >> on this list if you're not already on it. >> >> Here's the iOS part for refreshing (patches 1, 2, 3, 4). Suppose I have >> "Derek Charke" and "Darya Khan railway station" in my Saved pages list. Then >> when I tap the refresh button, the following requests are made >> automatically, with a User-Agent header of the following form: >> >> User-Agent: WikipediaApp/4.0.7 (iPhone OS 8.2; Phone) >> >> >> Requests...these use the ArticleFetcher class, which is the same class >> used for fetching articles even outside of a Saved pages refresh (i.e., >> garden variety article browsing). >> >> Derek Charke >> >> >> https://en.m.wikipedia.org/w/api.php?action=mobileview&appInstallID=<somevalue>&format=json&noheadings=true&page=Derek%20Charke&prop=sections%7Ctext%7Clastmodified%7Clastmodifiedby%7Clanguagecount%7Cid%7Cprotection%7Ceditable%7Cdisplaytitle%7Cthumb%7Cdescription%7Cimage§ionprop=toclevel%7Cline%7Canchor%7Clevel%7Cnumber%7Cfromtitle%7Cindex§ions=all&thumbwidth=640 >> >> >> Darya Khan railway station >> >> >> https://en.m.wikipedia.org/w/api.php?action=mobileview&appInstallID=<somevalue>&format=json&noheadings=true&page=Darya%20Khan%20railway%20station&prop=sections%7Ctext%7Clastmodified%7Clastmodifiedby%7Clanguagecount%7Cid%7Cprotection%7Ceditable%7Cdisplaytitle%7Cthumb%7Cdescription%7Cimage§ionprop=toclevel%7Cline%7Canchor%7Clevel%7Cnumber%7Cfromtitle%7Cindex§ions=all&thumbwidth=640 >> >> On Thu, Mar 19, 2015 at 1:36 PM, Oliver Keyes <[email protected]> >> wrote: >>> >>> (What I'd like from the Apps team to make this as efficient as possible: >>> >>> 1. Example URLs/UAs for each possible permutation >>> {{sections=0,sections=all}{iOS/Android}}; >>> 2. An idea (as suggested by Dan) of what the auto-update will mean. Is >>> Adam on this list or should I reach out distinctly?) >>> 3. Links to the pertinent gerrit patches that instituted the >>> auto-update thing and the iOS bugfix, so I can establish (in the logs >>> of the pageview def update) what the timeline is/was like here. >>> ) >>> >>> On 19 March 2015 at 16:33, Oliver Keyes <[email protected]> wrote: >>> > Okay. So, we're going to have to add an element of UA detection, then! >>> > That...should be doable pretty trivially. >>> > >>> > I have to make some changes to just this function for the session >>> > analysis (namely, breaking it out of its current scope and writing a >>> > UDF around it) so I'll incorporate this work into that. >>> > >>> > On 19 March 2015 at 16:32, Dan Garry <[email protected]> wrote: >>> >> On 19 March 2015 at 13:19, Oliver Keyes <[email protected]> wrote: >>> >>> >>> >>> Wait. So, sections=all is only /sometimes/ a pageview? ;) When? >>> >> >>> >> >>> >> If we're talking about Android, it's my understanding that nothing has >>> >> changed from before. sections=0 is a page view. sections=all is not >>> >> because >>> >> it's used for saved pages updates. >>> >> >>> >> If we're talking about iOS, as of right now, both sections=all or >>> >> sections=0 >>> >> are page views. Neither kind of query is used for anything else, >>> >> because >>> >> saved pages updates are not in production. >>> >> >>> >> Our next release for iOS, targeted for 30th March, will include a >>> >> saved >>> >> pages update feature. I'm unsure of the structure of the query used to >>> >> refresh saved pages. The iOS tech lead, Adam, should be able to shed >>> >> light >>> >> on this. >>> >> >>> >> Dan >>> >> >>> >> -- >>> >> Dan Garry >>> >> Associate Product Manager, Mobile Apps >>> >> Wikimedia Foundation >>> >> >>> >> _______________________________________________ >>> >> Analytics mailing list >>> >> [email protected] >>> >> https://lists.wikimedia.org/mailman/listinfo/analytics >>> >> >>> > >>> > >>> > >>> > -- >>> > Oliver Keyes >>> > Research Analyst >>> > Wikimedia Foundation >>> >>> >>> >>> -- >>> Oliver Keyes >>> Research Analyst >>> Wikimedia Foundation >>> >>> _______________________________________________ >>> Analytics mailing list >>> [email protected] >>> https://lists.wikimedia.org/mailman/listinfo/analytics >> >> > > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > -- Oliver Keyes Research Analyst Wikimedia Foundation _______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
