https://bugzilla.wikimedia.org/show_bug.cgi?id=18241
--- Comment #1 from Splarka <[email protected]> 2009-03-29 14:58:19 UTC --- Probably either bug 18228 or bug 18229 could solve this in the long run. Note that domas has optimized rc by about 30% with some live hacks, but is not yet willing to reinstate a higher limit. I've created a little script that might help you in the (time-critical) meantime: http://en.wikipedia.org/wiki/User:Splarka/ajaxrecentchanges.js It takes advantage of the fact that the API can paginate recent changes data. It works pretty good, and immitates most featurs of regular recent changes, plus lets you sort with very advanced options (any grouping of namespaces, any type/filter combo) and has ajax patrol buttons for one-click patrol (disabled by default) and can be localized by editing the arc-i18n. It does have limitations (as of this comment): * If you leave the page, all your data is lost, best to do all operations in new tabs. * It doesn't perfectly immitate the RC, I skipped some pointless UI and didn't put in rollback links. * If rc patrolling is disabled, it mistakenly shows a red "!" for every edit, this will be fixed in the next scap. If you have any questions about it -> http://en.wikipedia.org/wiki/User_talk:Splarka -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
