Cross-wiki watchlists
Open, NormalPublic

"Like" token, awarded by waldyrious."Love" token, awarded by mfb."Love" token, awarded by Ladsgroup."Love" token, awarded by MGChecker."Pterodactyl" token, awarded by Man77."Love" token, awarded by Ricordisamoa."Like" token, awarded by Negative24."Like" token, awarded by Kozuch."Like" token, awarded by Nemo_bis."Love" token, awarded by He7d3r.
Assigned To
Authored By
bzimport, Sep 21 2005


Author: acrush

Please consider providing wikimedians with crosswiki watchlists. Such could also
be made public as an option.

See Also:

There are a very large number of changes, so older changes are hidden. Show Older Changes

Before suggesting this to students, should we check with dba folks (@Springle) if having a single db that gets a write on any edit to any of our 300-odd projects (as that is the approach suggested above) would be problematic (i know very little about the write load performance considerations for our dbs or if globally the number of edits has big bursts, so probably this scheme is obviously ok and im just being pessemistic. If it was a problem there are probably ways around it [e.g. inserting in batches with a script with plenty of wait for slaves or something] so possibly still a good gsoc project, but i think this is something we should determine up front)

Providing the updates to the hypothetical[1] global database could be applied as asynchronous batches via jobrunners, the write load would be manageable.

The read load might actually be the more interesting problem. Currently we have watchlist queries segregated from normal traffic so they hit specific slaves in each shard which treats caches nicely and minimizes the blast radius when something goes south. Running a global watchlist might actually improve this arrangement overall; the separation would reduce the freedom to run some of the current complex joins and encourage a more scalable approach.

[1] We already have a few global databases. Eg, centralauth, flowdb, and wikishared on extension1.

@Springle, would you like to mentor this project?

In T5525#1104132, @NiharikaKohli wrote:

@Springle, would you like to mentor this project?

Probably not alone since I'm not a developer. Happy to team up though.

From a brief chat with @Legoktm and @yuvipanda, it appears this project might be a little too big for GSoC. If we could break down the task into smaller chunks, perhaps separating the backend and frontend implementation, it might be more doable.

I've made a prototype for a cross-wiki watchlist as an OAuth tool:
It's currently very limited, as it only queries a list of hand-picked projects and doesn't offer any options. I would like to actually build it as an GSoC project, anyone willing to mentor such a project?

Building it as an OAuth webapp and not as an extension has the advantages of not being confined by the requirements of code review, scalability or modifying existing complex code and database structures. It also allows greater freedom to do things differently and experiment with the UI. While it currently looks similar to the well-known mediawiki watchlist I don't think it will when it's "released". To pick a particular feature I would like to add support for inline diffs as discussed in T53958: Watchlist and recent changes should be able to show diffs inline.

The prototype uses AngularJS for the frontend and python for the backend. I've build it by basically forking a different prototype: T91490: Proposal: A semi-automatic find and replace webapp. See that task for a more implementation details.

Feel free to ping me in IRC, I idle around in the usual channels with the nick sitic.

An external tool would not meet the requirements to fix this bug, but may be useful (IIRC we already had such tools in the past): please file it as a separate task.

Qgil edited the task description. (Show Details)Mar 17 2015, 2:03 PM
Negative24 added a subscriber: Negative24.
Qgil added a comment.Mar 19 2015, 10:06 AM

T92955: An enhanced cross-wiki watchlist as an OAuth tool is looking for mentors and feedback. Your help is appreciated. The deadline for GSoC submissions is 27 March, in 8 days.

Erwin removed a subscriber: Erwin.Mar 19 2015, 10:13 AM
Ricordisamoa added a subscriber: Ricordisamoa.
Man77 added a subscriber: Man77.Mar 23 2015, 1:12 PM
Man77 awarded a token.Apr 15 2015, 8:58 AM
jayvdb added a subscriber: jayvdb.Jun 21 2015, 8:15 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 25 2015, 11:35 AM
Ladsgroup added a subscriber: Ladsgroup.

I see that gamepedia wikis have a "GlobalWatchlist" extension. Can someone register there and see how it works? It would be nice to ask Curse to publish it on gerrit, but maybe the code is already published somewhere.

WTM added a subscriber: WTM.Sep 15 2015, 11:42 AM
Qgil added a comment.Sep 23 2015, 9:04 AM

This task is listed under "Missing mentors" at Possible-Tech-Projects. Are there mentors willing to propose it for Outreachy-Round-11 (December-March, although the application period is starting soon and we already have potential candidates looking for project ideas).

Qgil added a comment.Sep 23 2015, 9:36 AM

This is a message sent to all Possible-Tech-Projects. The new round of Wikimedia Individual Engagement Grants is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after (T105414). If someone is interested in obtaining funds to push this task, this might be a good way.

Alexia added a subscriber: Alexia.Sep 23 2015, 4:11 PM

The GlobalWatchlist extension that runs on Gamepedia is tied heavily into the Curse account system to be able to use a single user identifier. Exactly like the global_id used by Extension:CentralAuth. Releasing it in its current state would result in code that is unusable by anyone else. There are future plans for the team, one year or more, to rework the Curse account system so that extensions that rely on it can be easily decoupled.

mfb awarded a token.Dec 1 2015, 12:25 PM
mfb added a subscriber: mfb.
Alexia removed a subscriber: Alexia.Dec 15 2015, 9:37 PM
Nizil added a subscriber: Nizil.Dec 15 2015, 9:57 PM
Aschroet removed a subscriber: Aschroet.Dec 15 2015, 9:57 PM
Matiia added a subscriber: Matiia.Dec 16 2015, 12:50 AM
Ltrlg added a subscriber: Ltrlg.Dec 16 2015, 4:06 PM
Ata added a subscriber: Ata.Dec 23 2015, 4:29 PM

Crosswatch tool exists.

Johan added a subscriber: Johan.Jan 13 2016, 6:47 AM
IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.
Base added a subscriber: Base.Jan 26 2016, 10:24 AM
Qgil removed a subscriber: Qgil.Feb 12 2016, 8:40 AM
Meno25 removed a subscriber: Meno25.Feb 22 2016, 7:14 PM
Sumit added a subscriber: Sumit.Mar 1 2016, 5:37 PM
IMPORTANT: This is a message posted to all tasks under "Need Discussion" at Possible-Tech-Projects. Wikimedia has been accepted as a mentor organization for GSoC '16. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.

@Sumit @Qgil This is one of the top 10 wishlist projects for Community Tech. We're going to be working on this soon, and coordinating with the TCB's watchlist project. I don't think this is a good project for Hackathon/GSoC.

And too big a task for GSoC as per previous discussions.

To support the cross-wiki watchlist project, we're running a survey about how active contributors use their watchlists. The results will help inform the requirements and design for the cross-wiki watchlist.

I'm sure everybody subscribed on this ticket has opinions about their watchlists :) -- so feel free to participate in the survey:

It's hosted on a third-party service. We'll be running the survey for about a week, and once it's closed, we'll publish aggregated results on Meta.

If you're interested in how we're going to collect and use the data, here's the Privacy Statement:

Posting a survey announcement is unusual behavior on a Phab ticket, so I hope this doesn't break Phab law in some way. Thanks.

Qgil removed a subscriber: Qgil.Mar 30 2016, 9:49 AM
Johan mentioned this in Unknown Object (Task).Apr 8 2016, 1:33 PM

Add Comment