Mobile-l

mobile-l@lists.wikimedia.org

4 participants
6884 discussions

Fwd: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Adam Baso 03 Jun '15

03 Jun '15

Cross posting for visibility. This kind of stuff gets posted to the API lists, so be sure to subscribe to those if you aren't already subscribed to them. ---------- Forwarded message ---------- From: Brad Jorsch (Anomie) <bjorsch(a)wikimedia.org> Date: Tue, Jun 2, 2015 at 1:42 PM Subject: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, mediawiki-api-announce(a)lists.wikimedia.org As has been announced several times (most recently at https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081559.html), the default continuation mode for action=query requests to api.php will be changing to be easier for new coders to use correctly. *The date is now set:* we intend to merge the change to ride the deployment train at the end of June. That should be 1.26wmf12, to be deployed to test wikis on June 30, non-Wikipedias on July 1, and Wikipedias on July 2. If your bot or script is receiving the warning about this upcoming change (as seen here <https://www.mediawiki.org/w/api.php?action=query&list=allpages>, for example), it's time to fix your code! - The simple solution is to simply include the "rawcontinue" parameter with your request to continue receiving the raw continuation data ( example < https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1 >). No other code changes should be necessary. - Or you could update your code to use the simplified continuation documented at https://www.mediawiki.org/wiki/API:Query#Continuing_queries (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue= >), which is much easier for clients to implement correctly. Either of the above solutions may be tested immediately, you'll know it works because you stop seeing the warning. I've compiled a list of bots that have hit the deprecation warning more than 10000 times over the course of the week May 23–29. If you are responsible for any of these bots, please fix them. If you know who is, please make sure they've seen this notification. Thanks. AAlertBot AboHeidiBot AbshirBot Acebot Ameenbot ArnauBot Beau.bot Begemot-Bot BeneBot* BeriBot BOT-Superzerocool CalakBot CamelBot CandalBot CategorizationBot CatWatchBot ClueBot_III ClueBot_NG CobainBot CorenSearchBot Cyberbot_I Cyberbot_II DanmicholoBot DeltaQuadBot Dexbot Dibot EdinBot ElphiBot ErfgoedBot Faebot Fatemibot FawikiPatroller HAL HasteurBot HerculeBot Hexabot HRoestBot IluvatarBot Invadibot Irclogbot Irfan-bot Jimmy-abot JYBot Krdbot Legobot Lowercase_sigmabot_III MahdiBot MalarzBOT MastiBot Merge_bot NaggoBot NasirkhanBot NirvanaBot Obaid-bot PatruBOT PBot Phe-bot Rezabot RMCD_bot Shuaib-bot SineBot SteinsplitterBot SvickBOT TaxonBot Theo's_Little_Bot W2Bot WLE-SpainBot Xqbot YaCBot ZedlikBot ZkBot -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

iOS 4.1.4 is live
by Corey Floyd 03 Jun '15

03 Jun '15

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

2 1

hacks I particularly liked at Lyon
by Brian Gerstle 02 Jun '15

02 Jun '15

Hey everyone, Just wanted to send my notes on the hack demos from this weekend, and potentially start a discussion about shipping some of them! *Apple Watch: *Corey & Jason did an incredible job on this, and I'm essentially sold that a watch companion app could augment our *read later* and *search* flows for what seems like a reasonable development cost. Not sure who did it, but server-side image/upload validation could be further facilitate cross-platform mobile uploads? *Image surface content gap*: IOW, which pages are in the most need of pictures. Seems like a "micro edit" workflow that could work well for apps when combined with location/geo-fencing. *Haikus from recent changes:* More of a technical inspiration: I'd love to discuss building a service that sends push notifications in response to RC stream events. *Dmitry's "Wikipedia Lite" hack*: I think we should do some prototypes on this. In particular, I'd like to play around with parsoid to create a "reader view" for Wikipedia pages. Aside from streamlining content for mobile and improving performance, this could also make it easier to bring back a lot of reader-centric features. Dynamic font sizes & color/contrast configurations are two things I see pop up from time to time in OTRS & iTunes. *Bernd's map view for Nearby:* This seems like a no-brainer. I sent a separate email to mobile-l, because it seems like some progress has been made in this area since I last looked into it. What were your favorite hacks? -- EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle IRC: bgerstle

2 1

Re: [WikimediaMobile] [FYI] Popular mobile phone in Ghana
by Adam Baso 02 Jun '15

02 Jun '15

Sharing to mobile-l On Thursday, May 28, 2015, Rachel diCerbo <rdicerb(a)wikimedia.org> wrote: > Not certain if you guys are aware of this: > > > > https://medium.com/product-notes/the-mystery-of-the-power-bank-phone-taking… >

5 4

Re: [WikimediaMobile] [Analytics] Share a Fact Initial Analysis
by Dario Taraborelli 02 Jun '15

02 Jun '15

Thanks for sharing this, Adam. Aside from engagement/funnel data, the critical question for this feature is: does it bring back eyeballs to the site from social media? It looks like it doesn’t yet, at least not in a substantial way, even with the caveat that App traffic is a very small fraction of total mobile traffic. Having looked into referrals for this feature before and after comparing them to Twitter’s own engagement analytics (and finding some big discrepancy), you should consider removing spiders/crawlers from the data (see [1]) to avoid inflating pageviews with non-human activity. I’m a big fan of this feature and look forward to seeing how you guys intend to scale it. Dario [1] https://github.com/ewulczyn/wmf/blob/b9f726ee3468852c3fed2780af1d8ac0004eda… <https://github.com/ewulczyn/wmf/blob/b9f726ee3468852c3fed2780af1d8ac0004eda…> > On May 21, 2015, at 12:37 PM, Toby Negrin <tnegrin(a)wikimedia.org> wrote: > > Hi all - some interesting analysis on the share-a-fact feature from the mobile team. > > -Toby > > Begin forwarded message: > >> From: Adam Baso <abaso(a)wikimedia.org <mailto:abaso@wikimedia.org>> >> Date: May 21, 2015 at 12:05:29 PDT >> To: mobile-l <mobile-l(a)lists.wikimedia.org <mailto:mobile-l@lists.wikimedia.org>> >> Subject: [WikimediaMobile] Share a Fact Initial Analysis >> >> Hello all, >> >> We’ve been looking at some initial results from the Share a Fact feature introduced on the Wikipedia apps for Android and iOS in its basic "minimal viable product" implementation. Here’s some analysis, using data from one day (20150512) with respect to the latest stable versions of the apps (2.0-r-2015-04-23 on Android and 4.1.2 on iOS) for that day. >> >> * On iOS, when a user initiates the first step of the default sharing workflow - tapping the up-arrow box share button (6,194 non-highlighting instances for the day under question) - about 11.7% of the time it yielded successful sharing. >> >> * On Android, it’s not possible to easily tell when the sharing workflow was carried through to successful share, but we anticipate the Android success rate is currently much higher, as general engagement percentage up to the point of picking an app for sharing is higher on Android than on iOS. >> >> * On Android, when presented with the share card preview, 28.0% of the time the ‘Share as image’ button was tapped and 55.5% of the time the 'Share as text' button was tapped, whereas on iOS it was 8.4% ‘Share as image’ and 16.8% ‘Share as text’. >> >> * The forthcoming 4.1.4 version of the iOS app will relax its default sharing snippet generation rules and be more like the Android version in that respect. We anticipate this will result in higher engagement with both the ‘Share as image’ and ‘Share as text’ buttons on iOS, and we should be able to verify this once the 4.1.4 iOS version is released and generally adopted (usually takes 4-5 days after release; the 4.1.4 release isn’t released yet). >> >> * On the Android app the ‘Share’ option is located on the overflow menu, not as part of the main set of UI buttons. This potentially increases the likelihood of Android users being primed to step through the workflow. On the iOS app, the share button (up-arrow box) is plainly visible from the main UI and not an overflow menu, and this probably creates a different priming dynamic for the iOS demographic. >> >> * When users on iOS tapped on the ‘Share as image’ or ‘Share as text’ buttons, there is a pretty sharp drop off at the next stage - the system sharesheet. Once the sharesheet was presented to iOS users, 41.6% of the time it resulted in active abandonment. We believe this probably has something to do with the relatively small set of default apps listed on the sharesheet and the extra work involved with exposing additional social apps for sharing in that context. As with the Android app, the labels of ‘Share as image’ and ’Share as text’ may also pose something of a hurdle at least for first time users of the feature. To this end, there is an onboarding tutorial planned at least on Android. >> >> * For a one hour period (2015051201) there were about 100 pageviews in some sense attributable to Share a Fact using a provenance parameter available on the latest stable versions of the apps at that time; this may slightly overstate the number of pageviews attributable to the two specific apps reviewed in this analysis, but probably not too much (n.b., previously a different source parameter was used than the new wprov provenance parameter). Pageviews are not the sole motivation for the feature, but following the trendline over the long run should be interesting. Impact on social media and the destinations of shares is a little harder to capture directly, but https://twitter.com/search?f=realtime&q=%40wikipedia%20-%40itzwikipedia%20f… <https://twitter.com/search?f=realtime&q=%40wikipedia%20-%40itzwikipedia%20f…> gives one a sense about image shares, at least. >> >> * A couple potential options for increasing sharing include: >> >> ** Trying to add support for sharing to the Photos app on iOS. People may be interested in using images from the Photos apps for various workflows, as Dan Garry has noted. >> >> ** Offering a more concise app picklist, in particular explicitly adding the native OS app components (namely, Twitter and Facebook, and as mentioned, Photos if possible), with an option to expose the sharesheet for additional options if necessary. This is probably also somewhat confined to iOS, although conceivably a similar approach could be possible on Android. On Android the full list of applications in its equivalent of the sharesheet is by default readily available to the user, though. >> >> ** On Android, exposing the diagonal arrow share button on the main interface akin to how the iOS version of the app shows the up-arrow share button. This may introduce more opportunities for sharing (and thus numbers of abandons would go up in tandem with numbers of shares), but would also partially clutter the interface and probably increase abandon. A controlled experiment may be useful for observing the impact of such an approach. >> >> * As a point of reference, for the app versions in scope for this analysis over a single day, there appeared to be approximately 3.78 million Wikipedia for Android pageviews and 1.19 Wikipedia Mobile for iOS app pageviews. There were about 6.73 million app pageviews on the “modern” versions of these apps total for this particular day, meaning there were about 1.75 million pageviews on other modern versions of the app. >> >> * Examination of the categories of successful shares on iOS showed the following distributions: >> >> Images: >> 48.5% messaging >> 25.5% sharesheet copy >> 22.9% social >> 1.8% productivity >> 0.9% reading >> >> >> Text: >> 53.6% messaging >> 31.9% sharesheet copy >> 7.1% social >> 5.4% reading >> 2.0% productivity >> >> >> Here were some queries used in the analysis: >> >> == SHARE A FACT ATTRIBUTABLE PAGEVIEWS FOR ONE HOUR == >> >> select wprov, uri_host, count(*) from (select x_analytics_map['wprov'] as wprov, uri_host >> from webrequest where year = 2015 and month = 5 and day = 12 and hour = 1 and is_pageview = true and uri_host like '%.wikipedia.org <http://wikipedia.org/>' and x_analytics_map['wprov'] is not null) t >> group by wprov, uri_host; >> >> >> == PAGE VIEWS FOR THE DAY FOR THE “MODERN” VERSIONS OF THE APPS == >> >> SELECT >> user_agent, count(*) >> FROM >> wmf.webrequest >> tablesample(BUCKET 1 OUT OF 100 ON rand()) >> WHERE >> YEAR = 2015 >> AND MONTH = 5 >> AND DAY = 12 >> AND is_pageview = TRUE >> AND lower(uri_host) like '%.wikipedia.org <http://wikipedia.org/>' >> AND user_agent like 'WikipediaApp%' >> GROUP BY user_agent; >> >> >> >> == HIGHLIGHTING SESSION CASE FOR SPECIFIC VERSIONS OF THE APPS == >> select CASE WHEN t2.userAgent LIKE 'WikipediaApp/2.0-r-2015-04-23%' THEN 'Android' WHEN t2.userAgent LIKE 'WikipediaApp/4.1.2%' THEN 'iOS' END AS 'ua', t1.event_action, t1.event_sharemode, t1.event_target, count(*) from MobileWikiAppShareAFact_11331974 t1 inner join MobileWikiAppShareAFact_11331974 t2 on t1.event_shareSessionToken = t2.event_shareSessionToken where t1.timestamp > '20150512' and t1.timestamp < '20150513' and t2.timestamp > '20150512' and t2.timestamp < '20150513' and t1.event_action != 'highlight' and t2.event_action = 'highlight' and (t2.userAgent like 'WikipediaApp/2.0-r-2015-04-23%' or t2.userAgent like 'WikipediaApp/4.1.2%') group by ua, t1.event_action, t1.event_sharemode, t1.event_target; >> >> >> == NON-HIGHLIGHTING SESSION CASE FOR SPECIFIC VERSIONS OF THE APPS == >> n.b., subtract the highlighting cases from the non-highlighting cases to arrive at the default sharing behavior. Technically, inner joins can be used to do more comprehensive session analysis, but the queries take a long time. >> >> select CASE >> WHEN userAgent LIKE 'WikipediaApp/2.0-r-2015-04-23%' THEN 'Android' >> WHEN userAgent LIKE 'WikipediaApp/4.1.2%' THEN 'iOS' >> END AS 'ua', event_action, event_sharemode, event_target, >> count(*) from MobileWikiAppShareAFact_11331974 where timestamp > '20150512' and timestamp < '20150513' and (userAgent like 'WikipediaApp/2.0-r-2015-04-23%' or userAgent like 'WikipediaApp/4.1.2%') group by ua, event_action, event_sharemode, event_target; >> >> -Adam >> _______________________________________________ >> Mobile-l mailing list >> Mobile-l(a)lists.wikimedia.org <mailto:Mobile-l@lists.wikimedia.org> >> https://lists.wikimedia.org/mailman/listinfo/mobile-l <https://lists.wikimedia.org/mailman/listinfo/mobile-l> > _______________________________________________ > Analytics mailing list > Analytics(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/analytics

2 2

Re: [WikimediaMobile] Mobile Firendly
by Adam Baso 30 May '15

30 May '15

Thank you! On Friday, May 29, 2015, Brandon Black <bblack(a)wikimedia.org> wrote: > We've merged up https://gerrit.wikimedia.org/r/#/c/214705/1 to address > this, and I've purged the caches to ensure the update is fully live > already. It should address the issue, assuming that the block on RL's > /w/load.php entry point was the only part of the problem. > > On Fri, May 29, 2015 at 8:43 PM, Jon Robson <jrobson(a)wikimedia.org > <javascript:;>> wrote: > > Yup what brandon said. > > > > On 29 May 2015 1:35 pm, "Jon Robson" <jrobson(a)wikimedia.org > <javascript:;>> wrote: > >> > >> It's all in the report. We block w/ in robots.txt always have. > >> > >> There have been a bunch of changes to improve performance of the site > >> overall which might have led to that. Mailing this to the public mailing > >> list wikitech would give you a better idea. > >> > >> Our site /is/ mobile friendly it's just we tell google not to load > styles > >> from w/load.php so no need to panic. > >> > >> The question is what is the penalty of us failing this tool? Does it > >> impact our google search rankings? > >> > >> Fix is trivial.. Update robots.txt but first the question is why are we > >> blocking scripts and styles on that url? > >> > >> On 29 May 2015 1:17 pm, "Jon Katz" <jkatz(a)wikimedia.org <javascript:;>> > wrote: > >>> > >>> Hi Readership team and broader community, > >>> Any changes we might have recently made to cause this warning to appear > >>> about googlebot not being able to access our site? > >>> I consider this to be a very serious issue. > >>> The examples below are not mobile, but same issue applies when you try > an > >>> en.m. version of the pages. > >>> > >>> Best, > >>> Jon > >>> > >>> > >>> ---------- Forwarded message ---------- > >>> From: Wes Moran <wmoran(a)wikimedia.org <javascript:;>> > >>> Date: Fri, May 29, 2015 at 12:47 PM > >>> Subject: Mobile Firendly > >>> To: Jon Katz <jkatz(a)wikimedia.org <javascript:;>> > >>> Cc: Adam Baso <abaso(a)wikimedia.org <javascript:;>> > >>> > >>> > >>> Jon, > >>> > >>> Google notified us of the followin... > >>> > >>> "We recently noticed that there was a change with how you embed CSS & > JS > >>> which results in us not being able to use the CSS & JS to recognize > what the > >>> page looks like. That's making some of your pages fail the > >>> mobile-friendly-test, for example. You used to load CSS & JS from > >>> bits.wikimedia.org, but now they're loaded through /w/load.php?... > directly > >>> from the Wikipedia host, where that path is blocked by robots.txt. > >>> > >>> You can see how we render the pages with Fetch as Google in Webmaster > >>> Tools / Search Console, you can also see most of that with the > test-page at: > >>> > >>> > https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fe… > >>> > >>> Some of the pages still pass the test there (example), but the CSS is > >>> broken there too since it's blocked. " > >>> > >>> Any ideas what can be causing this? > >>> > >>> Regards, > >>> Wes > >>> > >>> > >>> _______________________________________________ > >>> reading-wmf mailing list > >>> reading-wmf(a)lists.wikimedia.org <javascript:;> > >>> https://lists.wikimedia.org/mailman/listinfo/reading-wmf > >>> > > > > _______________________________________________ > > Ops mailing list > > Ops(a)lists.wikimedia.org <javascript:;> > > https://lists.wikimedia.org/mailman/listinfo/ops > > > > _______________________________________________ > Ops mailing list > Ops(a)lists.wikimedia.org <javascript:;> > https://lists.wikimedia.org/mailman/listinfo/ops >

1 0

Re: [WikimediaMobile] [reading-wmf] Fwd: Mobile Firendly
by Jon Katz 30 May '15

30 May '15

+external mobile and wikitech Shoot. I meant to send this the external list. For those of you just joining us, we recently got an email from google letting us know that some of our pages are now failing the mobile-friendly test, which has an adverse impact on our search results. It appears that most of our pages are also blocking style info. Google doesn't offer much insight into penalties, but if they're sending us the email then it is or will have some impact. I'd like to see if we can better understand the other side of the equation- what is cost of fixing it? I think Jon's questions below are the ones to start with. -J On Fri, May 29, 2015 at 1:35 PM, Jon Robson <jrobson(a)wikimedia.org> wrote: > It's all in the report. We block w/ in robots.txt always have. > > There have been a bunch of changes to improve performance of the site > overall which might have led to that. Mailing this to the public mailing > list wikitech would give you a better idea. > > Our site /is/ mobile friendly it's just we tell google not to load styles > from w/load.php so no need to panic. > > The question is what is the penalty of us failing this tool? Does it > impact our google search rankings? > > Fix is trivial.. Update robots.txt but first the question is why are we > blocking scripts and styles on that url? > On 29 May 2015 1:17 pm, "Jon Katz" <jkatz(a)wikimedia.org> wrote: > >> Hi Readership team and broader community, >> Any changes we might have recently made to cause this warning to appear >> about googlebot not being able to access our site? >> I consider this to be a very serious issue. >> The examples below are not mobile, but same issue applies when you try an >> en.m. version of the pages. >> >> Best, >> Jon >> >> >> ---------- Forwarded message ---------- >> From: Wes Moran <wmoran(a)wikimedia.org> >> Date: Fri, May 29, 2015 at 12:47 PM >> Subject: Mobile Firendly >> To: Jon Katz <jkatz(a)wikimedia.org> >> Cc: Adam Baso <abaso(a)wikimedia.org> >> >> >> Jon, >> >> Google notified us of the followin... >> >> "We recently noticed that there was a change with how you embed CSS & JS >> which results in us not being able to use the CSS & JS to recognize what >> the page looks like. That's making some of your pages fail the >> mobile-friendly-test, for example. You used to load CSS & JS from >> bits.wikimedia.org, but now they're loaded through /w/load.php?... >> directly from the Wikipedia host, where that path is blocked by robots.txt. >> >> You can see how we render the pages with Fetch as Google in Webmaster >> Tools / Search Console, you can also see most of that with the test-page at: >> >> https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fe… >> >> Some of the pages still pass the test there (example >> <https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fe…>), >> but the CSS is broken there too since it's blocked. " >> >> Any ideas what can be causing this? >> >> Regards, >> Wes >> >> >> _______________________________________________ >> reading-wmf mailing list >> reading-wmf(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/reading-wmf >> >> > _______________________________________________ > reading-wmf mailing list > reading-wmf(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/reading-wmf > >

2 2

Re: [WikimediaMobile] maps w/ nearby
by aude 27 May '15

27 May '15

Meant to send to the list. Katie On May 27, 2015 11:33 AM, "aude" <aude.wiki(a)gmail.com> wrote: > > > On May 27, 2015 2:46 AM, "Bernd Sitzmann" <bernd(a)wikimedia.org> wrote: > > > > Yes, we're using the mapbox API for Android. There's one for iOS and Web, too. > > Its pretty cool. It allows for customized tooltips on the place markers. > > > > We were hitting the OSM servers directly. > > As an alpha feature, it might be okay to use the map tiles on labs, which are same as the osm tiles. (though maybe slower) > > Beyond that, we need what yurik and max are working on. > > The patch could still use some more polish to improve the markers and maybe other details. > > Cheers, > Katie > > > _______________________________________________ > > Mobile-l mailing list > > Mobile-l(a)lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/mobile-l > >

1 0

Re: [WikimediaMobile] Your receipt No.6860996233300
by Jonatan Svensson Glad 25 May '15

25 May '15

This is a scam and a virus, do not click on any links in the HTML attachment. Jonatan Svensson Glad President of SSU Tyresö and Editor on Wikipedia +46 (0)760-44 24 44 | gladjonatan(a)outlook.com All views and opinions expressed in this email message are the personal opinions of the author and do not represent those of any organization which might be related to this message. No liability can be held for any damages, however caused, to any recipients of this message.

1 0

Your receipt No.6860996233300
by mobile-l＠lists.wikimedia.org 24 May '15

24 May '15

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l