Last modified: 2013-04-08 11:01:42 UTC
It would be nice it frequently updated special pages, such as Recent Changes, Watchlist, Block log, Page creation log, page history and possibly others, would live-update themselves frequently, in the style of identi.ca. RC patrollers would probably appreciate it.
They do but several special pages on the WMF cluster are disabled due to load issues. *** This bug has been marked as a duplicate of bug 15434 ***
whoops misread what you wrote.
Here's a website that does something similar: http://wikistream.inkdroid.org/
Some user scripts which may be of interest: * [[meta:User:Krinkle/Tools/Real-Time Recent Changes]] * [[User:Lupin/Anti-vandal tool]]
I'm closing this bug because imho it is too generic to be feasible. (In reply to comment #0) > It would be nice if frequently updated special pages, such as Recent Changes, > Watchlist, Block log, Page creation log, page history and possibly others, > would live-update themselves frequently, in the style of identi.ca. RC > patrollers would probably appreciate it. They are all special pages, and you could make a gadget in < 10 minutes that just polls itself and auto-refreshes with AJAX. That would work fine, but is not very flexible, efficient and has some usability issues (e.g. the page is replaced, and whatever you were doing is gone). So that is not a way we can do it in core, but one could create a gadget that does that. Having said that, whatever the solution is going to be, it should be optimized for the specific use case. For example, for patrolling recent changes the (imho) most appropiate solution is to make use of a push feed in the browser and implement a proper patrolling workflow (see bug 5560 for that, which depends on bug 29305). So for the most common use case requested in this bug, it is a dupe of bug 5560 / bug 29305. The other examples (refreshing block log...), those are already covered by recent changes. And if so desired, it could be easily implemented on those individual special pages as well - that is, as soon as we have it working for the catch-all recent changes. (for the individual special pages one just tabs into the same feed, listen for rc.type=log where log_action is block, and then use the interface messages / html templates to inject list items on the page). *** This bug has been marked as a duplicate of bug 5560 ***
