ayg wrote:

This is not currently configurable on a per-wiki basis. Ideally, we should fix the code so that it doesn't take a ludicrous amount of time to format 5000 rows, and reenable it for everyone . . . or just add paging.

stanley wrote:

The current recentchanges url is not consistent with its logic. According to logic, "..&from=20090326145934&limit=500&..." should provide all recent changes started from the older post (20090326145934) and 500 newer post. The current logic is calculated from the newer post (now) and 500 older post, therefore it should be changes to "..&from=now&limit=500&..." :D. I can live with the 500 limit if you change this sort method. :D

stanley wrote:

Anyone. Please dont limit rc to 500. If 5000 is too many, 3000 or 2000 is fine. 500? How can you expect people to monitor vandal with this restriction?

herd wrote:

(In reply to comment #2)

The current recentchanges url is not consistent with its logic. According to
logic, "..&from=20090326145934&limit=500&..." should provide all recent changes
started from the older post (20090326145934) and 500 newer post. The current
logic is calculated from the newer post (now) and 500 older post, therefore it
should be changes to "..&from=now&limit=500&..." :D.

That is bug 18228. Note this is possible with the API, so you can fake it (eg: http://en.wikipedia.org/wiki/User:Splarka/ajaxrecentchanges.js ).

Now the maximum limit seems to be 5000. So WORKSFORME (or maybe dupe of bug 18241).