Last modified: 2014-03-26 18:02:00 UTC
Feature request for common watchlists, that can be maintained by users or bots. Logged-in users can subscribe to a particular common watchlist, so that changes to pages on the list appear directly on their personal watchlist. Motivation and details on a possible implementation given at the url. It's a sort of enhancement of the extension PovWatch; the proposed implementation uses a UI similar to the AbuseFilter one.
*** This bug has been marked as a duplicate of bug 7467 ***
Reopened. bug 7467 is to allow users to have public (additionally to private) personal watchlists, while the present bug is for common watchlists, centralized and maintained by users and bots with appropriate permissions - described at the url.
The principle remains the same: the ability to maintain separate watchlists (with varying degrees of access). Re-suggest DUPING.
why don't you just use relatedchanges feature?
(In reply to comment #3) > The principle remains the same: the ability to maintain separate watchlists > (with varying degrees of access). Re-suggest DUPING. > The principle is fundamentally different, bug 7467 and bug 5875 are about personal/user watchlists, splitting them or changing their visibility, while this bug is about developing common watchlists (CW), hosted for example at Special:CommonWatchlists/1, Special:CommonWatchlists/2, ... editable by users with CW editor permissions, that can be created and marked as deleted by CW admins, etc (see http://strategy.wikimedia.org/wiki/Proposal:Common_watchlists). A user can subscribe to a particular CW so that all pages on the CW appear directly on their user watchlist (similarly to PovWatch). It requires a whole new extension or heavy upgrade of PovWatch. (In reply to comment #4) > why don't you just use relatedchanges feature? > It's been tried, some wikiprojects have their watchlists, and some pages listing articles like [[Template:Popular articles]] propose this functionality, but it's not much used, and often the pages end up no longer updated and people cease to use them; because it's very impractical to use and limited: you need to access the relatedchanges for the page, and of course there is no dynamic way to add to your watchlist all pages linked on a given page. It's also cumbersome to update, you need to sort them, link the talk pages too, while a common watchlist editor similar to the raw watchlist editor would be simple to use and sort automatically. So common watchlists could be deployed widely, and linked from [[Special:Watchlist]] in some way. In fact it's a heavy enhancement of PovWatch, and you can see support for it being enabled at [[Wikipedia:Village pump (proposals)/Archive 52#PovWatch]] - bug 20523.
(In reply to Cenarium from comment #5) > It's been tried, some wikiprojects have their watchlists, and some pages > listing articles like [[Template:Popular articles]] propose this > functionality, but it's not much used[...] Why would this feature be any different? > [...], and often the pages end up no longer > updated and people cease to use them; because it's very impractical to use > and limited: you need to access the relatedchanges for the page, and of > course there is no dynamic way to add to your watchlist all pages linked on > a given page. This may be true, but it should not be /too/ hard to get the page names and add them with the raw watchlist editor. > It's also cumbersome to update, you need to sort them[...] You don't strictly *need* to sort them. > [...], link the talk pages too[...] You may be able to use a template for that. > [...], while a common watchlist editor similar to the raw > watchlist editor would be simple to use and sort automatically. > So common watchlists could be deployed widely, and linked from > [[Special:Watchlist]] in some way. In fact it's a heavy enhancement of > PovWatch, and you can see support for it being enabled at > [[Wikipedia:Village pump (proposals)/Archive 52#PovWatch]] - bug 20523.
(In reply to PiRSquared17 from comment #6) > (In reply to Cenarium from comment #5) > > [...], link the talk pages too[...] > You may be able to use a template for that. That could be a separate ticket (enhancement) for RecentChangesLinked.
