Return to Question

I was looking at Am I allowed to use/create robots to track questions? just now and started wondering whether my current userscript to help with reviewing has quite the right internal rate limits. It reloads the page* every so often (30 seconds on SO, 5 minutes elsewhere) if there's no review ready to go, but since I have access to a number of queues, that loads things down a bit more.

On the other hand, because it makes no attempt to maintain the lock on any items, it's really limited as much by my manual review speed as anything else, except in times where there's nothing to review for a while in any queue. Max load at present would be about 13 per minute across three sites.

I'm not aware of any specific rate limits that would apply, so this is really more a matter of good manners, I suppose. It's not as though one user loading ~10 extra pages/min is a problem; it's the principle of the thing.

Is this script sanely self-limited? Or should I tweak the timing some more?

(Note: For clarity's sake, although I really hope I don't actually need to say this, I do not have any scripts to automate any review actions. That would be a remarkably stupid idea.)

(In case anyone on SO is wondering, yes, this is how I manage to cap Late Answers first each day. Gasp!)

_{*One of these days I'll try again to get the AJAX loading to work. It's oddly less trivial than I'd expect.}

I was looking at Am I allowed to use/create robots to track questions? just now and started wondering whether my current userscript to help with reviewing has quite the right internal rate limits. It reloads the page* every so often (30 seconds on SO, 5 minutes elsewhere) if there's no review ready to go, but since I have access to a number of queues, that loads things down a bit more.

On the other hand, because it makes no attempt to maintain the lock on any items, it's really limited as much by my manual review speed as anything else, except in times where there's nothing to review for a while in any queue. Max load at present would be about 13 per minute across three sites.

I'm not aware of any specific rate limits that would apply, so this is really more a matter of good manners, I suppose. It's not as though one user loading ~10 extra pages/min is a problem; it's the principle of the thing.

Is this script sanely self-limited? Or should I tweak the timing some more?

(Note: For clarity's sake, although I really hope I don't actually need to say this, I do not have any scripts to automate any review actions. That would be a remarkably stupid idea.)

(In case anyone on SO is wondering, yes, this is how I manage to cap Late Answers first each day. Gasp!)

_{*One of these days I'll try again to get the AJAX loading to work. It's oddly less trivial than I'd expect.}

I was looking at Am I allowed to use/create robots to track questions? just now and started wondering whether my current userscript to help with reviewing has quite the right internal rate limits. It reloads the page* every so often (30 seconds on SO, 5 minutes elsewhere) if there's no review ready to go, but since I have access to a number of queues, that loads things down a bit more.

On the other hand, because it makes no attempt to maintain the lock on any items, it's really limited as much by my manual review speed as anything else, except in times where there's nothing to review for a while in any queue. Max load at present would be about 13 per minute across three sites.

I'm not aware of any specific rate limits that would apply, so this is really more a matter of good manners, I suppose. It's not as though one user loading ~10 extra pages/min is a problem; it's the principle of the thing.

Is this script sanely self-limited? Or should I tweak the timing some more?

(Note: For clarity's sake, although I really hope I don't actually need to say this, I do not have any scripts to automate any review actions. That would be a remarkably stupid idea.)

(In case anyone on SO is wondering, yes, this is how I manage to cap Late Answers first each day. Gasp!)

_{*One of these days I'll try again to get the AJAX loading to work. It's oddly less trivial than I'd expect.}

I was looking at Am I allowed to use/create robots to track questions? just now and started wondering whether my current userscript to help with reviewing has quite the right internal rate limits. It reloads the page* every so often (30 seconds on SO, 5 minutes elsewhere) if there's no review ready to go, but since I have access to a number of queues, that loads things down a bit more.

On the other hand, because it makes no attempt to maintain the lock on any items, it's really limited as much by my manual review speed as anything else, except in times where there's nothing to review for a while in any queue. Max load at present would be about 13 per minute across three sites.

I'm not aware of any specific rate limits that would apply, so this is really more a matter of good manners, I suppose. It's not as though one user loading ~10 extra pages/min is a problem; it's the principle of the thing.

Is this script sanely self-limited? Or should I tweak the timing some more?

(Note: For clarity's sake, although I really hope I don't actually need to say this, I do not have any scripts to automate any review actions. That would be a remarkably stupid idea.)

(In case anyone on SO is wondering, yes, this is how I manage to cap Late Answers first each day. Gasp!)

_{*One of these days I'll try again to get the AJAX loading to work. It's oddly less trivial than I'd expect.}

I was looking at Am I allowed to use/create robots to track questions? just now and started wondering whether my current userscript to help with reviewing has quite the right internal rate limits. It reloads the page* every so often (30 seconds on SO, 5 minutes elsewhere) if there's no review ready to go, but since I have access to a number of queues, that loads things down a bit more.

On the other hand, because it makes no attempt to maintain the lock on any items, it's really limited as much by my manual review speed as anything else, except in times where there's nothing to review for a while in any queue. Max load at present would be about 13 per minute across three sites.

I'm not aware of any specific rate limits that would apply, so this is really more a matter of good manners, I suppose. It's not as though one user loading ~10 extra pages/min is a problem; it's the principle of the thing.

(Note: For clarity's sake, although I really hope I don't actually need to say this, I do not have any scripts to automate any review actions. That would be a remarkably stupid idea.)

(In case anyone on SO is wondering, yes, this is how I manage to cap Late Answers first each day. Gasp!)

_{*One of these days I'll try again to get the AJAX loading to work. It's oddly less trivial than I'd expect.}

I was looking at Am I allowed to use/create robots to track questions? just now and started wondering whether my current userscript to help with reviewing has quite the right internal rate limits. It reloads the page* every so often (30 seconds on SO, 5 minutes elsewhere) if there's no review ready to go, but since I have access to a number of queues, that loads things down a bit more.

On the other hand, because it makes no attempt to maintain the lock on any items, it's really limited as much by my manual review speed as anything else, except in times where there's nothing to review for a while in any queue. Max load at present would be about 13 per minute across three sites.

I'm not aware of any specific rate limits that would apply, so this is really more a matter of good manners, I suppose. It's not as though one user loading ~10 extra pages/min is a problem; it's the principle of the thing.

Is this script sanely self-limited? Or should I tweak the timing some more?

(Note: For clarity's sake, although I really hope I don't actually need to say this, I do not have any scripts to automate any review actions. That would be a remarkably stupid idea.)

(In case anyone on SO is wondering, yes, this is how I manage to cap Late Answers first each day. Gasp!)

_{*One of these days I'll try again to get the AJAX loading to work. It's oddly less trivial than I'd expect.}