Mobile-l

mobile-l@lists.wikimedia.org

3 participants
6883 discussions

Fwd: The Wikimedia Research Newsletter 6(7) is out
by Tilman Bayer 11 Aug '16

11 Aug '16

Forwarding, as the reviewed paper on wikilinks and navigability might be of interest to this list too. ---------- Forwarded message ---------- From: Mohammed Sadat <masssly(a)ymail.com> Date: Wed, Aug 10, 2016 at 6:22 AM Subject: The Wikimedia Research Newsletter 6(7) is out To: Wikimedia Research Mailing List <wiki-research-l(a)lists.wikimedia.org> Cc: Tilman Bayer <tbayer(a)wikimedia.org>, Dario Taraborelli < dtaraborelli(a)wikimedia.org> The July 2016 issue of the Wikimedia Research Newsletter is out: https://blog.wikimedia.org/2016/08/10/research-newsletter-july-2016/ https://meta.wikimedia.org/wiki/Research:Newsletter/2016/July In this issue: 1 Making it easier to navigate within article networks via better wikilinks 2 Briefly 2.1 New research journal about Wikipedia and higher education 2.2 Conferences and events *** 19 recent publications were covered or listed in this issue *** Thanks to Jonathan Morgan for contributing. Masssly, Tilman Bayer and Dario Taraborelli --- Wikimedia Research Newsletter https://meta.wikimedia.org/wiki/Research:Newsletter/ * Follow us on Twitter: @WikiResearch <http://twitter.com/Wikiresearch> * Receive this newsletter by mail: https://lists.wikimedia.org/mailman/listinfo/research-newsletter * Subscribe to the RSS feed: http://blog.wikimedia.org/c/research-2/wikimedia-research-newsletter/feed/ -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB

1 0

Readership metrics for the timespan until July 31, 2016
by Tilman Bayer 10 Aug '16

10 Aug '16

Hi all, this resumes the usual look <https://www.mediawiki.org/wiki/Reading/Readership_metrics_reports> at our most important readership metrics. This edition of the report introduces a new year-over-year comparison chart to better understand which traffic changes are seasonal, and highlights a recent browser-related issue that has, suddenly and probably artificially, increased our global usage by 11%. We also take a first look of how the ratio of pageviews per device has been developing over time, and point out some other events that had an impact on core metrics. As laid out earlier <https://lists.wikimedia.org/pipermail/mobile-l/2015-September/009773.html>, the main purpose is to raise awareness about how these 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 <https://www.mediawiki.org/wiki/Wikimedia_Product#Reading> at MediaWiki.org. This edition of the report covers a timespan of 14 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 Q4 2015-16 (April-June), which includes lots of traffic and usage data <https://commons.wikimedia.org/w/index.php?title=File:Reading_Quarterly_Revi…> . - I gave an update on long-term traffic trends at the Foundation’s metrics meeting in May, see slides <https://commons.wikimedia.org/w/index.php?title=File%3AWMF_Metrics_%26_Acti…> (and will again later this month). Now to the usual data. (All numbers below are averages for April 25-July 31, 2016 unless otherwise noted.) Pageviews Total: 511 million/day (-5.0% from the previous report) Context (April 2015-July 2016): <https://commons.wikimedia.org/wiki/File:Wikimedia_daily_pageviews,_all_vs._…> See also the Vital Signs dashboard <https://analytics.wikimedia.org/dashboards/vital-signs/#projects=all/metric…> (Small caveat: Android app pageviews in April and early May were undercounted by up to 1-2 million/dayl due to a bug <https://phabricator.wikimedia.org/T132965>.) Overall pageviews developed relatively uneventfully during the timespan of this report until around July 20, when the desktop traffic to the main pages of several large Wikipedias (including English, Russian and Dutch) suddenly increased drastically. The investigation <https://phabricator.wikimedia.org/T141506> is still ongoing. At this point though it seems likely that this is not due an undetected spider or such, but caused by browsers of real users behaving in an unusual way, namely an old version of Chrome on Windows. Overall pageviews for all projects appear to have increased around 11% due to this. To improve our understanding of which traffic movements are seasonal and which may indicate lasting changes, I have pieced together 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): <https://commons.wikimedia.org/wiki/File:Wikimedia_pageviews_year-over-year_…> For example, we talked before about how the large year-over-year decrease seen in earlier months (e.g. -11.9% from April 2015 to April 2016) could probably be attributed to two one-time events in May/June 2015: the switch to HTTPS-only connections and the block of the Chinese Wikipedia in China. At the time this was based on more indirect evidence, in particular changes in the ratio of pageviews from the Global North. Now that a year has passed, we can directly compare data from after these events year-over-year. It confirms that conclusion (in the chart, compare the red line against the other three on the left hand side). In July 2016 there actually was a 1.1% increase compared to July 2015. Of course this is partly due to the aforementioned main pages anomaly, which is also visible clearly in this chart. Desktop: 54.1% (previous report: 55.2%) Mobile web: 44.6% (previous report: 43.6%) Apps: 1.3% (previous report: 1.2%) (small caveat: app percentage is a bit too low due to the aforementioned Android-related bug in April/May) Context (April 2015-July 2016): <https://commons.wikimedia.org/wiki/File:Wikimedia_daily_pageviews,_mobile_p…> After largely stagnating earlier this year following the christmas bump, the mobile percentage started to rise again towards parity around May (reaching 48.6% in the week until July 11). However, the recent anomalously high main pages traffic described above was entirely on desktop and has thus, perhaps temporarily, brought this percentage down again (to 42.7% in the week until July 31). As a reminder, mobile already has a solid majority in terms of unique devices, cf. below. Global North ratio: 75.5% of total pageviews (previous report: 76.5%) Context (last seven months): After a notable decrease (or, increase in the Global South ratio) at the beginning of the year, this number was relatively steady over the timespan of this report. NB: We are currently rethinking this metric and might replace it with a different country selection constructed as part of the work on the New Readers project. Unique devices See the announcement blog post <https://blog.wikimedia.org/2016/03/30/unique-devices-dataset/> from March for background and details on this recently introduced metric. These estimated numbers are provided for all Wikimedia language projects (separately for the desktop and mobile web version). Because of the instrumentation method, there is no global metric for all projects and all languages, but following some recent discussions it is now planned <https://phabricator.wikimedia.org/T138027> to extend it to a cross-language global metric per project at least. For now, we track the daily numbers of the English Wikipedia in this report. Daily unique devices estimate for English Wikipedia: - Mobile web: 32.2 million (previous report: 33.2 million) - Desktop: 22.3 million (previous report: 25.7 million) - Total: 54.5 million (previous report: 58.9 million) - Average mobile web ratio: 59.3% (previous report: 56.5%) Context (January-August 2016): See also the new Vital Signs dashboard <https://analytics.wikimedia.org/dashboards/vital-signs/#projects=enwiki/met…> As mentioned in the previous report, there was a drop in early to mid March which hasn’t seen an explanation so far. This metric hasn’t existed long enough yet to get a good sense of what yearly seasonalities may exist, but it looks a bit like a decreasing trend in desktop devices during these seven months. Interestingly though, pageviews did not decrease as much. Or to put it differently, pageviews per device rose during this time (even if one disregards the aforementioned main page increase since the end of July): <https://commons.wikimedia.org/wiki/File:Daily_views_per_unique_device_for_E…> New app installations Android:19.7k/day (-37.7% from the previous report) Daily installs per device, from Google Play Context (last six months): As described in the previous report, in March a Google bug had accidentally increased visitor number to the app’s Play Store listing enormously (spike cut off in this chart). So this it’s not surprising that the average install rate over the timespan of this report is much lower. Even disregarding this factor though, the install rates have been decreasing over the last few months and are matched by uninstalls on most days (except for a bump during two weeks in July whose reason is unknown to me). Combined with devices going inactive etc. this has meant that the app’s install base has been shrinking, from from 15.5 million on March 31 to 15.1 million today. On July 28, an updated version of the app with several exciting new features was launched, with a blog post <https://blog.wikimedia.org/2016/07/28/wikipedia-android-redesign/> that had very high pageview numbers and was picked up by media outlets in various countries. Unfortunately this public attention has not translated into a lot of downloads - we estimate around 3000 (a few hours’ worth at the normal rate). In comparison, the relaunch of the OS app in March brought roughly 50k additional installs (see previous report). iOS: 3.18 k/day (-37.2% from the previous report) Download numbers from App Annie Context (last six months): As mentioned, the iOS app’s huge relaunch fell into the timespan of the previous report, so the decrease here is not surprising. App user retention Android: 16.7% (previous report: 15.4%) (Ratio of app installs opened again 7 days after installation, among all installed one week before a date that falls within this report. 1:100 sample) Context (last six months): As remarked in earlier reports, this data is a bit too noisy for drawing conclusions about whether retention changed significantly between different releases. But we can at least rule out the existence of major shifts during this timespan. iOS: N/A <https://phabricator.wikimedia.org/T126693> Unique app users Android: 1.145 million / day (-5.0% from the previous report timespan, reconstructed <https://phabricator.wikimedia.org/T132965>) Context (last six months): Continuing the slight but steady decline that had been interrupted by the aforementioned Google bug windfall in March. iOS: N/A <https://phabricator.wikimedia.org/T130432> While we don’t have total active user numbers available for the iOS app any more, let’s mention an interesting increase that happened in the app’s pageviews back in May, by around 20%. (Because of the app’s small share in overall traffic, it did not affect the global pageviews discussed above in a notable way.) After some investigation, it turned out this coincided with the release of version 5.0.3 of the app, see the yellow slice on the right: Josh and I are planning to look further into possible causes; at the moment it’s still possible that this is either an artefact or due to real improvements in the app. ---- For reference, the queries and source links used are listed below (access is needed for each). Unless otherwise noted, all content of this report is © Wikimedia Foundation and released under the CC BY-SA 3.0 <https://creativecommons.org/licenses/by-sa/3.0/> license. Most of the above charts are available on Commons, too <https://commons.wikimedia.org/w/index.php?title=Special:ListFiles&offset=20…>; together with PDF versions of this report. 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>0 AND agent_type = 'user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT LEFT(timestamp, 10) AS date, sum(IF(access_method <> 'desktop', pageviews, null)) AS mobileviews, SUM(pageviews) AS allviews FROM staging.pageviews05 WHERE is_spider = FALSE AND is_automata = FALSE GROUP BY date; SELECT access_method, SUM(view_count)/(7*14) FROM wmf.projectview_hourly WHERE agent_type = 'user' AND CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2016-04-25" AND "2016-07-31" GROUP BY access_method; SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")), SUM(view_count) AS all, 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)) AS Global_North_views FROM wmf.projectview_hourly WHERE year > 0 AND agent_type='user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; https://console.developers.google.com/storage/browser/pubsite_prod_rev_0281… (“overview”) https://www.appannie.com/dashboard/252257/item/324715238/downloads/ (select “Total”) SELECT LEFT(timestamp, 8) AS date, SUM(IF(event_appInstallAgeDays = 0, 1, 0)) AS day0_active, SUM(IF(event_appInstallAgeDays = 7, 1, 0)) AS day7_active FROM log.MobileWikiAppDailyStats_12637385 WHERE userAgent LIKE '%-r-%' AND userAgent NOT LIKE '%Googlebot%' GROUP BY date ORDER BY DATE; (with the retention rate calculated as day7_active divided by day0_active from seven days earlier, of course) SELECT CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, unique_count AS Android_DAU FROM wmf.mobile_apps_uniques_daily WHERE platform = 'Android'; SELECT year, month, day, CONCAT(year,'-',LPAD(month,2,'0'),'-',LPAD(day,2,'0')) AS date, CONCAT(SPLIT(user_agent_map['wmf_app_version'], '\\.')[0], COALESCE( CONCAT('.', SPLIT(user_agent_map['wmf_app_version'], '\\.')[1]), ''), COALESCE( CONCAT('.', SPLIT(user_agent_map['wmf_app_version'], '\\.')[2]), '')) AS app_version, SUM(view_count) AS views FROM wmf.pageview_hourly WHERE year >0 AND access_method = 'mobile app' AND user_agent_map['os_family'] = 'iOS' AND agent_type = 'user' GROUP BY year, month, day, user_agent_map['wmf_app_version'] ORDER BY year, month, day, app_version LIMIT 20000; -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB

2 2

Reading team updates from last quarter and planning for next quarter
by Moushira Elamrawy 10 Aug '16

10 Aug '16

Good day everyone, Planning for the next quarter is coming soon, if you have relevant ideas that the reading team <https://www.mediawiki.org/wiki/Reading> can consider to work on for the upcoming 3 months, please add them to the page here <https://www.mediawiki.org/wiki/Reading/Quarterly_planning/FY2016-2017/Q2>[0]. The page has archives for quarterly planning from previous months, and you can review ideas from last quarter here <https://www.mediawiki.org/wiki/Reading/Quarterly_planning/FY2016-2017/Q1> [1] There is also a summary for Reading team updates during the last quarte <https://www.mediawiki.org/wiki/Reading_team_updates_April_2016_-_July_2016>r [2], major highlights include, a) Lazy loading of images <https://www.mediawiki.org/wiki/Reading/Web/Projects/Performance/Lazy_loadin…>,[3] b) new readers <https://meta.wikimedia.org/wiki/New_Readers>,[4] c) and the move of the language switching button on mobile. Hope that was helpful, looking forward to your ideas and input! Regards, Moushira [0] https://www.mediawiki.org/wiki/Reading/Quarterly_planning/FY2016-2017/Q2 [1] https://www.mediawiki.org/wiki/Reading/Quarterly_planning/FY2016-2017/Q1 [2] https://www.mediawiki.org/wiki/Reading_team_updates_April_2016_-_July_2016 [3] https://www.mediawiki.org/wiki/Reading/Web/Projects/Performance/Lazy_loadin… [4] https://meta.wikimedia.org/wiki/New_Readers

3 2

Redlinks in Android app
by Andy Mabbett 04 Aug '16

04 Aug '16

The Android Wikipedia app shows Wikipedia's red links as blue links, then returns a user-unfriendly 404 error page, with the somewhat dishonest text "an unknown error occurred". Alternative, and better, behaviours would be one of (in no particular order): * Show a red link; behave like desktop Wikipedia * Show a red link; when the link is selected, show a customised 404 page, which advises users how start a new article * Show red text, but make it non linking (i.e. "unclickable") * Remove the link and colour-styling, and render ordinary text * Fix the erorr page so it says "Sorry, that page does not exist", with a link to a guide to starting a new article -- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk

3 2

mobile-l:企业如何预防劳动用工过程中的法律风险 38lzl3
by ryinnfzt 02 Aug '16

02 Aug '16

mobile-l: 您好 1.如何预防劳动者的“应聘欺诈”，如何证明劳动者的“欺诈”？ 2.招收应届毕业生，应注意哪些细节问题？ 3.招用达到法定退休年龄的人员，应注意哪些细节问题？ 4.招用待岗、内退、停薪留职的人员，应注意哪些细节问题？ 5.入职体检需注意哪些细节问题？ 6.入职前后用人单位应告知劳动者哪些情况，如何保留证据？ 7.《入职登记表》如何设计，才能起到预防法律风险的作用？ 8.劳动者无法提交《离职证明》，该怎么办？ 9.企业如何书写《录用通知书》，其法律风险有哪些？附件中的内容希望能帮助到您的工作。。。至高至明日月，至深至浅清溪。 2016-8-26:58:55 喜塔腊觅山

1 0

Getting link to a contact form to work using mobile view
by Karsten Hoffmeyer 02 Aug '16

02 Aug '16

Heiya, on the talk page of the ContactPage extension [0] it was reported [1] that adding a link to the contact page in the footer section of the skin [2] does not work when using the MobileFrontend extension [3], i.e. the mobile view. I just shows up for the regular desktop view. It was suggested that we should try asking for help on this mailing list. Since I am not a programmer ... Help will be appreciated and the solution will be added to the documentation page of the ContactPage extension as soon as it is known. Cheers Karsten [0] https://www.mediawiki.org/wiki/Extension:ContactPage [1] https://www.mediawiki.org/wiki/Topic:T8js2zyu3jt1rr7m [2] https://www.mediawiki.org/wiki/Extension:ContactPage#Further_customization [3] https://www.mediawiki.org/wiki/Extension:MobileFrontend

5 4

[Apps] Wikipedia for iOS 5.0.5 released to App Store
by Joshua Minor 30 Jul '16

30 Jul '16

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

5 4

Fwd: [Analytics] [Pageview API] Data Retention Question
by Adam Baso 29 Jul '16

29 Jul '16

Cross posting. ---------- Forwarded message ---------- From: *Dan Andreescu* <dandreescu(a)wikimedia.org> Date: Friday, July 29, 2016 Subject: [Analytics] [Pageview API] Data Retention Question To: Analytics List <analytics(a)lists.wikimedia.org> Dear Pageview API consumers, We would like to plan storage capacity for our pageview API cluster. Right now, with a reliable RAID setup, we can keep *18 months* of data. If you'd like to query further back than that, you can download dump files (which we'll make easier to use with python utilities). What do you think? Will you need more than 18 months of data? If so, we need to add more nodes when we get to that point, and that costs money, so we want to check if there is a real need for it. Another option is to start degrading the resolution for older data (only keep weekly or monthly for data older than 1 year for example). If you need more than 18 months, we'd love to hear your use case and something in the form of: need daily resolution for 1 year need weekly resolution for 2 years need monthly resolution for 3 years Thank you! Dan

2 1

[Apps] New Android production release
by Dmitry Brant 29 Jul '16

29 Jul '16

Hi everyone, We're excited to bring you an updated version of the Wikipedia Android app <https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, rolling out now to the Google Play store! [1] In this update, we're 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[2]. See Wikipedia articles about current events, today's trending articles, today's featured article and featured picture from Commons, and more. Please see today's blog post <https://blog.wikimedia.org/2016/07/28/wikipedia-android-redesign/> for more information. Want to help make the app even better? Read our getting-started guide <https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_ha…>, and start contributing! [1] For devices without Google Play services, you may download <https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.…> the app directly. [2] Note: your reading history is only stored locally on your device. Cheers, -- Dmitry Brant Senior Software Engineer / Product Owner (Android) Wikimedia Foundation https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering

1 0

[Apps] Android Wikipedia beta app release (2.3.148-beta-2016-07-18)
by Stephen Niedzielski 27 Jul '16

27 Jul '16

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_ha…

4 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l