Page MenuHomePhabricator

RFC: update or remove throttle section in [[m:Bot policy]]
Closed, InvalidPublic

Description

The 5 edits/minute limit was established in 2007. Now we have the cool maxlag default set to 5 seconds plus a way faster infrastructure.

Event Timeline

Vituzzu created this task.Sep 21 2016, 10:04 AM
Restricted Application added subscribers: pywikibot-bugs-list, Aklapper. · View Herald TranscriptSep 21 2016, 10:04 AM
Vituzzu triaged this task as Low priority.Sep 21 2016, 10:05 AM
Vituzzu added a subscriber: Horcrux92.
Vituzzu added a subscriber: Pracchia-78.
Xqt added a subscriber: Xqt.EditedSep 21 2016, 11:35 AM

It is not only part of the infrastructure that bots have to have a write delay. It's also to have any change against disastrous bot malfunctions by reviewing their edits. Most local community have their own policy for maximum edit intervals.

Anyway this RFC is not part of the pywikibot projects and you are always able to owerride the default settings if you have good reasons to do it.

The discussion regarding this request is at
https://meta.wikimedia.org/wiki/Talk:Bot_policy

Xqt closed this task as Invalid.Sep 21 2016, 11:38 AM

Ok, so what's the place to have a technical feedback about this particular global policy which should affect *any* wiki?

Xqt added a comment.Sep 21 2016, 11:57 AM

Don't think we have a technical problem to solve. The throttle time is a setting variable in the config2?.py and may be overridden via user-config.py or through command line options.

Maybe I wasn't able to explain myself. Current global policy sets a limit for technical reasons. I think this technical background is no longer valid then my RFC here. Is there a technical limit upper limit to edit rate? Is maxlag default value enough to prevent techinical issues?

Xqt added a comment.Sep 21 2016, 12:46 PM

maxlag is not the only value. We also have a 'retry_after' value from api
see https://gerrit.wikimedia.org/r/#/c/307127/

From technical side this would be enough. The read delay is already deactivated in core as default. The put throttleling supports the local and global bot policies.