June 2014 - Mobile-l - lists.wikimedia.org

Re: [WikimediaMobile] [Wikitech-ambassadors] Deployment of tablet redirect to mobile interface (action needed)
by Federico Leva (Nemo) 19 Jun '14

19 Jun '14

I get reminded of https://xkcd.com/1174/ : "less information and a dumbed-down interface", "I like the tablet and desktop being the same", "Wiki for kiddies", "Mobile version sites are limited". https://blog.wikimedia.org/2014/06/17/wikimedia-sites-get-a-new-look-on-tab… Importance of data increases: I reiterate my question, for which I had no answer. Federico Leva (Nemo), 15/06/2014 09:09: >> Will someone be monitoring the effects [if any] on editing activity >> and number of active editors/new [10+ edits] editors? >> > > [...] I asked about effects of this change, not > about totals. And I add another question: is it technically possible to configure this switch per-wiki? Nemo

4 5

Fwd: VE on Android tablets
by Juliusz Gonera 18 Jun '14

18 Jun '14

Forwarding a list of bugs found by Rummana. ---------- Forwarded message ---------- From: Rummana Yasmeen <ryasmeen(a)wikimedia.org> Date: Tue, Jun 17, 2014 at 6:19 PM Subject: Re: [WikimediaMobile] VE on Android tablets To: Juliusz Gonera <jgonera(a)wikimedia.org> Hi Juliusz, I did some testing today on mobile VE with one of our Android tablets : Nexus 7(Android 4.4.2).There are some bugs around link inspector and other features. Though most of the bugs found in iPad are not reproducible here in Nexus 7, but there are many other different issues with it. I am sending you the list of reported bugs , let me know if you have any question regarding any bug :) Bug 66759 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66759> - VisualEditor Mobile: For the first time in each edit session in Nexus 7(Android 4.4.2), Link Inspector gets auto-zoomed in,which looks like partial rendering of the UI Bug 66755 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66755> - VisualEditor Mobile: Tapping at the end of each link, does copy-paste of preceding link text in Nexus 7(Android 4.4.2) Bug 66696 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66696> - VisualEditor Mobile: Getting stuck inside Link inspector while trying to clear the link text when there was no match for it in the inspector Bug 66753 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66753> - VisualEditor Mobile:Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) Bug 65325 <https://bugzilla.wikimedia.org/show_bug.cgi?id=65325> - VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE Bug 66697 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66697> - VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into. Bug 66758 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66758> - VisualEditor Mobile: Tapping on Return while cursor is at the end of a text , deletes that text in Nexus 7(Android 4.4.2) Bug 66756 <https://bugzilla.wikimedia.org/show_bug.cgi?id=66756> - VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2) Regards, Rummana On Tue, Jun 10, 2014 at 11:24 AM, Tomasz Finc <tfinc(a)wikimedia.org> wrote: > Juliusz, go ahead and sync up with Rummana (cc'd) and find out what her > availability is. > On Jun 10, 2014 11:21 AM, "Juliusz Gonera" <jgonera(a)wikimedia.org> wrote: > >> She could test a bit on recent Chrome for Android. Let's hold off on >> Android Browser for now, it's a buggy and we can instead suggest that >> Android 4 users install Chrome. >> >> >> Tomasz Finc wrote: >> >>> Should we get Rummana to help us do any additional testing on these? >>> >>> --tomasz >>> >>> On Thu, Jun 5, 2014 at 4:35 PM, Juliusz Gonera <jgonera(a)wikimedia.org> >>> wrote: >>> >>>> I tried VE on the two working Android tablets that we have: Samsung >>>> Galaxy >>>> Tab 10.1 (Android 4.0.4) and Nexus 7 (Android 4.4.2). Samsung uses >>>> Android >>>> Browser and VE performs slowly and buggy there. Link inspector works >>>> better >>>> than on iOS but there are other small bugs like problems with some >>>> icons not >>>> being scaled properly or occasional rendering issues. Nexus 7 with >>>> Kitkat >>>> has Chrome as its default browser and everything works fine there, I >>>> would >>>> even say it works better than iPads. >>>> >>>> Kaldari is doing more research regarding which tablets should be >>>> redirected >>>> to mobile. >>>> >>>> -- >>>> Juliusz >>>> >>>> _______________________________________________ >>>> Mobile-l mailing list >>>> Mobile-l(a)lists.wikimedia.org >>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l >>>> >>>> >>

2 1

Mobile revtags, redux
by Dario Taraborelli 18 Jun '14

18 Jun '14

Yuvi, Aaron and I sat down to review the implementation of revtags for mobile edits and we came up with the following proposal: Assumptions • we want to be able to expose whether an edit is from a mobile app or mobile web in MediaWiki as patrollers are filtering edits based on the source • we want to allow Product to have a handy way to select all mobile edits (regardless of whether they come from apps or mobile web) • we want a solution that is backward compatible • we don’t want to use tags to store additional metadata, such as platform or app version (which can be obtained from EventLogging instrumentation) Proposal Implement 3 distinct MediaWiki tags [1] mobile edit generic tag for all mobile edits mobile web edit tag specific to mobile web revisions mobile app edit tag specific to mobile app revisions Each mobile edit will get at least two tags. • run a maintenance script to remove spurious tags for mobile app account creations from change_tag and tag_summary • run a maintenance script looking for all instances of mobile edit without mobile web edit or mobile app edit and add tag them as mobile web edit This should be fully backward-compatible and allow flexible filtering by tag. Let us know if you have any question/concern. Dario [1] https://gerrit.wikimedia.org/r/#/c/139195/

4 5

New tablet-optimized mobile site now live for all tablet users
by Maryana Pinchuk 18 Jun '14

18 Jun '14

Today the WMF Mobile Web deployed a change to the default destination of users accessing Wikimedia projects from tablets – we're sending users to a new mobile view that's been optimized for larger touch-screen devices. You can learn more about this change here: http://blog.wikimedia.org/2014/06/17/wikimedia-sites-get-a-new-look-on-tabl… Please let us know if you're experiencing any issues as you browse Wikipedia or its sister projects on your iPad or Android tablet, and let us know what you think of the features and functionality. -- Maryana Pinchuk Product Manager, Wikimedia Foundation wikimediafoundation.org

1 0

[Apps] Biggest feature requests so far from the beta
by Dan Garry 17 Jun '14

17 Jun '14

Hi everyone, Since the Android beta release, we've been getting a lot of feedback about what people want added in. Here's an email listing some of those things, so we know what we've got to focus on. 1. Dark theme! A dark horse... no pun intended. By far the most requested feature. 2. Watchlist. The most requested feature from the editing community. 3. Searching within articles. Thanks, Dan -- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation

9 16

Wikipedia app release plan
by Yuvi Panda 17 Jun '14

17 Jun '14

Hello! 25th June is fast approaching, and we are on track to make the release with time to spare! Here's the proposed plan: 1. Release a final beta on Friday, 20th June. 2. Let people test the beta over the weekend, and up to 23rd. 3. Fix any bugs that pop up. No new feature work. Crashing bugs get priority. 4. Release on 25th! This means that any non-critical-bug fix has to be in place by this Friday. Is everyone ok with this plan, or does it feel like we are cutting it too short? Thanks! :) -- Yuvi Panda T http://yuvi.in/blog

2 1

Future of Windows 8.1 tablet app; support, unofficialize, or end-of-life?
by Brion Vibber 16 Jun '14

16 Jun '14

Microsoft sent me a report that our Windows 8.1 tablet app is having a crash-on-launch bug with today's featured articles; I've applied a quick fix and am submitting it to the Windows Store for update. This app was originally a prototype which I figured we'd rewrite if there was continued demand, but Windows 8/8.1 tablet apps just haven't taken the world by storm so far and we've not put work into it in a while... but it does have a non-zero maintenance cost picking up these little bugs. We may want to make sure we have an actual measure of its traffic usage before making a decision, but we don't think it's very high right now... A few possibilities: 1) Officially support the app for Windows 8.1 tablets, add support for Windows Phone 8.1, and continue to work on updating and improving the app alongside Android and iOS. 2) Transition it to an unofficial app "in-place", and I'll poke at phone support, media playback, and UI experiments on my own time. 3) Pick an official end-of-life date and kill it off entirely. If and when I or someone else want to make an unofficial version they can pick up the source and create a new app entry for people to download. Based on low demand and limited resources, I think we can safely throw out 1), so the choice is between 2) or 3). -- brion

5 5

Feedback about Android app from a blind user
by Yuvi Panda 16 Jun '14

16 Jun '14

Made me feel very happy, thought I should share :) > From the point of view of a blind Android user relying on Talkback, this > beta represents a profound improvement. Thank you, Wikimedia, for > getting accessibility right! > There are two defects you could clear up before releasing this app. > There are a couple unlabeled buttons in the U-I. > I have found nothing else to complain of so far! And, for that reason, I > expect to get much use out of this app. https://ticket.wikimedia.org/otrs/index.pl?Action=AgentZoom&TicketID=7609290 :) (We will fix the unlabeled buttons in the UI before release) -- Yuvi Panda T http://yuvi.in/blog

1 0

Re: [WikimediaMobile] [Wikitech-ambassadors] Roadmap and deployment highlights - week of June 16th
by Federico Leva (Nemo) 15 Jun '14

15 Jun '14

Greg Grossmeier, 14/06/2014 00:30: > Tablets will be sent to the mobile version of the project > websites. Previously they were sent to the desktop version. There is > a blog post and central notice drafted and ready to go out day of. Will someone be monitoring the effects [if any] on editing activity and number of active editors/new [10+ edits] editors? Nemo

2 3

git review issue (wmf/1.24wmf7)
by Jon Robson 13 Jun '14

13 Jun '14

The following patches https://gerrit.wikimedia.org/r/139278 https://gerrit.wikimedia.org/r/139379 are being sent to wmf/1.24wmf7 rather than master any idea why?

2 3

help with a commit?
by Chris McMahon 13 Jun '14

13 Jun '14

Hi Mobilers, Unfortunately the new toc.feature test is creating pages on enwiki. I made a commit to fix it, but for some reason when I do a regular git clone on the MobileFrontend repo I am not getting the master branch but the 1.24wmf7 branch instead. This commit really needs to be merged to master as soon as possible, but I don't know how to do that at this point: https://gerrit.wikimedia.org/r/#/c/139379/ -Chris

2 3

Re: [WikimediaMobile] help with a commit?
by Jon Robson 13 Jun '14

13 Jun '14

* every 2 weeks by this I mean beta labs and enwiki are always 1-2 weeks apart On 13 Jun 2014 09:59, jrobson(a)wikimedia.org wrote: The code in production changes every 2 weeks. It doesn't really justify regular Jenkins jobs. I could understand running them every Thursday on a deployment but that's about it.. On 13 Jun 2014 09:37, "Chris McMahon" <cmcmahon(a)wikimedia.org> wrote: I'd like to turn off browser tests in production, I don't think they bring much value. On Fri, Jun 13, 2014 at 8:12 AM, Jon Robson <jrobson(a)wikimedia.org> wrote: > Maybe it is time to consider turning off browser tests in production or at > least disabling the API URL variable on those servers to stop creation of > pages? > On 13 Jun 2014 08:10, "Chris McMahon" <cmcmahon(a)wikimedia.org> wrote: > >> >> Hi Mobilers, >> >> Unfortunately the new toc.feature test is creating pages on enwiki. >> >> I made a commit to fix it, but for some reason when I do a regular git >> clone on the MobileFrontend repo I am not getting the master branch but >> the 1.24wmf7 branch instead. >> >> This commit really needs to be merged to master as soon as possible, but >> I don't know how to do that at this point: >> https://gerrit.wikimedia.org/r/#/c/139379/ >> >> -Chris >> >> _______________________________________________ >> Mobile-l mailing list >> Mobile-l(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/mobile-l >> >>

1 0

Fwd: Page Styling Issues
by Yuvi Panda 13 Jun '14

13 Jun '14

Forwarding to mobile-l ---------- Forwarded message ---------- From: Vibha Bamba <vbamba(a)wikimedia.org> Date: Fri, Jun 13, 2014 at 6:25 AM Subject: Page Styling Issues To: Dan Garry <dgarry(a)wikimedia.org>, Monte Hurd <mhurd(a)wikimedia.org>, Moiz Syed <msyed(a)wikimedia.org>, Yuvaraj Pandian <yuvipanda(a)wikimedia.org>, Bernd Sitzmann <bsitzmann(a)wikimedia.org>, Dmitry Brant <dbrant(a)wikimedia.org > Monte and I have been recording Page styling Issues here - https://etherpad.wikimedia.org/p/App_Page_Styling Please add to this if you see broken styling. Include Article and Sections as necessary. Thanks Vibha ---- Vibha Bamba Senior Designer | WMF Design

2 2

Browser support for MobileFrontend
by Juliusz Gonera 12 Jun '14

12 Jun '14

Since our support table for browsers [1] is wildly out of date, we should come up with something better. Oliver generated some statistics for us from the last 30 days from logs for text/html requests (see attachment). I think we could divide browsers into Grade A and Grade B categories, similarly to desktop. Grade A would be full support, Grade B would be basic support for reading (non-JS version). Two additional suggestions: * Don't care about anything below < 0.1% * Drop support for JS for any problematic browser with < 0.5% (mark them as Grade B) I think coming up with a generic metric like "support last N versions of X and last M versions of Y" for all browsers would be hard because the browser landscape changes pretty fast. I'd rather reevaluate our support table every few months. For now, I propose the following: Grade A: * Mobile Safari 5-7 (that includes Chrome for iOS since it uses Safari's engine) * Android Browser 2.3+ (drop 2.3 to grade B as soon as it's < 0.5%) * Chrome for Android 18+ * Firefox for Android, latest version (since it's not very popular, but still a good browser) * IE Mobile 9+ (drop 9 to grade B as soon as it's < 0.5%) * Blackberry Webkit 7+ Grade B: * lower versions of browsers in Grade A * Opera Mini 4+ * NetFront 3+ * Ovi Browser 2+ * Nokia Browser 7+ When it comes to Grade B browsers, I don't think we should test on them very regularly, but accept bugs that come from their users. Comments? [1] https://www.mediawiki.org/wiki/Browser_support#Mobile_browsers -- Juliusz

5 11

[Apps] Dark theme discussion outcome
by Dan Garry 12 Jun '14

12 Jun '14

Vibha, May, Monte, Yuvi and I just met to discuss the dark theme work. For context, when we rolled out the Android beta, by far the most requested feature was a dark mode/night mode. The old beta had this, and people really loved it. For iOS, we've agreed to wait on implementing something, for two reasons. The first is that iOS already has a system-level setting for colour inversion which satisfies some of the user requirements. Secondly, users of this platform may not even want this feature, so it makes more sense for us to focus on page styling instead, which we agreed is not in as good of a state on iOS as it is on Android. For Android, we agreed the need is more pressing. May (who has some thoughts on the dark theming due to her previous work on the apps) will work with Vibha and Moiz to come up with a mockup for what kind of colouring we want to use. Then we'll start implementing this next sprint. This does mean that we won't have the dark theme at the time of the market release, but it'll be in shortly thereafter, so that's okay. Thanks everyone! Dan -- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation

2 1

Testing Knockoff
by Jon Robson 12 Jun '14

12 Jun '14

Sumanah poked me in IRC today to ask when we are scheduling time to give KnockOff / TAssembly a spin in MobileFrontend. Gabriel Wicke is looking for feedback...

3 8

Browser tests coverage in MobileFrontend stable (Result of spike 1687)
by Jon Robson 12 Jun '14

12 Jun '14

I ran an audit of the existing browser tests for MobileFrontend as part of a mobile team spike [1]. You can see the results here: https://www.mediawiki.org/wiki/Mobile/QA_Test_Audit_March_2014 Our coverage is actually not too bad, but there is definitely room from improvement. That said I have a big concern is around the organisation of the tests and how they are written and what is written - many of the tests could do with being reworded and a lot of them should probably actually be deleted. There is a lot of code duplication. When auditing I found tests scattered all over the place. This suggests that we could benefit from reorganising the file structure to be more logical, in particular features that relate to special pages should have their own folder (this is particularly useful for clarifying what tests the watch star and what tests the actual watchlist page - Zeljko / Chris is it possible to have subfolders in the features directory that contain features?). I would also suggest the following actions for improving our test coverage: * Add tests for error handling on login / account creation * Add tests for this page has issues * Improve tests for key editing and upload workflows * Add tests for Language variant support * Add tests for full text search support * Improve the existing watch star tests so they actually check the end result * Add test to check the user can close the left navigation menu * Add tests for logout * Add tests for reference overlay * Add tests for toggling * Add tests for Nearby in skins other than Minerva (mobile skin) * Address hygiene issues on https://www.mediawiki.org/wiki/Mobile/QA_Test_Audit_March_2014 [1] https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1687

3 5

Re: [WikimediaMobile] Provisional iOS release date: 7th July
by Tomasz Finc 11 Jun '14

11 Jun '14

Actually cc'ing mobile-l this time instead of just saying it ... On Wed, Jun 11, 2014 at 11:56 AM, Tomasz Finc <tfinc(a)wikimedia.org> wrote: > CC'ing mobile-l to get this archived and for others to know that its coming. > > Dan, given that we can't easily ship a beta within the iTunes store > what will the mechanics of the release look like? > > --tomasz > > On Wed, Jun 11, 2014 at 11:48 AM, Dan Garry <dgarry(a)wikimedia.org> wrote: >> Hey guys, >> >> Vibha, Moiz, Monte, Brion and I just met to get a date together for the >> release of the iOS app. We arrived at 7th July (3.5 weeks from now, the end >> of the next sprint). Here's how. >> >> I asked the engineers and designers what they felt the dependencies were. We >> identified: >> >> Edit workflow refinements (current sprint) >> Onboarding (first time UX) (current sprint) >> TOC refinement (next sprint) >> Styling refinement (next sprint) >> General bug fixes and cleanup (next sprint) >> >> The first three are hard requirements; if they're not in, then we will delay >> the release. The last two are softer requirements, particularly since we can >> update the app CSS without pushing out a new release. >> >> It was a careful negotiation! Monte originally wanted an extra sprint of >> slack, but I managed to arrive at the two sprint number by assuring him that >> if something game-breaking came up then we'd delay the release. I think the >> user feedback is really important, so I think it's worth setting the goal to >> be sooner rather than later. >> >> The cool thing is, this means the iOS release will only be two weeks after >> the Android one. Woohoo! >> >> We're all happy with this date. I'm meeting with Katherine tomorrow to >> discuss what the best communications strategy for this is. >> >> Thanks, >> Dan >> >> -- >> Dan Garry >> Associate Product Manager for Platform and Mobile Apps >> Wikimedia Foundation

1 0

Funding for development of WikiTrack mobile app approved
by Ryan Kaldari 11 Jun '14

11 Jun '14

This is essentially an app that gives you a mobile-friendly interface for tracking Recent Changes, Watchlist Changes, and Contributions on Wikipedia projects. See https://meta.wikimedia.org/wiki/Grants:IEG/WikiTrack for more information. Ryan Kaldari

2 1

VE on Android tablets
by Juliusz Gonera 10 Jun '14

10 Jun '14

I tried VE on the two working Android tablets that we have: Samsung Galaxy Tab 10.1 (Android 4.0.4) and Nexus 7 (Android 4.4.2). Samsung uses Android Browser and VE performs slowly and buggy there. Link inspector works better than on iOS but there are other small bugs like problems with some icons not being scaled properly or occasional rendering issues. Nexus 7 with Kitkat has Chrome as its default browser and everything works fine there, I would even say it works better than iPads. Kaldari is doing more research regarding which tablets should be redirected to mobile. -- Juliusz

2 3

[Apps] Conclusions on abuse filter in edit workflow
by Dan Garry 09 Jun '14

09 Jun '14

Hi everyone, This edit concerns discussions that Vibha, Yuvi and I have had about the abuse filter today. As it is part of the edit workflow, these discussions took place to unblock the card. The abuse filter works just fine on both platforms, but the design leaves a bit to be desired. For those of us who are unfamiliar with the abuse filter, I've prepared a short write-up in this Google Doc <https://docs.google.com/a/wikimedia.org/document/d/1VIIQhkribQuJa-6ugm3XM5d…> that explains what the abuse filter is. Here's the outcome of the discussions: 1) The abuse filter stuff has been broken off of the edit workflow cards and placed onto its own card here. This unblocks the iOS card, and then the Android card is only blocked by waiting for the relevant design. 2) The interaction of the designs on iOS is good. The design restyling that's in the edit workflow changes card can take place, but the functionality can remain the same. This goes for Android too. Let me know if you've got any questions! Thanks, Dan -- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation

1 0

Sprint 33: The Final (Android) Countdown begins!
by Dan Garry 09 Jun '14

09 Jun '14

Hi everyone, Our final sprint before the Android release has come! Woohoo! There are a few blocked cards in Trello: 1. Edit workflow changes: This card is awaiting the Android design. I've followed up with Vibha and Moiz and the design should be available by the end of the day today. 2. Re-do buttons for progressive styling: I think Monte and Moiz had some discussions about this last week but I'm not sure what came of it. Monte, can you update the card? 3. TOC bar: Blocked on us making a decision about whether the TOC button should have a spinner or not. Did we reach a decision about this? 4. More menu: Blocked on me making a decision about what should go in the menu. I will do that today and note on the card. Thanks everyone! Dan -- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation

2 1

[Apps] Edit workflow refinements
by Dan Garry 06 Jun '14

06 Jun '14

Hi all, Monte, Yuvi, Vibha, Moiz, Jared, Howie and I met today to talk about refining the edit workflow on the apps. The statement of the problem is that user testing has shown that in the current workflow the preview step is not useful; people are not recognising that it is a preview, not recognising the edit summary box is there, and accidentally abandoning their edits because they think they've saved already. This is related to the fact that there are too many steps in the edit workflow. In particular, the call to action to "sign in and save" or "save anonymously" was basically ignored by everyone who tested the app. Our macro-level goal for the app is to get people to edit. Whether that's by signing in and saving or by saving anonymously isn't as important to us as *actually getting them to edit.* Our course of action is therefore multi-faceted: 1. For the MVP we're removing the call to action to sign in and save. Since people are ignoring it, it's not really serving any purpose in the current workflow except to bloat it. This drastically reduces the number of steps in the process. 2. We're flipping the edit summary box and preview around, so that when you make a change and click next you see the edit summary on top. This makes it clearer that your edit hasn't saved, it emphasises the canned edit summaries that users responded positively to in the testing, and makes the preview step feel more optional. We're also going to restyle this page slightly to make it clearer. The workflow for editing is now press edit > make change > press next > enter edit summary (and optionally view preview) > save. This makes the workflow much easier to use, and a lot clearer. I realise that my description above isn't great; Vibha and Moiz are going to create a mockup for it, and I'll share that on this list once we've got it. Thanks everyone! Dan -- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation

2 3

Android app user feedback and requests
by Dmitry Brant 06 Jun '14

06 Jun '14

Hey all, Here's an etherpad with an aggregate of what our users have been asking for, so far (since the beta release): http://etherpad.wikimedia.org/p/androidappfeedback -Dmitry

4 6

Mobile tags for Wikipedia android app
by Dario Taraborelli 06 Jun '14

06 Jun '14

This afternoon Dan and I reviewed how tags from the android app are captured in the change_tag and tag_summary tables. (1) We noticed that the “mobile app edit” tag is applied to recentchanges events that are not edits, but new account registrations: SELECT * FROM enwiki.change_tag WHERE ct_rev_id IS NULL AND ct_tag = "mobile app edit"; ct_rc_id ct_log_id ct_rev_id ct_tag ct_params 661123291 56899294 NULL mobile app edit NULL 661123407 56899301 NULL mobile app edit NULL 661124928 56899375 NULL mobile app edit NULL 661127933 56899610 NULL mobile app edit NULL 661128644 56899685 NULL mobile app edit NULL 661131626 56899908 NULL mobile app edit NULL 661133278 56899998 NULL mobile app edit NULL 661134572 56900072 NULL mobile app edit NULL 661140653 56900620 NULL mobile app edit NULL 661155198 56901558 NULL mobile app edit NULL 661155799 56901593 NULL mobile app edit NULL 661156983 56901659 NULL mobile app edit NULL AFAIK this is unusual behavior for tags and will create artifacts in tagged revisions unless people are aware that all these registration-related events always need to be excluded (it’s also confusing because the name of the tag explicitly refers to an edit). As suggested earlier [1], we should not track the source of account registrations via MediaWiki tags but via the ServerSideAccountCreation log. (2) edits made on apps should be stored with two separate tags: “mobile edit” and “mobile app edit”. The tags are correctly stored in the change_tag table with 2 records for each revisions, e.g. SELECT * FROM enwiki.change_tag WHERE ct_rc_id = 661110028; ct_rc_id ct_log_id ct_rev_id ct_tag ct_params 661110028 NULL 611585155 mobile app edit NULL 661110028 NULL 611585155 mobile edit NULL but when the tags are combined in the tag_summary table, the “mobile app edit” tag is lost: SELECT * FROM enwiki.tag_summary WHERE ts_rc_id = 661110028; ts_rc_id ts_log_id ts_rev_id ts_tags 661110028 NULL 611585155 mobile edit This should not be the case, the 2 tags should be concatenated in the ts_tags field, see for example this desktop revision with 2 tags: SELECT * FROM enwiki.change_tag WHERE ct_rc_id = 578489188; ct_rc_id ct_log_id ct_rev_id ct_tag ct_params 578489188 NULL 555564321 gettingstarted edit NULL 578489188 NULL 555564321 visualeditor NULL SELECT * FROM enwiki.tag_summary WHERE ts_rc_id = 578489188; ts_rc_id ts_log_id ts_rev_id ts_tags 578489188 NULL 555564321 gettingstarted edit,visualeditor I believe that neither (1) nor (2) is intended behavior for apps. Can you guys confirm and if so, can we fix this? Dario [1] http://lists.wikimedia.org/pipermail/mobile-l/2014-May/007150.html

7 10

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l June 2014