Template talk:Repeat vandal
From Wikipedia, the free encyclopedia
Contents |
[edit] Purpose
Used to mark pages of anonymous editors who have been repeatedly blocked for vandalism.
[edit] Changes
[edit] Color
Personally, I preferred the yellow, stood out more. My eyes are in their mid-30's and didn't mind. I dont' really care about the vandal's eyes. :) Wikibofh(talk) 17:22, 14 December 2005 (UTC)
- Yeah, me too -- and my eyes are in their 50s. It's supposed to be uggily. --jpgordon∇∆∇∆ 22:49, 18 December 2005 (UTC)
-
- No, it's not supposed to be obnoxious. We got some template guidelines for talkpages which we should stick to.SoothingR 23:32, 1 January 2006 (UTC)
[edit] Collateral damage warning
-
-
- I prefer the the yellow - it carries more content, shall we say. But what I came here for was to suggest adding something the following
- Note: This a shared IP Address. <strong>Please use only short blocks</strong> to limit collateral damage.<br>
- An example may be seen at [1]. Regards, Ben Aveling 11:17, 3 March 2006 (UTC)
- I prefer the the yellow - it carries more content, shall we say. But what I came here for was to suggest adding something the following
-
-
-
-
- Not all repeat vandals are shared-IP's, by any means. And of those that are, not infrequently the entire list of "contributions" is vandalism, whether it's just a single user at that shared address (the others not caring to do Wikipedia), or whether, as in the case of a number of schools, it's all a pile of young children each doing their own vandalism. Bill 13:32, 3 March 2006 (UTC)
-
-
I would also oppose the automatic inclusion of the shared IP comment. Some vandal accounts are shared, some are not. Shared IPs should be noted separately using the {{sharedIP}} template. Rossami (talk) 14:28, 3 March 2006 (UTC)
- I agree that sharedIP ought to be enough to warn admins off from applying long blocks, but at leasts in the case of 202.6.138.33, it isn't. Otherwise, point taken. What about "If this IP Address is shared, ..." Regards, Ben Aveling 15:17, 3 March 2006 (UTC)
- So what if the IP is shared? Nothing prevents an individual user, though using the computer at some school, from registering. Serious users already very much tend to register: ignoring the shared-IP and blocking a whole school for a month, or even AOL, would be a powerful inducement for serious editors to register: what harm is there in that? (As for whether admins pay attention to things, by and large they don't; the whole question of vandalism has got so out of hand that in the case at least of the 210 articles I follow, the great majority of edits are vandalism and reverts. The solution is to require registration with traceable e‑mail. Anyone who thinks this would kill Wikipedia may note that registration has been required now for several months for the writing of new articles, and it hasn't done the least damage to anything.)Bill 16:29, 3 March 2006 (UTC)
- Registration alone does not solve all evils. Remember that an IP block also blocks all signed-in users who are connecting from that IP address. Ben is correct that long blocks should be used very sparingly against IPs. Rossami (talk) 16:35, 3 March 2006 (UTC)
-
- Uh, did you read what I wrote? Why would I have written it if I didn't know that blocking the IP blocks everybody? The question really is not about the wording of a template that the overwhelming majority of people won't read, but about preventing vandalism. In my view, precisely, it is not correct that "long blocks should be used sparingly": since so far there has been no solution to the vandalism problem, to get to one, we need to start thinking outside the mindless box that has been created for us. Bill 16:56, 3 March 2006 (UTC)
-
- Registration alone does not solve all evils. Remember that an IP block also blocks all signed-in users who are connecting from that IP address. Ben is correct that long blocks should be used very sparingly against IPs. Rossami (talk) 16:35, 3 March 2006 (UTC)
- So what if the IP is shared? Nothing prevents an individual user, though using the computer at some school, from registering. Serious users already very much tend to register: ignoring the shared-IP and blocking a whole school for a month, or even AOL, would be a powerful inducement for serious editors to register: what harm is there in that? (As for whether admins pay attention to things, by and large they don't; the whole question of vandalism has got so out of hand that in the case at least of the 210 articles I follow, the great majority of edits are vandalism and reverts. The solution is to require registration with traceable e‑mail. Anyone who thinks this would kill Wikipedia may note that registration has been required now for several months for the writing of new articles, and it hasn't done the least damage to anything.)Bill 16:29, 3 March 2006 (UTC)
-
-
-
- There is a push for a form of blocking that locks out anons and new user registration while still allowing registered users to edit which might one day help solve this problem. See http://bugzilla.wikimedia.org/show_bug.cgi?id=3706 and http://bugzilla.wikimedia.org/show_bug.cgi?id=550
- 550 proposes a flag on IP blocks to say if they block everything, block anon editing, or block anon editing and account creation. 3706 is different, but not all that different. It proposes a flag on accounts to allow them to edit through IP blocks. More discussion may be found at Wikipedia:Blocking policy proposal.
- If either bug is ever implemented, it will help. But for the moment, shared IPs are a problem we have to live with. Regards, Ben Aveling 16:53, 3 March 2006 (UTC)
- Hi Bill, I'm sure that you would never put a long block on a shared IP. But the fact is, people do it. If we do not give them a gentle reminder in this template, what do you suggest we do? Or are you in favour of long blocks on shared IPs? Regards, Ben Aveling 16:28, 7 March 2006 (UTC) PS. You make a good point that {{SharedIP}} should also carry a similar warning. I'll follow up on it, but I don't think that's sufficient, both because that template won't always be present, and because it is this template that is actively encouraging and authorising the use of blocks.
- Ben, actually, I would — as above. Not to worry, I'm not an admin, and despite flattering queries, am not running for admin, either. Absolutely nothing prevents the serious editor from registering, and thus detaching themselves from AOL as it were. Yes, I'd block all of AOL if the vandalism got bad enough. In fact, of course, with these rotating IP's, that's not what would happen: one of the rotating IP's would be blocked, and the same proportion of vandals would get thru on the others, with afew people occasionally being mystified that they couldn't edit.... Short of requiring traceable registration for editing (just as on the overwhelming majority of bulletin boards) there is no solution to the vandalism. I would encourage serious editors to join me in refusing by and large to revert vandalism — to go on strike — If enough of us did that, the articles would quickly liquefy, and the people who really run this show (i.e., Jimbo) would change the rules. Bill 17:45, 7 March 2006 (UTC)
-
- What do you mean by 'detaching themselves from AOL'? Do you mean changing ISPs? Regards, Ben Aveling 16:53, 9 March 2006 (UTC)
- Not the clearest writer, am I? I merely mean that, by registering, although whatever IP they're assigned to each time is still one of these AOL numbers, the Wiki software no longer lumps them in with AOL or its IP's. If I were on AOL, for example, and found myself blocked because of some idiot, well — I'd register. Therefore blocking even all of AOL doesn't do the slightest harm to anyone: we've just got to think outside the box. Bill 17:31, 9 March 2006 (UTC)
- Um, if you are a registered user on a blocked IP, you're still blocked. Regards, Ben
- Not the clearest writer, am I? I merely mean that, by registering, although whatever IP they're assigned to each time is still one of these AOL numbers, the Wiki software no longer lumps them in with AOL or its IP's. If I were on AOL, for example, and found myself blocked because of some idiot, well — I'd register. Therefore blocking even all of AOL doesn't do the slightest harm to anyone: we've just got to think outside the box. Bill 17:31, 9 March 2006 (UTC)
- What do you mean by 'detaching themselves from AOL'? Do you mean changing ISPs? Regards, Ben Aveling 16:53, 9 March 2006 (UTC)
- I just wish they made users sign up before editing. 90% of anonymous edits has to be vandalism. It's not so muc that it'll stop vandalism, it's just another hoop to jump through. And you need to insert a strong, highlighted message referring to collateral damage. I've been hit around five times by it thanks to vandals and it's no help. michael talk 23:31, 7 March 2006 (UTC)
-
- Ben, actually, I would — as above. Not to worry, I'm not an admin, and despite flattering queries, am not running for admin, either. Absolutely nothing prevents the serious editor from registering, and thus detaching themselves from AOL as it were. Yes, I'd block all of AOL if the vandalism got bad enough. In fact, of course, with these rotating IP's, that's not what would happen: one of the rotating IP's would be blocked, and the same proportion of vandals would get thru on the others, with afew people occasionally being mystified that they couldn't edit.... Short of requiring traceable registration for editing (just as on the overwhelming majority of bulletin boards) there is no solution to the vandalism. I would encourage serious editors to join me in refusing by and large to revert vandalism — to go on strike — If enough of us did that, the articles would quickly liquefy, and the people who really run this show (i.e., Jimbo) would change the rules. Bill 17:45, 7 March 2006 (UTC)
- Hi Bill, I'm sure that you would never put a long block on a shared IP. But the fact is, people do it. If we do not give them a gentle reminder in this template, what do you suggest we do? Or are you in favour of long blocks on shared IPs? Regards, Ben Aveling 16:28, 7 March 2006 (UTC) PS. You make a good point that {{SharedIP}} should also carry a similar warning. I'll follow up on it, but I don't think that's sufficient, both because that template won't always be present, and because it is this template that is actively encouraging and authorising the use of blocks.
-
-
[edit] Width=100%
Why is the width 100% and not 80%? Off! 02:49, 5 April 2006 (UTC)
- Why would you want it to be 80%? 100% would seem to be the most efficient use of the space on the screen. Rossami (talk) 04:43, 5 April 2006 (UTC)
- It can be more discreet, and more readable and ethical with all text in a central area. --Off! 04:55, 5 April 2006 (UTC)
- Ummm... you lost me there. When I switch it to 80% and preview it, the template changes from 2 lines deep to 3 lines deep on my screen. Since it's a colored template, that appears to make it less discrete. The word-wrap does nothing that I can see to impact readability one way or the other. And I really don't know what you mean by "ethical". Please explain? Rossami (talk) 05:03, 5 April 2006 (UTC)
- It can be more discreet, and more readable and ethical with all text in a central area. --Off! 04:55, 5 April 2006 (UTC)
This template is often used in conjunction with other user talk header templates such as {{SharedIP}}, {{SharedIPEDU}}, {{ISP}}, {{AOL}}, etc., all of which use the standard CSS classes and therefore are 80% wide. With only this template at 100%, the combination looks really awful. I think the width should be kept consistent; if you want it to be consistently 100%, feel free to propose the change at MediaWiki talk:Common.css, but for now the standard width in 80%. —Ilmari Karonen (talk) 11:49, 24 June 2006 (UTC)
Also, basing layout decisions on how a given line wraps on your screen is rather pointless. For example, on my screen the current 100% layout has almost all of the text on one line, except for "further warning." which wraps to the next. For me, the text would look more balanced at 80% or even 60%. Of course, for anyone else it'll look different again. In general, for any given width there will be someone on whose screen the text will fit on n lines save for one word on the n+1th. —Ilmari Karonen (talk) 11:58, 24 June 2006 (UTC)
- Clarification: I agree that different widths can look more balanced. I was responding to Off!'s comment that the 80% width made it more "discrete" which I interpreted as "takes fewer lines on the page" - an assertion which I do not believe can be true. Going to a narrower screen width could be the same number of lines or more lines but cannot take less lines unless you simultaneously changes something else like font size. I will take your suggestion to propose a change to the standard at MediaWiki talk:Common.css. Thanks for pointing it out. Rossami (talk) 13:21, 24 June 2006 (UTC)
- Well, for me, making the width 80% would make the box narrower without making it any taller. So yes, for me the 80% version would indeed clearly be more discreet. —Ilmari Karonen (talk) 14:47, 24 June 2006 (UTC)
[edit] Usage
Is this a template that should only be put on by admins or if anyone comes across an ip that seems to be getting blocked a lot can they put it on?--Crossmr 18:42, 14 July 2006 (UTC)
- It probably shouldn't be used by an anon or very new user but anyone actively working on one of the Vandalism Patrols should be able to apply the template. Just be sure to check the block log carefully and be sure of your facts before applying it. Remember that sometimes a long list is the result of multiple admins blocking in rapid succession for a single event or that the list can be inflated if someone has to reset the block to a shorter time in order to fix a problem of collateral damage. Rossami (talk) 02:09, 15 July 2006 (UTC)
[edit] Substitution
Is it really necessary to substitute this template? It only has 444 uses and some of them can be removed, as they are in inappropriate places. I hate unnecessary substitution because the wording of the message cannot be modified on the templates already placed, and the template code can really clutter up a page, especially when more than one template has been substituted. Sometimes I cannot tell where one template ends and the other begins. -- Kjkolb 09:12, 12 May 2007 (UTC)
- I agree with not substituting this template. Could you give a few different examples where they are in inappropriate places? --Geniac 14:28, 14 May 2007 (UTC)
- I noticed this template among the list of templates that should NOT be substituted, but the decription used recommends substituting. I trust someone will decide and fix it. -- Belegûr 16:35, 8 August 2007 (UTC)
[edit] How many blocks qualify?
What qualifies as 'repeatedly blocked'? Twice? SaltyBoatr (talk) 16:50, 18 December 2007 (UTC)