Change Details

It is common to use the same or similar set of values for the marker template of archivebot on a certain wiki. We could add an argument for the script to provide default values. Option 1: The new parameter (e.g. -defaults:filename.json) accepts a file path which points to a text file (maybe a JSON?) which gives pairs of parameter name and value like "minthreadsleft = 1". If a wiki community wants a new set of default values, they should ask the operator to update the file. Option 2: The new parameter (e.g. -defaults:MediaWiki:Archivebotconfig.json) accepts a wiki page title, not a local file on the server side. This is more flexible for the wiki community to update settings, and easier for the operator to live with. However, since there is a large potential for vandalism, we would want to put a restriction that only sysops can edit the page (e.g. limiting to the MediaWiki namespace). We would want to enforce hard upper/lower limits for certain values, since the default set might have quite large implications and there will be a larger chance for mistake by Option 1. Perhaps we can implement both and let the operator and community choose.

It is common to use the same or similar set of values for the marker template of archivebot on a certain wiki. We could add an argument for the script to provide default values. Option 1: The new parameter (e.g. -defaults:filename.json) accepts a file path which points to a text file (maybe a JSON?) which gives pairs of parameter name and value like "minthreadsleft = 1". If a wiki community wants a new set of default values, they should ask the operator to update the file. Option 2: The new parameter (e.g. -defaults:MediaWiki:Archivebotconfig.json) accepts a wiki page title, not a local file on the server side. This is more flexible for the wiki community to update settings, and easier for the operator to live with. However, since there is a large potential for vandalism, we would want to put a restriction that only sysops can edit the page (e.g. limiting to the MediaWiki namespace). For further safety we might want to enforce hard upper/lower limits for certain values. (The same could be said to Option 1, but Option 2 seems to be more vulnerable.) Perhaps we can implement both and let the operator and community choose. Exactly what kind of structure and semantics the config file should have is open to discussion.

It is common to use the same or similar set of values for the marker template of archivebot on a certain wiki. We could add an argument for the script to provide default values. Option 1: The new parameter (e.g. -defaults:filename.json) accepts a file path which points to a text file (maybe a JSON?) which gives pairs of parameter name and value like "minthreadsleft = 1". If a wiki community wants a new set of default values, they should ask the operator to update the file. Option 2: The new parameter (e.g. -defaults:MediaWiki:Archivebotconfig.json) accepts a wiki page title, not a local file on the server side. This is more flexible for the wiki community to update settings, and easier for the operator to live with. However, since there is a large potential for vandalism, we would want to put a restriction that only sysops can edit the page (e.g. limiting to the MediaWiki namespace). We wouldFor further safety we might want to enforce hard upper/lower limits for certain values. (The same could be said to Option 1, since the default set might have quite large implications and there will be a larger chance for mistake by Option 1.but Option 2 seems to be more vulnerable.) Perhaps we can implement both and let the operator and community choose. Exactly what kind of structure and semantics the config file should have is open to discussion.