Hello all, On 4/26/06, Essjay <essjaywiki(a)gmail.com> wrote:> Developer Rob Church has enabled the [[Special:Makebot]] feature for Now it seem to be activated on all projects. Perhaps some wikis may want to have their bot policies multiligualize. If you may want to ask a help for translation, consider to submit your request on [[Meta:Translation requests]]. There you find a section dedicated for "requests from local projects". Cymri (Welsh)Wikipedia has once used it for i18n of their welcoming messages and they seem to be happy with results of their requests. URLs are: Main Page: http://meta.wikimedia.org/wiki/Translation_requests Submittion: http://meta.wikimedia.org/wiki/Template:Translation_requests/fromlocalreqs Enjoy! -- Aphaea(a)*.wikipedia.org email: Aphaia @ gmail (dot) com

You can't make sysops bots with this feature... Though I don't know if it's possible to make a bot sysop.

Go ahead. I'll remove it if it works. =)

Jon Harald Søby wrote: Just tested on en.wiki; you can assign a sysop flag to an account that already has a bot flag, but you cannot assign a bot flag to an account with a sysop flag. The account in question (User:EssjayTest, my testing account) is now desysopped and deflagged. (Thanks Jon!) Essjay

Whether technically possible or not technically possible, Proxybot was both a sysop and a bot on the cs.wikipedia. His activity is to block ips : http://cs.wikipedia.org/w/index.php?title=Speciální%3ALog&type=block&am… Is that suitable that a bot also has a sysop status ?

On 4/28/06, Anthere <Anthere9(a)yahoo.com> wrote: Perhaps more pertinently, why does this bot need bot status? I don't believe being a bot hides your admin activites from the log or elsewhere.

From experience with ProxyBot

Indeed, I can't actually imagine any circumstance where a bot needs sysop privileges to *edit*, which is the only area that botship (?) actually affects.

On Fri, Apr 28, 2006 at 04:38:57PM +0200, Anthere wrote: ... I think several aspects should be separated -technical implementation & mediawiki issues (problems with cluttering of logs etc.) -questions od accuracy of open proxy detection, if such blocks can be automated -should open proxies be blocked just because beeing open proxies? I hope Egg (creator of Proxybot) will post something about the bot in wikitech-l, in Requests_for_permissions also another solution was proposed, to import the blacklist directly into db. I hope this will be discussed in wikitech-l What seems to me as relevant topic for Foundation-l are the policy questions 1. should open proxies be blocked? some possible answers a. yes b. only after they are source of vandalism c. no, they should be treated as normal ips d. it should be left to local communities of language versions / projects to decide As we have a "WikiProject on open proxies" http://meta.wikimedia.org/wiki/WM:OP and http://meta.wikimedia.org/wiki/WM:NOP no open proxies policy the answer seems to be "yes", but see complains at [[en:Wikipedia talk:No open proxies#Foundation Issue Violation]] 2. can such blocks be automated? a. yes b. yes, if the list was verified by hand by experienced users c. yes, if the list was verified by trusted script run by trusted user d. yes, if the list comes from reputable source (is meta: page a reputable source?) e. no, it should be checked by hand one by one f. no g. it should be left to local communities of language versions / projects to decide In my opinion trusted proxycheck script run by trusted user is resonable. Scripts tend to err on side of caution (if I play with nmap etc. I'm able to identify more proxies simple script is). My thought on the topic - if http://meta.wikimedia.org/wiki/WM:NOP is official Foundation policy, it would make sense to have Wikimedia-wide ip blacklist, blocking proxies. One-by-one blocks by hand by admins of individual projects are IMO waste of time. That isn't a problem on en: with its overwhelming manpower, but for smaller project dealing with open proxy abuse may be non-negligeable burden. One technically savvy vandal can occupy several checkusers and admins for indefinite time period: all he has to do is to download some public open proxy list, run his own scan, and as soon as one proxy is blocked, switch to another. If privacy policy is relatively strict and blocking policy relatively liberal (warn several times, block only after several repeated vandalisms, if vandalizing edits are mixed with good edits, talk more, use RfC etc.) time impact on wiki users vs. vandal plays in favour of vandal. Jan Kulveit - User:Wikimol