Well, it would be nice if when someone blocked a bot account, it wouldn't automatically block everyone at that IP address (including the owner).
I don't particularly like the idea of requiring bots to check their own talk pages, at least not on every edit. I think that would waste server resources. It would also significantly raise the bar on bot-writing. If you ask me, we should be *encouraging* more people to write bots, not discouraging them with more red tape. I don't see very many instances of bots gone wild, and surely if it's an emergency, having an administrator block it is quite sufficient control. We can also always run an undo-bot on the account, if necessary to clean up.
I'm also a bit hesitant about allowing third parties to futz with live bots. If there's one bot operator, then there's one person who can be held accountable for all of the actions of the bot. If any of a number of people can come by and frob its code and run the bot, this clear accountability becomes fuzzy.
I'm sure it's useful to post source code for bots, but if a second person wants to use the same source as an existing, useful bot, they should copy it and get a separate account to edit under.
-B.
On 10/26/05, Christopher Beland beland@alum.mit.edu wrote:
Well, it would be nice if when someone blocked a bot account, it wouldn't automatically block everyone at that IP address (including the owner).
Well thats a whole nother ball of feature creep.. Lots of people would like to be able to select 1) if the block stops editing the underlying IP and others on it, 2) if the block blocks new account creation, 3) if a block on an IP blocks logged in users.... It would often be useful to inhibit new accounts, and block anons, but allow logged in users. Such flexibility would be generally desirable but I expect isn't at the top of anyone's wishlists.
I don't particularly like the idea of requiring bots to check their own talk pages, at least not on every edit. I think that would waste server resources. It would also significantly raise the bar on bot-writing. If you ask me, we should be *encouraging* more people to write bots, not discouraging them with more red tape. I don't see very many instances of bots gone wild, and surely if it's an emergency, having an administrator block it is quite sufficient control. We can also always run an undo-bot on the account, if necessary to clean up.
I'd hope that most people writing bot would use frameworks like pywikipedia which would automate such a task. In any case, if the message is left on the talk page the bot would get a notice message on its next page read. I haven't seen any interesting bots that operate completely blind, so it wouldn't add overhead if it only checked once it got the notice.
I'm also a bit hesitant about allowing third parties to futz with live bots. If there's one bot operator, then there's one person who can be held accountable for all of the actions of the bot. If any of a number of people can come by and frob its code and run the bot, this clear accountability becomes fuzzy.
Fairly reasonable idea that edits should be accountable to a single person.
I'm sure it's useful to post source code for bots, but if a second person wants to use the same source as an existing, useful bot, they should copy it and get a separate account to edit under.
I'm also a bit hesitant about allowing third parties to futz with live bots. If there's one bot operator, then there's one person who can be held accountable for all of the actions of the bot. If any of a number of people can come by and frob its code and run the bot, this clear accountability becomes fuzzy.
Fairly reasonable idea that edits should be accountable to a single person.
I'm sure it's useful to post source code for bots, but if a second person wants to use the same source as an existing, useful bot, they should copy it and get a separate account to edit under.
Toolserver-l mailing list Toolserver-l@Wikipedia.org http://mail.wikipedia.org/mailman/listinfo/toolserver-l
What I primarily question what happens or what you do for someone who is still running a bot, but no longer part takes in the Wikipedia? Pass the account? Shutdown the bot, wait for someone to reinvent their wheel?
On 10/26/05, Jason Y. Lee jylee@cs.ucr.edu wrote:
What I primarily question what happens or what you do for someone who is still running a bot, but no longer part takes in the Wikipedia? Pass the account? Shutdown the bot, wait for someone to reinvent their wheel?
Ask them for a copy of the bot, run it under a different account. Every bot needs to have someone who can modify it and be accountable for its actions.
toolserver-l@lists.wikimedia.org