Wikidata:Requests for permissions/Administrator/HaroldBot
From Wikidata
Jump to navigation
Jump to search
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- No consensus for promotion to admin bot status at this time.--Jasper Deng (talk) 03:14, 6 April 2013 (UTC)[reply]
- HaroldBot (talk • contribs • new items • new lexemes • SUL • Block log • User rights log • User rights • xtools)
It simply takes en:User:ProcseeBot's blocklist, and re-blocks those IPs on Wikidata. See Wikidata:Requests for permissions/Bot/HaroldBot for a bit longer rationale. --Legoktm (talk) 07:25, 29 March 2013 (UTC)[reply]
Votes
[edit]- Support --Rschen7754 07:33, 29 March 2013 (UTC)[reply]
- Yes, but please do some "test blocks" --Ricordisamoa 07:59, 29 March 2013 (UTC)[reply]
- Take a look at Special:Log/block/Legoktm, and the ones that say <!-- port #### --> are from the "bot". Legoktm (talk) 22:40, 29 March 2013 (UTC)[reply]
- Support --Stryn (talk) 08:34, 29 March 2013 (UTC)[reply]
- Support Wow, it has my name, lol. — ΛΧΣ21 17:44, 29 March 2013 (UTC)[reply]
- Support Rzuwig► 20:16, 29 March 2013 (UTC)[reply]
- Weak oppose per my comment below; task seems a bit unnecessary and non-productive (as a gblock would do this for all wikis) to me. Kind regards, Vogone talk 21:13, 29 March 2013 (UTC)[reply]
- Support In my opinion the global policy against proxies is no reason not to perform automatic proxy blocks on Wikidata. Regards --Iste (D) 22:27, 29 March 2013 (UTC)[reply]
- Support And assuming everything goes well, maybe in a few months you should take it to Meta and request some sort of "global blocker" right for it, as was suggest in ProcseeBot's BRFA? — PinkAmpers&(Je vous invite à me parler) 03:13, 31 March 2013 (UTC)[reply]
- Oppose from personal experience with ProcseeBot. Aurora (talk) 15:54, 31 March 2013 (UTC)[reply]
- Sorry, do you mind expanding on that? I'm not aware of what your personal experience was... Legoktm (talk) 16:47, 31 March 2013 (UTC)[reply]
- Obviously the experience of being on the receiving end of ProcseeBot's actions. Aurora (talk) 08:18, 1 April 2013 (UTC)[reply]
- Sorry, do you mind expanding on that? I'm not aware of what your personal experience was... Legoktm (talk) 16:47, 31 March 2013 (UTC)[reply]
- Oppose as above. IW (wikidata addict) 16:06, 31 March 2013 (UTC)[reply]
- Oppose per above. Lukas²³ talk in German Contribs 21:26, 31 March 2013 (UTC)[reply]
- Weak oppose per above--DangSunM (talk) 02:44, 1 April 2013 (UTC)[reply]
- Support I believe that the work Hazardbot can do will have many more positives for the project than negatives. Del♉sion23 (talk) 22:06, 2 April 2013 (UTC)[reply]
- This is HaroldBot, not Hazard-Bot, by the way.
;-)
Regards, Vogone talk 01:05, 3 April 2013 (UTC)[reply]
- This is HaroldBot, not Hazard-Bot, by the way.
Comments
[edit]- In my opinion, reporting unblocked open proxies to stewards + gblock would be more effective as a global anti proxy policy already exists. Regards, Vogone talk 11:41, 29 March 2013 (UTC)[reply]
- Sure but I don't see why that's a reason to not block them locally. If a steward wants to start blocking them globally, that's great, but until then a local solution is needed. Legoktm (talk) 22:39, 29 March 2013 (UTC)[reply]
- Again, why? Wouldn't it be better to report the OPs directly to the stewards instead of blocking locally and do nothing more? If every project should do that at its own one wouldn't need gblocks … Regards, Vogone talk 23:03, 29 March 2013 (UTC)[reply]
- The point is that it currently doesn't happen. If a few stewards step and start g-blocking enmasse, great! The bot will have nothing to do then. But ProcseeBot has been running for 2? years now and that hasn't happened yet. Legoktm (talk) 13:53, 30 March 2013 (UTC)[reply]
- I just left a note at m:Stewards' noticeboard#Global blocking of open proxies. Feel free to join in on that discussion. — Hazard-SJ ✈ 04:28, 1 April 2013 (UTC)[reply]
- The point is that it currently doesn't happen. If a few stewards step and start g-blocking enmasse, great! The bot will have nothing to do then. But ProcseeBot has been running for 2? years now and that hasn't happened yet. Legoktm (talk) 13:53, 30 March 2013 (UTC)[reply]
- Again, why? Wouldn't it be better to report the OPs directly to the stewards instead of blocking locally and do nothing more? If every project should do that at its own one wouldn't need gblocks … Regards, Vogone talk 23:03, 29 March 2013 (UTC)[reply]
- Sure but I don't see why that's a reason to not block them locally. If a steward wants to start blocking them globally, that's great, but until then a local solution is needed. Legoktm (talk) 22:39, 29 March 2013 (UTC)[reply]
- IIRC, Slakr has never made the source code to ProcseeBot public. While that's never been an issue, I'm slightly concerned about the idea of running a bot off of another, mostly inactive user's private source code. Do you think there's any way you could track Slakr down (I have no clue if he still frequents tech-y channels... I just make note of en:Special:Contributions/Slakr) and convince him to give you the code? — PinkAmpers&(Je vous invite à me parler) 18:13, 29 March 2013 (UTC)[reply]
- Right. I don't think he will given his rationale given here. Normally I wouldn't want to run a bot based on another bot, but I think slakr/ProcseeBot's track record speaks for itself (over 600k blocks). Legoktm (talk) 22:39, 29 March 2013 (UTC)[reply]
- Fair enough. Mind throwing in something to disable all tasks (or self-block, I suppose) in the unlikely event that ProcseeBot is blocked on En? — PinkAmpers&(Je vous invite à me parler) 23:55, 29 March 2013 (UTC)[reply]
- If ProcseeBot is disabled on enwiki, that means it stops blocking proxies, which means when my bot goes to fetch new blocks...it won't find anything. Legoktm (talk) 13:53, 30 March 2013 (UTC)[reply]
- Oh. Right. Cool. :/ — PinkAmpers&(Je vous invite à me parler) 03:12, 31 March 2013 (UTC)[reply]