Public and private watchlists, shared watchlists


Author: ml4macdo

would it be possible to allow other people to see the pages you are watching? this
would be very useful for WikiProject coordination.

to avoid privacy issues, you could have a "public watchlist" and a "private

it has been suggested many times that a link from each page "users watching this page",
may deter vandals; but understandably, it may attract some to pages that aren't being
publicly watched (even though they may be privately watched). is this a conceivable

Version: unspecified
Severity: enhancement

bzimport added a project: MediaWiki-Watchlist.Via ConduitNov 21 2014, 9:25 PM
bzimport added a subscriber: Unknown Object (MLST).
bzimport set Reference to bz7467.
bzimport created this task.Via LegacyOct 2 2006, 1:17 PM
bzimport added a comment.Via ConduitOct 2 2006, 1:27 PM

jimmy.collins wrote:

There is an extension but it
don't differ between public and private.

Changing severity to enhancement because it's a feature reuqest - not a bug.

bzimport added a comment.Via ConduitOct 2 2006, 2:59 PM

ml4macdo wrote:

i see; so that watchers extension is unlikely to be implemented in English
Wikipedia.. but what about one that distinguishes public and private, is there a
chance for that?

bzimport added a comment.Via ConduitOct 30 2006, 3:31 AM

robchur wrote:

You need a special page for this? I mean, a simple user subpage ("Pages I'm
Watching") wouldn't suffice?

bzimport added a comment.Via ConduitNov 3 2006, 6:26 PM

dunc_harris wrote:

Yes, you can make a public watchlist by creating a subpage, e.g.
[[User:Example/Publicwatchlist]] and then by going to
[[Special:Recentchangeslinked/User:Example/Publicwatchlist]] which will show the
related changes.

Though obviously this is non-standard, and perhaps a little inelegant. When bug
1492 multiple watchlists is
implemented, maybe it would be possible to make some watchlists public and some not.

bzimport added a comment.Via ConduitNov 3 2006, 10:18 PM

robchur wrote:

How is it nonstandard or inelegant? The reason watchlists are implemented as now
is to keep them private. You can do a public watchlist in the manner described

It would be nice to have it all incorporated as part of a new watchlist
mechanism, but it isn't going to be critical, is it?

aaron added a comment.Via ConduitMay 10 2007, 3:57 PM

(In reply to comment #5)

How is it nonstandard or inelegant? The reason watchlists are implemented as now
is to keep them private. You can do a public watchlist in the manner described

It would be nice to have it all incorporated as part of a new watchlist
mechanism, but it isn't going to be critical, is it?

Seconded, and this just seems to feature creep and add more complexity without
justifiable gain.

siebrand added a comment.Via ConduitFeb 2 2009, 10:44 AM

Add dependency on bug 5875

siebrand added a comment.Via ConduitFeb 2 2009, 11:42 AM

Changing component to "Watchlist"

demon added a comment.Via ConduitOct 22 2009, 7:07 PM
  • Bug 21223 has been marked as a duplicate of this bug. ***
Cenarium added a comment.Via ConduitOct 23 2009, 4:33 PM

bug 21223 is not a duplicate, it's for common watchlists, centralized and maintained by users or bots with appropriate permissions, and not necessarily public in any case - described in full at

Common watchlists would allow for coordination though, it's even their prime motivation. So with this in consideration, as above, I don't see the need for a public personal watchlist and agree it would have some downsides not worth the implementation cost.

Ricordisamoa added a subscriber: Ricordisamoa.Via WebFeb 3 2015, 5:40 PM
Daniel_Mietchen added a subscriber: Daniel_Mietchen.Via WebFeb 3 2015, 7:33 PM
Tbayer added a subscriber: Tbayer.Via WebFeb 3 2015, 11:01 PM
Nemo_bis added a subscriber: Nemo_bis.Via WebFeb 4 2015, 7:16 AM

The Education extension allegedly covers the "shared watchlists" feature.
That part should perhaps be split out of the extension and integrated in core?

Nemo_bis changed the title from "public and private watchlists" to "Public and private watchlists, shared watchlists".Via WebFeb 4 2015, 7:17 AM
Nemo_bis added a project: Epic.
Nemo_bis set Security to None.
Elitre added a subscriber: Elitre.Via WebFeb 4 2015, 11:56 AM
Mattflaschen added a comment.Via WebFeb 5 2015, 1:00 AM

The mobile team is also working on Gather, which has a similar public list concept, though more oriented towards readers (at least for the initial version).

It would be good to have some core support for this.

Nemo_bis added a comment.Via WebFeb 5 2015, 8:42 AM

Readers don't exist. I'd rather say the proposal mentioned above doesn't have a clear use case yet.

Moushira added a subscriber: Moushira.Via WebFeb 13 2015, 11:05 PM
Jdlrobson added a subscriber: Jdlrobson.Via WebMar 18 2015, 1:17 AM

I'm going to make this happen. I've been hacking on an editor version of Gather in spare time. Hoping we can get together at Wikimedia-Hackathon-2015 and make this happen.

Florian added a subscriber: Florian.Via WebMar 23 2015, 9:22 PM
Alsee added a subscriber: Alsee.Via WebMay 8 2015, 2:26 PM Maybe a nitpick but there's no mention that history actions need to show up in User Contribution History too, and everything should be Oversightable. Extra care is needed for any user-controlled content in Special. It doesn't get the automatic infrastructure that exists for wiki pages.

If this does get built, I'm not sure the current proposal provides the desired functionality. Or maybe there needs to be a second kind of shared watchlist with different functionality? This proposal doesn't create a "shared watchlist", it creates a shared list of pages that anyone can add to their own watchlist. It creates redundant parallel watching, not coordinated watching.

How about a list that has *it's own* last access date for each page listing. I check the list and see [apple] has an unreviewed new change (based on the list's access date). I check [apple], I see it's good. I then click [apple] as reviewed on the shared watchlist. My last-access-date for [apple] gets copied into the watchlist date for [apple] (only if my date is newer). My username gets copied onto the list next to [apple], identifying me as the reviewer. Bob checks the list and sees no new changes for [apple] because I already reviewed it. If Bob looks further he finds my name next to the no-new-change [apple] listing. If he trusts me, we just coordinated and saved 30 people from redundant review work. If Bob doesn't trust me, he can re-check [apple]. If [apple] is bad then Bob can red-flag [apple] in the shared list. Bob can post elsewhere that I'm a bad reviewer. It would be up to the community to deal with that.

Moushira added a comment.Via WebMay 9 2015, 8:25 PM

Thanks for the elaboration on the exact story for a shared watchlist concept Alsee. As you mentioned, your scenario is different from what is proposed on this ticket, both are needed, however, they serve different causes, as you mentioned.

Glaisher added a subscriber: Glaisher.Via WebMay 24 2015, 3:49 AM
mgrabovsky added a subscriber: mgrabovsky.Via WebMay 24 2015, 9:05 AM
Scott reopened blocking task T3492: Multiple watchlists as "Open".Via WebOct 6 2015, 7:43 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptVia HeraldOct 6 2015, 7:43 PM

Add Comment