User talk:Andy Dingley

Archives

/2007 •

/2008 1 - 3

/Archive 4

/Archive 2009 January

/Archive 2009 February

/Archive 2009 March

/Archive 2009 April

/Archive 2009 May

/Archive 2009 June

/Archive 2009 July

/Archive 2009 September

/Archive 2009 October

/Archive 2009 November

/Archive 2009 December

/Archive 2010 January

/Archive 2010 February

/Archive 2010 March

/Archive 2010 April

/Archive 2010 May

/Archive 2010 June

/Archive 2010 July

/Archive 2010 August

/Archive 2010 September

/Archive 2010 October

/Archive 2010 November

/Archive 2010 December

/Archive 2011 January

/Archive 2011 February

/Archive 2011 March

/Archive 2011 April

/Archive 2011 May

/Archive 2011 June

/Archive 2011

/Archive 2012

/Archive 2013

Superheater

Hi Andy, Please stop undoing the edits on Superheater and take the time to read the text. Unsaturated steam and wet steam are the same thing. When I first read the article, it was confusing, which is why I took the time to edit it. The revised text should be clearer to everyone. Jonathan 123987 talk 00:34, 26 January 2014

FYI

Hi Andy. If you're not happy with the way user Wereith totally screwed you over recently over that non-free rendering of an engine, perhaps you could get your own back by exposing what many Wikipedia admins seem to be completely unwilling to even acknowledge (and which some others, like BlackKite, seem to be actively assisting in covering up) - Wereith is none other than the banned user Betacommand. He has all the same behavioural flaws, the same binary perception of policy, all the same interests, he even has the same retarded grasp of English (where instead of were for example). What he did to you is exactly what Betacommand used to do - whenever he is caught in a lie he simply ignores it and changes tack to another argument. The others in the debate didn't question it because they all already know, or at least suspect, that this is Beta returned, and so pulling Wereith up on such things would be as much of a waste of time now as it was with Beta. While he is undoubtedly right in many cases, even in spite of that, his entire approach is extremely damaging to Wikipedia. The number of users who end up completely disillusioned with the project or come away with the completely wrong idea about what policy on non-free imagery says, due to this arrogant, confrontational and frankly clueless wannabe robot approach, is huge. The community (and multiple arbcoms) has already expended a massive amount of time getting to that conclusion once in order to finally ban him, it really shouldn't have to repeat the same process again on the obviously flawed assumption that Wereith is a brand new user (and even if people doubt he is Wereith, they cannot ignore the obvious, that he is definitely not a brand new user). I've tried to raise this issue before in various ways, but as I'm sure you know - on Wikipedia the policy that matters above all others is WP:SOCK - anyone like me who makes a complaint without any identifiable history behind them, is automatically ignored, no matter how serious or damaging it would be if their allegations turned out to be correct (granted, this isn't Watergate, but as far as time-sink disruptive users go, Betacommand was top of the tree). As such, don't be too surprised if this is the only communication I am able to send on this account. The only way that Beta is going to be stopped is if an established user like your good self files an SPI on Wereith. It won't find any technical evidence I'm sure, as Beta knew all about how CU works, but as long as you make it a good one and fill it with plenty of diffs covering all the similarities - general behaviour, approach to dispute resolution (edit warring, battling), policy knowledge (or lack of), areas of interest (and the complete lack of interest in writing at all), the writing style - I'm sure a block would be forthcoming based on the deafening sound of quacking that it would expose. He might claim that the fact Wereith uploads non-free media (book covers, one of the tiny class of non-free media that is de facto acceptable) shows he is not Beta - but that activity stopped abruptly a while back - so it was clearly just a cover story, if you'll excuse the pun. His increased levels of arrogance and sarcasm to others (such as yourself in that NFCR), show that he clearly thinks he has gotten away with it, and is now not even really trying to suppress his true identity, so this is more than overdue. Arnhem 96 (talk) 21:50, 28 November 2013 (UTC)

Actually, could the reason he was exceptionally rude to you in the NFCR be that he maybe remembers you as a previous critic? Had you ever supported one of the countless block/ban proposals of Beta? Or had similar non-free image disputes with him? (I'd check for myself, but the archive search facility isn't much help in trying to verify that easily). Arnhem 96 (talk) 22:09, 28 November 2013 (UTC)

Thanks for the heads up. I question though whether this really changes the position much.

The problem is not who such an editor is, but rather what they're doing. WP culture prioritises the slavish observance of rules over the value that such actions generate. There doesn't seem to be any reluctance at NFCR to join in with such behaviour. Andy Dingley (talk) 01:04, 29 November 2013 (UTC)

Unbelievably I'm not blocked yet, so I'll respond. NFCC enforcement on Wikipedia has its problems, yes, but what you need to realise is that, due to his OCD level of interest in the activity and the many and varied behavioural problems that are unique to him, Beta will always have a massively disproportionate affect on Wikipedia as regards the perception, and indeed practice, of NFCC enforcement. While others will follow his lead while he is here, if he is not, then except perhaps Black Kite and Hammersoft (who is no longer an issue as he has decided to 'retire' from the activity out of frustration at not getting his way often enough, something he reminds everyone of at any opportunity), believe it or not, most of the other people who frequent venues like NFCR really wouldn't dare to treat you like an asshole just because you have a different view. And they certainly wouldn't dare to edit war against you or otherwise ignore you if there were other editors involved and shared your view (obviously, like all areas of Wikipedia, even in ideal conditions, interpreting NFCC is at heart always going to be a numbers game). The problem with Beta is, the existence of other editors never makes any difference. If he thinks an image fails NFCC, he will never ever change that view, no matter what. The fact he simply ignored you when you pointed out it was not an actual picture of an engine was no accident. The same tactic plays out day after day with Beta. Much like a robot, the tactics he uses against the people who challenge his view are all very predictable, and all entirely unaffected by what anyone else says. His behaviour is, at its core, the very antithesis of what collaborative editing is supposed to be all about. Imagine the effect that has on Wikipedia when the same thing happens to editors who are simply trying to improve Wikipedia with non-free imagery, day after day, sometimes multiple times a day, due to the script assisted industrial scale of his activities. It doesn't matter how many people disagree with him, it doesn't matter how many warnings he receives, it doesn't matter how many people tell him his approach is totally counter productive, in any situation like that he will still believe he is in the right, and everyone else is wrong. That is why you really need to expose the fact that, in defiance of an arbcom ban, he has just returned to Wikipedia and picked up where he left off. Because just like Beta, he is apparently not going to stop until every single instance of the use of a non-free image on Wikipedia adheres to his personal interpretation of 'policy' (and as far as Beta goes, policy is what you call any policy, guideline, essay or years old discussion between two people that supports his view). Other people can be reasoned with, or will at least respect consensus. Beta cannot. He must be exposed and therefore returned to his well-deserved and more than earned state of persona non-grata, for the sake of Wikipedia. Arnhem 96 (talk) 18:14, 29 November 2013 (UTC)

Andy, I'm disappointed to see you still wasting time trying to deal with Wereith as if he is just another user. I cannot stress to you enough just how futile that will be for you - you only need to look at how many times Betacommand brushed off warnings/blocks and even a couple of arbitration cases, how many different users tried and failed to get through to him or get admins to force him to comply with the basic norms of discussion and consensus. It went on for years before he was finally banned, and even then it involved numerous trips to ANI with countless episodes of wiki-lawyering as he bent and stretched his well earned restrictions. You only have two choices here if you're interested in your own sanity - either file an SPI, or completely ignore him. Trust me when I say that if he thinks you are wrong, even when (and especially when) you're right, nothing else matters. Nothing. Even in the unlikely event you prevail in any particular dispute, he will never ever admit he was wrong. And he will simply wait a few months and try the same edit again, hoping nobody notices. You will only save yourself and Wikipedia from repeating this entire years long farce again by exposing the fact he is a ban evading sock. I notice you think you don't have any hard evidence - you have to realise that you do - the sheer amount of similarities between the two users is effectively hard evidence as far as SPI goes. I've seen people banned as WP:DUCKs on much weaker cases than this, I really have. At the very least, the very least, he needs to be confronted with the fact that he is very clearly not a brand new user, so if he is not Beta, what is his explanation for that (per WP:SOCK, he is expected to have an actual answer for that, even if it is given to arbcom in secret). If I can't convince you, I'm also informing SlimVirgin (talk · contribs), who he is also having issues with, maybe you can collaborate if you're not willing to file an SPI on your own? I am still amazed I am still not blocked, but as I become more visible, it's only a matter of time - then it will be down to you. Arnhem 96 (talk) 20:07, 8 December 2013 (UTC)

And just to re-iterate - right now, the guy is calling you, an editor who registered in 2007, an incompetent dick. That's pretty strong words from a guy who registered in 2012, and only started editing in any great volume this time last year. Yet he claims to "know complexity of NFCC far far more than you do." I wonder how. I wonder how a guy ends up knowing all about NFCC in just under a year, yet has not grasped the inevitable consequences of calling an editor of your experience and service, an incompetent dick (and obviously I'm not talking about NPA, but the intended meaning if someone was properly invoking those two links). I'll tell you how - this behaviour is the result of the exact same mental illness or developmental issue that used to cause Betacommand to do the exact same thing. The guy is making an absolute mug out of you with this crap. And if you indulge him in it by simply exchanging 3RR templates and nasty words, I have to say, you are being a bit of a mug. If he is no longer interested in merely trying to pretend to be a brand new user, if as it seem he now wants to actively take the piss out of you on the basis you both know he is Beta returned, you need to hit him where it hurts - I have no doubt he was devastated when he finally got banned, because he is simply addicted to Wikipedia. Unfortunately for him, a lot of people spent an awful lot of time coming to the conclusion that, in his case, Wikipedia is not therapy, and his continued presence was not required for at least a year. (I cannot believe I also forgot to mention Betacommand has form for socking around blocks - see User:Quercus basaseachicensis). Arnhem 96 (talk) 20:49, 8 December 2013 (UTC)

Hello Andy. Once again I have to stress to you to not even try to interact with Werieth on the assumption he is a normal editor - you are seriously just wasting your time. I note the filing of SPI, and beefing this up with diffs really is the only way you will ever get rid of this guy for good. I can provide you with some, but you can see form the attitude of some admins that they are not going to let me stick around to do a proper job. Here's some to be getting on with. You should remember, Beta used the main identities Betacommand and later "Δ" (Delta). He also had various socks (see Category:Wikipedia sockpuppets of Betacommand), the investigations of which might yield further diffs.

Regarding the obsession with NFCC enforcement, it should be sufficient to just link to a few 500 page views of random months for each account, but here's Werieth confirming it his own words in a brilliant way as well (in the context of how relatively new that account is): "I have done thousands of non-free image enforcement edits"

• Side interests in technical areas, and gnoming & script editing:

Werieth [1] [2] (huge run of expand book citation edits) [3] (a perfect example - in 500 edits, as well as mass NFC enforcement, we also see contributions to village pump (tech)/bot request/spam blacklist project pages, as well as mass AWB edits, mass reference/external link edits (obviously script assisted editing). It shouldn't really be necessary to convince anyone that Beta was totally obsessed with technical matters and script/bot editing, but if anyone asks, you'll be able to find similar examples in their contribs quite easily

• affection for casting opposition as harassment

Werieth [4] [5] Betacommand [6] [7] [8] Δ [9]

• affection for casting opposition as people who merely hate NFCC 'shooting the messenger'

Werieth [10] Δ [11] [12] Betacommand [13]

• Habit of directing people to the 'third door on the left" when seeking to avoid discussing an NFC issue any further with an opponent

Werieth [14] Δ [15]

• Using where instead of were:

Werieth [16] Δ [17] Betacommand https://en.wikipedia.org/wiki/User_talk:Betacommand/20090701#July_2009

By way of showing that their response to short term blocks - completely ignore, don't complain/appeal or even acknowledge, just wait it out, then resume the bad behaviour where they left off, is the same, then you can refer to these two as examples:

• Betacommand

blocked for 24 hours for 3RR on 06:42, 3 June 2008 (blocked indef 2 days later, for edit warring)

• Werieth

blocked for 48 hours for 3RR on 17:38, 3 December 2013 (resumed edit warring soon aftwerwards)

One thing I also noticed today - notice the way Wereith deceptively changed the header you used on his talk page into something that belittles/attacks the original poster [18] - I'm sure Betacommand has done that before, but I'm finding it hard to track down an example. Although I might be thinking of Beta's long time admirer/defender Hammersoft - he absolutely loved doing that as far as I can remember. He used to love altering headers to things like 'Trolling by ...'.

It's great news that someone has noticed the timings of the account creations - it's all damning when considered alongside everything else - especially as Wereith's defence is still just the lame point about how he uploads book covers (one of the few classes of non-free imagery that are accepted, no questions, so are not likely to be the target of someone like Beta) - you should point out in the SPI that, as I predicted, he only resumed those uploads recently after a long recess, coincidentally at the same time as he was yet again being likened to Betacommand.

Here's another interesting thing - Betacommand was obviously fully conversant with SPI procedures (in his later years he even ran a bot for the clerks). So, it's interesting that after just a few months editing, Werieth was at ease with filing SPI reports himself [19][20]investigations/Expatkiwi/Archive . The first one is from Jan 2013, just a few months into his Wikipedia career.

Here's another interesting thing too - years ago Betacommand used to run a bot which did various NFCC enforcement tasks, but it was so crap, and he was such a retard when it comes to dealing with other people (i.e. complaints), that it was eventually shut down. Unsurprisingly, he was of the opinion that the bot was superb, not least as it did nothing but enforce policy, and he basically blamed everyone else for the grief and hassle it generated. With that in mind, and given the relative youth of the Wereith account, isn't it strange that he would have formed views like this: [21]. Can Wereith explain at all how/where/when he would form that opinion about bot assisted NFCC editting, given that as far as I know, Betacommand was the last person to have first hand experience of it.

I'm sure if you just peruse the talk page archives you will find plenty of links to give that will support the broader similarities in how they deal with opponents, such as the habit of casting anything on any NFC page as black and white policy, or claiming that every opponent is simply someone who wants to ignore NFC altogether (try and pick examples where that is manifestly not the case). There's not much point me looking for those, as it's almost as much work to explain them to you, as it would be for you to find them and be able to explain them yourself. But I hope I've been clear enough in these posts and elsewhere for you to know what to look for, but the best way will be for you to observe what Wereith does now and look for similarities in Beta's past behaviour - the only thing that's changed is that he is less sweary or a total twat, but the basic approaches to policy/opponents are the same. A few starters could be these - the way Wereith hates it when admins don't help him [22] - and the way Wereith sees edit warring as a necessity, so that people "get the point" [23]. Formal Appointee Number 6 (talk) 22:48, 12 December 2013 (UTC)

Source Clarification

Looking for clarification here, you inputted in the List of fictional aircraft article, that "The film aircraft was a modified Handley-Page Halifax/Halton G-AHDM Falmouth. K.A.Merricks book, published in 1980, states: G-AHDM Falmouth went from BOAC to Aviation Traders; then to Westminster Airways; then converted as Reindeer G-AFOH for film No Highway in the Sky" K.A.Merricks is the author? If so what’s the name of the book? FOX 52 (talk) 23:51, 3 December 2013 (UTC)

Merrick, not Merricks (there should be an apostrophe there) and it's his book on the Halifax.

Merrick, K.A. (1980). Halifax: An Illustrated History of a Classic World War II Bomber. Ian Allan. ISBN 0711007675.

Andy Dingley (talk) 11:07, 4 December 2013 (UTC)

Invitation to Trademark Policy Discussion

Hi Andy!

I noticed that you've contributed to the trademark article on Wikipedia. I wanted to reach out to you because the Wikimedia Foundation legal team has just released a draft trademark policy for consultation with the Wikimedia community. The purpose of the new draft is to facilitate permissive use of the Wikimedia trademarks for the community while preserving protection of the marks.

I thought that you may have an interesting perspective to add to this discussion, given your interest in trademark law. I would like to personally invite you to review the new draft and contribute any comments you may have. We plan to keep the discussion open for two months and incorporate the feedback into the final trademark policy. We hope this new version of the policy will make it easier for community members to use the logos to encourage Wikipedia editing.

Best,

DRenaud (WMF) (talk) 00:39, 6 December 2013 (UTC)

Atomic Demolition munition

Andy, just a heads up, I removed the picture you like putting into the article Atomic Demolition Munition again. The reason being, is that the Sedan crater was caused by a deeply buried thermonuclear device with a yield around 104 kilotons. In contrast to ADM's that would not coake, mistnceivably be deeply buried when in use very often, if at all, as I don't think most targets would allow someone to drill a giant well hole to oblige would be atomic demolition teams. You dig? If you could find a picture of a surface burst or shallow underground nuclear explosion in the 20 to 40 kiloton range, that would be a lot more apt. What do you think? As I've just added one that was ~ 1 kiloton in yield.

83.71.31.96 (talk) 12:47, 7 December 2013 (UTC)

My mistake, I thought that Plowshare Sedan had been one of the ADM series. Just checked in Hansen and it isn't. Andy Dingley (talk) 21:03, 7 December 2013 (UTC)

The Wikipedia Library Survey

As a subscriber to one of The Wikipedia Library's programs, we'd like to hear your thoughts about future donations and project activities in this brief survey. Thanks and cheers, Ocaasi ^{t | c} 15:23, 9 December 2013 (UTC)

Green Goddess

Thanks for the Green Goddess picture on Coventry Climax. I am wondering if you have reasons to have placed the pic in the Final Years section, not in the Pre- or Post War. I don't even know what engine type was used on it, so would appreciate your further attention. Yiba (talk) 12:41, 11 December 2013 (UTC)

I'd rather replace it with a picture of the trailer-mounted Godiva pump, rather than the one on the Green Goddess. I didn't put it in any particular section, just restored it, but as the Goddess-specific installation that is post-war, rather than wartime. I would see a specific wartime section as worthwhile; their trailer-mounted fire pumps were a significant part of civil defence planning. Andy Dingley (talk) 14:10, 11 December 2013 (UTC)

Tank article: Porsche as inventor of torsion bar suspension

Hello. I have created a Talk section on the Tank article to discuss this. Can you please justify crediting Porsche with invention of torsion bar suspension or its use on AFVs? Thanks in advance. — Preceding unsigned comment added by Vasiliy Fofanov (talk • contribs) 20:51, 11 December 2013 (UTC)

Tin box

Hi, just a quick note to say that I've mentioned you here. Horatio Snickers (talk) 17:33, 12 December 2013 (UTC)

Hello! There is a DR/N request you may have interest in.

This message is being sent to let you know of a discussion at the Wikipedia:Dispute resolution noticeboard regarding a content dispute discussion you may have participated in. Content disputes can hold up article development and make editing difficult for editors. You are not required to participate, but you are both invited and encouraged to help find a resolution. The thread is "Tin box". Please join us to help form a consensus. Thank you! EarwigBot ^{operator / talk} 17:33, 12 December 2013 (UTC)

SPI question

Hi Andy, I just saw this question. You'll have to ask Future Perfect at Sunrise (talk · contribs) about his reasoning though, I can't speak for him. Alternatively, you could talk to the checkuser team, as they more-or-less have the final say in sockpuppetry investigations. Mark Arsten (talk) 01:54, 14 December 2013 (UTC)

Can we get a few things straight?

Before you come out with something like that again.

• Yes, I was a staunch defender of Betacommand. I believe (and still believe now) that he was hounded off the project by a number of users who didn't like his - mostly correct - enforcement of NFCC. At least two of those editors have since been permabanned, and others have disappeared.
• But no, I will not stand for him socking, if he indeed is doing so. My main concern is that the next account that comes along and aggressively enforces NFCC is immediately accused of being Beta (Werieth wouldn't be the first). However, if Werieth is Betacommand, they should be blocked. I actually think, however, that you aren't doing the SPI many favours with our sock friends' "evidence", though - most of it proves nothing. The "Third door on the left" stuff, for example, was a dramaboard meme a few years ago - [24]. You give me some actual evidence that Werieth is Betacommand, and I'll support a block all the way. But not until then. Black Kite (talk) 20:08, 15 December 2013 (UTC)

I don't know if Werieth is a Betacommand sock or not. I had little to do with Betacommand, I'm not terribly familiar with his style. Personally I see Werieth's behaviour as bad enough of itself to be a problem, whoever he is.

You demand evidence. That's reasonable enough – except that when it comes to Arnhem 96, you're less fussy: At Wikipedia:Administrators'_noticeboard/Incidents#self_admitted_sock you claim that they're blocked: "Oh for goodness sake, Andy. This is a previously checkuser identified blocked editor" Which you then justify with a link [25] to a different editor. Betacommand had a great many editors with a grudge (right or wrong) against them. You can't just extrapolate that because one editor was CU'ed to a blocked editor then all editors acting against Betacommand are the same person! Per AGF, even if you suspect so, you can't act on that basis. Andy Dingley (talk) 20:49, 15 December 2013 (UTC)

But surely you must realise that the evidence is in front of you? An account with that much knowledge of Betacommand's activities is one of two - either a current editor who is hiding their identity (WP:ILLEGIT), or alternatively a blocked or banned editor (WP:SOCK). I don't see any way that this account is not either of the above? (And, to be honest, it's fairly obvious that the CU blocked sock is the same user as this one, even so). If Werieth's behaviour is that bad in itself then surely the preferred location is WP:RFC/U? Black Kite (talk) 19:59, 16 December 2013 (UTC)

"the evidence is in front of [me]" What evidence?, where?

I see good reason to believe that Arnhem 96 is not a new editor. Clearly they dislike Betacommand and Werieth. However that applies to a lot of editors. There is no evidence to link them to any particular editor beyond this. Yet several admins involved in this have persisted in implying that they are. That is factually inaccurate, or as it's called when non-admins do it, "lying".

I do not like socking, nor even alternate accounts (the necessary uses for which are far fewer than those for which they're claimed). I wish that this editor had instead simply emailed me. However what they posted appears accurate. They are diffs: it's a simple matter to verify them. This effort to suppress any discussion of the return of a banned editor is far worse than any minor socking. Andy Dingley (talk) 00:13, 17 December 2013 (UTC)

[rant by harassment sock removed. – Fut.Perf. ☼ 03:30, 17 December 2013 (UTC)]

• Hi, Black Kite (hullo AD). Do you wonder why so many of the people who enforced WP rules against bc when he repeatedly proved that his determination to enforce guidelines was to the detriment of the editing environment and against the consensus of the editorship have since left? Well, I suggest it is because of people not being able to see that edits like this are entirely consistent with the modus operandi of betacommand. I tagged Werieth as a bc sock within weeks of them editing - and had such a fun time at SPI that I went back into retirement. Now I may be no great loss to WP, but how many good admins editors have simply walked away for similar reasons? LessHeard vanU (talk) 22:03, 16 December 2013 (UTC)
• Andy, it seems very clear that one of the socks which posted in that SPI is Wikinger. The IP who participated in the discussion linked to the Japanese version of Wikipedia:Long-term abuse/Wikinger, which looks like self-identification. I don't know who "Formal Appointee" or "Arnhem" are, except that their behaviour suggests that they are both the same person, and the accounts must obviously belong to someone who has been around for some time. --Stefan2 (talk) 15:57, 17 December 2013 (UTC)

Final warning

I have warned you before to stop enabling that sock troll by reposting their material. The troll is clearly engaging in a wiki-hounding agenda, and by colluding with them you are contributing to that wiki-hounding. Proxying for block-evading socks is not legitimate. This goes for any place, including your own talk page. If I see you doing this again, I will block you. Fut.Perf. ☼ 04:01, 17 December 2013 (UTC)

Discussion open at WP:DRN

A volunteer has opened the case. Please feel free to proceed with discussion now. Thanks for your patience. -- — Keithbob • Talk • 18:05, 18 December 2013 (UTC)

It appears that Pkgx has aready done with the discussion. Yet again, everyone else is all wrong. Andy Dingley (talk) 18:26, 18 December 2013 (UTC)

(Non-)Strategic Materials in main Mosquito Article

Hi Andy, I removed the livelink to Strategic Materials because no Article on that subject exists. Are you planning to write one? Otherwise, I recommend you should agree to my removal of the square brackets around the term. Best Wishes.Dendrotek 22:55, 20 December 2013 (UTC) — Preceding unsigned comment added by Dendrotek (talk • contribs)

Please read WP:REDLINK Andy Dingley (talk) 23:10, 20 December 2013 (UTC)

Yes, Andy, I've read that. So again, my question - are you going to write an article on Strategic Materials? I might also add, is this an online encyclopedia, or trying to be a rival to the Oxford English Dictionary?!Dendrotek 21:21, 21 December 2013 (UTC) — Preceding unsigned comment added by Dendrotek (talk • contribs)

I've also removed a few red links. It's good form to write the article first, then link it. Thanks. Magnolia677 (talk) 16:17, 22 December 2013 (UTC)

Either of you are free to write the article yourselves, if you're so keen. Don't let me stand in your way.

If you're so against redlinks, and our long-established practice in this area, then I suggest you take that up at Wikipedia talk:Red link or even Wikipedia:Miscellany for Deletion/Wikipedia:Red link. Andy Dingley (talk) 19:23, 22 December 2013 (UTC)

I looked at the "what links here" on the "strategic materials" red-link article, and every page linking to it is yours. Doing this is not "long-established practice". Please take a moment to read WP:RED, particularly "do not overlink in the mainspace solely for use as an article creation guide. Instead, editors are encouraged to consider Write the article first, or to use WikiProjects or user spaces to keep track of unwritten articles." Thank you. Magnolia677 (talk) 20:49, 22 December 2013 (UTC)

I have to agree with the others. It's a bit questionable to extensively redlink an article you haven't yet written. It's much worse to redlink an article you have no plans to write. --Yaush (talk) 16:45, 23 December 2013 (UTC)

Glad Tidings and all that ...

FWiW Bzuk (talk) 23:46, 23 December 2013 (UTC)

WP:BURDEN

Hello, I'm TheRedPenOfDoom. I noticed that you made a change to an article, Treehouse attachment bolt, but you didn't provide a reliable source. It's been removed for now, but if you'd like to include a citation and re-add it, please do so! If you need guidance on referencing, please see the referencing for beginners tutorial, or if you think I made a mistake, you can leave me a message on my talk page. Thank you. -- TRPoD aka The Red Pen of Doom 13:49, 28 December 2013 (UTC)

Please read the policies you're so fond of relying upon. BURDEN refers to the use of sources to support content within an article. Your claim is instead that a source is invalid; quite a different proposition.

Also please see WP:3RR, as you've already reached it. Andy Dingley (talk) 14:03, 28 December 2013 (UTC)

Nutation RfC

Andy, if you really wish to avoid abuse, why did you add a personal attack to the discussion? It would be much better for you to vote and then take the page off your watchlist. That way your voice is heard but you don't get troubled by any rude responses. RockMagnetist (talk) 17:17, 28 December 2013 (UTC)

I think that people have done everything that needs doing. His edit of Nutation was reverted the same day and Op47 asked him to wait for the consensus. The creation of Nutation (engineering) may have been premature, but it doesn't do any harm. After all, even if the merge option were chosen (which seems unlikely now), it would be trivial to change that article to a redirect. For that matter, an unstated fourth choice would be to leave Nutation as it is but make Nutation (engineering) the main page for Nutation#Mechanical engineering. The important thing is that all the material on nutation in engineering has been left intact. RockMagnetist (talk) 16:56, 29 December 2013 (UTC)

Andy, by your comments at Talk:Nutation, I see that you think you are being treated unfairly. My main interest is not in this fight between you two, but in keeping the RfC on track. I removed your contribution because you fired the first salvo in this round, and there was nothing constructive about your first comment. I was hoping to prevent another pointless fight. I did reproduce your alert about Nutation (engineering), but in a way that was more neutral and informative. I also put a warning tag on the talk page of the IP editor who added the rude comments here. RockMagnetist (talk) 03:04, 29 December 2013 (UTC)

I've refactored this conversation to remove most mention of a 3rd party editor who I have asked not to post here further, and who might be blocked if they do. As a general rule, we should not talk about an editor in good standing in a forum where they cannot respond. If you still need to discuss this other editor, please do so at WP:ANI, or other appropriate forum, not here. Thank you so much for your understanding. Jehochman ^Talk 14:20, 1 January 2014 (UTC)

OK, then, on that basis I'm happy to agree to your request. Andy Dingley (talk) 14:21, 1 January 2014 (UTC)

Please revert your edit

this edit should be reverted and allow someone uninvolved close the discussion. Werieth (talk) 02:15, 3 January 2014 (UTC)

Oh? Has consensus at NFCR suddenly changed, that it no longer fails WP:NFCC#8? Andy Dingley (talk) 03:16, 3 January 2014 (UTC)

Until the discussion is closed by an uninvolved user (which you are not, since you filed the NFCR) you shouldnt be removing the file. Your removal of the file before the NFCR has been closed is inappropriate. Werieth (talk) 03:20, 3 January 2014 (UTC)

Not a principle you've followed! Andy Dingley (talk) 03:22, 3 January 2014 (UTC)

Please find a NFCR that I opened and also closed? I dont close NFCRs that I have commented on. Werieth (talk) 03:25, 3 January 2014 (UTC)

I refer to your practice of blanket deleting images you object to, with, without or during NFCR. Andy Dingley (talk) 03:37, 3 January 2014 (UTC)

I dont remove files during an active NFCR. And its not blanket removal. Werieth (talk) 03:39, 3 January 2014 (UTC)

Inflatable rat

Was it your legendary pettiness or simply some sort of holiday-induced hangover that inspired this? One second of inspection by an educated source suggests the documented rationale is disingenuous at best (the Telegraph has never not been known to relay any right-wing trope carried by the red tops). Generously, you Googled for sources and, finding a bunch of self-reinforcing ones typically considered to be "reliable" by the Twitterati, dumped them en-masse to reinforce the one sentence of non-laughable fact you'd added. I'd suggest that if this were taken to talk, it'd result in removal again. I've thankfully reduced my wasted time on this sort of thing over the last six months; I'd hope you'd help me out in this manner by self-reverting. Chris Cunningham (user:thumperward) (talk) 22:46, 3 January 2014 (UTC)

If you're concerned that these sources are too primary, then I can understand that. I wouldn't trust the Daily Mail to tell me it was Friday, but I do consider it a reliable source for the DM's own soapboxing position that using the rat had turned a union protest into a howling mob. Blanking the lot though and claiming that the Telegraph is an unreliable red top, so untrustworthy as to be deleted on sight, is just ridiculous though. Andy Dingley (talk) 00:31, 4 January 2014 (UTC)

Optional end tags

Hi, regarding the sentence "Many tags, especially the closing end tags, are optional." - this implies that all end tags are optional, which is not the case. True, </p> is omitted more often than it is used - but neither the section nor that paragraph are specific to <p>, and that tag is mentioned only once, in the first paragraph. In HTML 5, the list of optional tags is significantly shorter than the list of all elements. --Redrose64 (talk) 19:41, 8 January 2014 (UTC)

I'm confused by your comment, "Elements: the number of elements with mandatory end tags vastly exceeds those where it is optional (COLGROUP DD DT LI OPTION P TD TFOOT TH THEAD TR) even if you count the empty elements (AREA BASE BR COL HR IMG INPUT LINK META PARAM))"

Are we talking about tags (things in documents) or tag types (definition sections in the standard)? In such a case, the number of omitted </p> far exceeds any number of tag types listed. My point is that the tags which can be and are ignored altogether (like <tbody>) just aren't an important issue for HTML coders or even numerically common, in comparison to the case (above all) of omitting <p /> to explicitly close an element. The common case, vis "especially" is this omitted closure.

As for <br>, that end tag isn't omitted, it's not even permitted. Of course any agent will silently ignore such as error as providing one (esp. for Appendix C reasons), but the standard is still clear that </br> isn't merely optional, it's wrong. Andy Dingley (talk) 23:24, 8 January 2014 (UTC)

In my edit summary, the text "Elements:" is in grey so it's the section heading, not my comment. I was also constrained by the 255-byte limit of the ref summary, so for brevity I listed only those tags which were in HTML 4 and ignored the new ones for HTML 5. In HTML 4, the various elements may be divided into two main groups. The first comprises thirteen empty elements, where the start tag is mandatory, but there is neither content nor an end tag; these elements are AREA BASE BR COL HR IMG INPUT LINK META PARAM (plus FRAME, only found where frames are used, and the deprecated elements BASEFONT ISINDEX). The second group comprises the enclosures, each comprising start tag, content, and end tag. In four cases (BODY HEAD HTML TBODY) both start and end tags are optional; in eleven cases (COLGROUP DD DT LI OPTION P TD TFOOT TH THEAD TR) the start tag is mandatory but the end tag is optional; and in the remainder (A ABBR ACRONYM ADDRESS B BDO BIG BLOCKQUOTE BUTTON CAPTION CITE CODE DEL DFN DIV DL EM FIELDSET FORM H1 H2 H3 H4 H5 H6 I INS KBD LABEL LEGEND MAP NOSCRIPT OBJECT OL OPTGROUP PRE Q SAMP SCRIPT SELECT SMALL SPAN STRONG STYLE SUB SUP TABLE TEXTAREA TITLE TT UL VAR plus FRAMESET IFRAME NOFRAMES (frames) APPLET CENTER DIR FONT MENU S STRIKE U (deprecated)), both start and end tags are mandatory. Of the elements deprecated in HTML 4.01, three (MENU S U) are no longer deprecated in HTML 5.

So out of about 115 different elements defined in the HTML 4 standard, there are 28 where an end tag is either optional or invalid, giving 87 where the end tag is mandatory. This is what I meant by "the number of elements with mandatory end tags vastly exceeds those where it is optional". The phrase that I used later "even if you count the empty elements" refers to including the 13 empty elements among those which do not have a mandatory end tag.

To return to the sentence "Many tags, especially the closing end tags, are optional." the "many tags" here totals just 19: the start and end tags for BODY HEAD HTML TBODY (i.e. 8 tags) and the end tags for COLGROUP DD DT LI OPTION P TD TFOOT TH THEAD TR (11). I therefore feel that "many tags" is significantly overstating it. --Redrose64 (talk) 01:14, 9 January 2014 (UTC)

I think we're coming at this from different directions here: you're counting the types of tag, I'm counting their incidence in documents.

I have little interest within this scope in the <thead> case. It's a high level article, that's obscure. I don't think it really belongs there. What I'm more interested in is the hugely common issue of omitting </p> (and maybe </li>) because the ETAG is genuinely optional and implied by the DTD content rules. That's what I think needs mention here. If you have any other forms of wording that would make this clearer, then I'm not attached to the current form of words, but I do think the emphasis should stay on the very common tags that require the start tag but make their end tags optional. Andy Dingley (talk) 13:58, 11 January 2014 (UTC)

I don't know why you're singling out <thead>, I only mentioned it as part of a list that would otherwise be incomplete. The impression that I don't want to give is that the end tags for commonly-used elements (like <a>...</a> <div>...</div> <h1>...</h1> <i>...</i> <table>...</table> <ul>...</ul>) are optional, when they are definitely mandatory. Browsers vary in the methods that they use for coping with these elements if they are found not to be closed. --Redrose64 (talk) 19:20, 11 January 2014 (UTC)

Panzer II

You reverted to a DAB link. Perhaps you can fix this. Dougweller (talk) 14:35, 12 January 2014 (UTC)

We don't have a better target. Drivetrains aren't the same thing as powertrains, and in this case drivetrain is significantly correct (lack of new engine developments became as big a problem for Germany in the late war as they had been for the UK in the early years.). Really we need an article at drivetrain (drivetrain) (or better, move drivetrain to drivetrain (disambiguation). Andy Dingley (talk) 15:23, 12 January 2014 (UTC)

No problem. All I was really doing is correcting a spelling correction, someone changed it to "drive train". Thanks. Dougweller (talk) 18:44, 12 January 2014 (UTC)

A barnstar for you!

	The Original Barnstar
	For preventing Bible translations into the languages of China from being quietly blanked. Thank you. In ictu oculi (talk) 12:38, 13 January 2014 (UTC)

Thankyou, I hope both articles may flourish. Andy Dingley (talk) 19:16, 14 January 2014 (UTC)

Proposed deletion of Mr Whoppit

The article Mr Whoppit has been proposed for deletion because of the following concern:

all the "sources" are of absolutely non reliable kind

While all constructive contributions to Wikipedia are appreciated, content or articles may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the article to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. -- TRPoD aka The Red Pen of Doom 23:15, 14 January 2014 (UTC)

Nomination of Mr Whoppit for deletion

A discussion is taking place as to whether the article Mr Whoppit is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/Mr Whoppit until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. -- TRPoD aka The Red Pen of Doom 23:30, 14 January 2014 (UTC)

Your GA nomination of Gaunless Bridge

Hi there, I'm pleased to inform you that I've begun reviewing the article Gaunless Bridge you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of ТимофейЛееСуда -- ТимофейЛееСуда (talk) 22:12, 15 January 2014 (UTC)

Your GA nomination of Gaunless Bridge

The article Gaunless Bridge you nominated as a good article has been placed on hold . The article is close to meeting the good article criteria, but there are some minor changes or clarifications needing to be addressed. If these are fixed within 7 days, the article will pass; otherwise it may fail. See Talk:Gaunless Bridge for things which need to be addressed. Message delivered by Legobot, on behalf of ТимофейЛееСуда -- ТимофейЛееСуда (talk) 17:02, 16 January 2014 (UTC)

Your GA nomination of Gaunless Bridge

The article Gaunless Bridge you nominated as a good article has failed ; see Talk:Gaunless Bridge for reasons why the nomination failed. If or when these points have been taken care of, you may apply for a new nomination of the article. Message delivered by Legobot, on behalf of ТимофейЛееСуда -- ТимофейЛееСуда (talk) 00:52, 17 January 2014 (UTC)

A barnstar for you!

	The No Spam Barnstar
	Thanks for prodding the relatively tiny New Apostolic Church in India. Bearian (talk) 23:27, 22 January 2014 (UTC)

Coke (fuel)

Andy: How is my edit vandalizing? ~~Junvfr <~_~> (talk) 23:22, 1 February 2014 (UTC)

Hi your edit certainly wasn't vandalism and no-one is calling it that. However coke isn't mined either: coal is mined, then coal is turned into coke in a coking oven on the surface. Andy Dingley (talk) 23:32, 1 February 2014 (UTC)

ani 3rr

You're aware of WP:3RR, right? NE Ent 19:50, 5 February 2014 (UTC)

I can count: [26] [27] [28]

Four: [29]

I'm sure User talk:Future Perfect at Sunrise#Heads up will act equivocally in this, now that he's been canvassed for his support. Andy Dingley (talk) 19:55, 5 February 2014 (UTC)

I did not canvas anyone, FPaS was the one who gave you the last warning in regards to you proxying for a sockpuppet. I felt it appropriate to give them a heads up that your behavior has continued despite the warnings that where given. Werieth (talk) 20:01, 5 February 2014 (UTC)

Who is the sockpuppet? The rather obvious 79.70.66.86, 79.70.79.23, 79.70.66.74? Or Garbage turk, for whom you have provided no evidence that they are a sock of a blocked user, merely that they are challenging your behaviour in a way that you don't like.

If you have evidence that someone is a sockpuppet, then go through SPI and demonstrate this. Otherwise you have no justification for claiming Garbage turk to be a sock, let alone for claiming they're also an (unidentified) banned user. Andy Dingley (talk) 20:08, 5 February 2014 (UTC)

(edit conflict) I have already had a CU look into it and they blocked several socks. I have already requested a CU for the newest sock. Werieth (talk) 20:12, 5 February 2014 (UTC)

Werieth didn't block Garbage turk as a sock, so your issue isn't with him.NE Ent 20:10, 5 February 2014 (UTC)

Werieth is repeatedly blanking my comments and Garbage turk's at ANI (see diffs above: 4RR at ANI and 5RR6RR (so far) at User talk:Garbage turk) on the grounds that Garbage turk is a sock of a banned user. There is no evidence for this. At User_talk:Hell_in_a_Bucket#ANI he offers to "[...] provide some(sic) the account names." but has not done so, either now or in the past. AGF still applies to Garbage turk. We have no reason and even no right to treat them as if banned. Andy Dingley (talk) 20:16, 5 February 2014 (UTC)

Note

I think my warning from last time was quite clear enough, and the fact that the Garbage turk (talk · contribs) account was the same harassment troll who was involved the last time was quite obvious enough. Please don't insult our intelligence by going on about how there was "no evidence" about it – continuing that pretense would only put your own acting in good faith into doubt. The only reason I'm not blocking you right now is that the offending account has been blocked in the meantime, so I suppose at this point the block would come across as "punitive, not preventive" – but rest assured that if it turns out you continue with this kind of behaviour, blocks will come, and with no further warning. Fut.Perf. ☼ 22:18, 5 February 2014 (UTC)

Then please raise me at ANI.

I disagree absolutely with your self-created policy that some users are non-persons and their words must be removed from all places. Not can or even should, but you impose this as must, against the direct wishes of other GF editors.

As best I understand it, we have two socks. One is Arnhem 96 / Garbage turk etc. They appear to me to be an editor acting in what is a GF attempt to expose Werieth as the returned sock of Betacommand. They are far from alone in believing this, per the several SPIs. I believe this myself. I am permitted to believe this and I am permitted to tell other editors that I believe this. You might note some very specific comments to that effect at User talk:DeltaQuad#Troll sock series

There is also another sock, which I now believe to be Wikinger. I have no idea who Wikinger is/was and don't particularly care – although it would have been extremely useful for you to tell me this at the time. This was the sock over whom we previously had the dispute. I have no interest in furthering the aims of such a troll (cheers for the little hint there that my own good faith is in such tenuous regard). However I have even less interest in facilitating the career of Betacommand. You surely do not believe Garbage turk to be Wikinger or you would have presumably simply come out and said so.

There is a significant difference between the two of these: one is known and banned. Garbage turk is not (Werieth claims to know who he is, but won't divulge this). You and Werieth do not, per AGF, have the right to behave as if you "know" that Garbage turk is banned and so feel free to ignore 3RR et al in your pursuit of him.

You behaviour is unpleasantly partisan. Werieth can behave badly everywhere and lie repeatedly in the ANEW and you say nothing. An IP can sock away in the ANI thread, or attacking my talk: page, and you do nothing. Yet Garbage turk appears and suddenly they're a worse editor than Betacommand and must be blanked and their edits, even to their own talk page removed beyond all regular practice. I'm just surprised that their post at ANI hasn't been revdel'ed yet. A post that doesn't breach CIVIL any more (about 300 milliErics) than is already common at ANI. Mind, I suppose you object to his pointing out that you as "a hard line NFCC admin" have so much of a shared interest with both Betacommand and Werieth. As for your rapid response to Werieth canvassing you on your talk page, that's shameful.

In User talk:Arnhem 96's block we see user:Floquenbeam taking the bold step of "taking ownership" of the block because the original blocking admin was in a dubious position. That's a positive action and I commend them for it. I would do exactly the same with Arnhem 96's detailed comments for the Betacommand SPI as I support each part of them. Per WP:EVADE, " Editors who subsequently reinstate edits originally made by a blocked editor take complete responsibility for the content.". Yet in that case I was not allowed to do so, under your threat of immediate blocking. Not because they were Arnhem 96's (you still do not know who Arnhem 96 is) but by using the excuse that a Wikinger sock had now become involved. Perhaps I was indeed naively being used by Wikinger for their trolling, but no more than you're letting yourself be used by Werieth. Andy Dingley (talk) 23:31, 5 February 2014 (UTC)

I'm honestly tired of debating the whole ugly proxying-for-socks issue with you. I'll just say this much: Yes, of course "Garbage turk" is a blocked/banned user. He is, at a minimum, a sock of the other socks (User:Arnhem 96, User:Formal Appointee Number 6 etc.). Since he was blocked on those accounts, his reappearance is, obviously, block evasion, which automatically makes his edits fall under the removal rules. It really doesn't matter if there is an identifiable named sockmaster behind these known accounts and whether that master is currently banned or not. Anybody who creates this many throwaway accounts for obviously illegitimate purposes is de facto banned. If there is some as-yet-unknown good-hand account of the sockmaster that is seemingly still in good standing, so much the worse for them; if it were ever to be identified it would simply be treated as yet another previously undetected sock, and blocked immediately. Through his harassment sockpuppetry, Arnhem 96 or whoever is behind him actually is a "worse editor than Betacommand" – Betacommand had his character flaws but was otherwise undoubtedly a committed and good-faith contributor. No committed good-faith Wikipedian could ever engage in serial sockpuppetry of the kind this person has engaged in. Calling this a potentially good-faith behaviour is just outrageous and unworthy of a person of your intelligence.

I'm honestly at a loss to understand where you think User:Wikinger comes into all of this, though. You must have misunderstood something about this. IIRC, there were some Wikinger IPs turning up at one of the SPIs back in December, but they were certainly not the sock "over whom we previously had the dispute". The socks I warned you not to support back then were obviously not Wikinger but that Arnhem 96 series. Fut.Perf. ☼ 00:24, 6 February 2014 (UTC)

You haven't debated a thing. You've threatened. And worse, you've threatened at Werieth's beck and call. Shameful. Why are you so afraid of an editor, blocked, socked or whatever, raising the relevant diffs for that SPI so that previously uninvolved editors can then judge that SPI? Andy Dingley (talk) 00:49, 6 February 2014 (UTC)

Hi-fi icons

So far, I've covered Arnold Wolf • Isobaric speakers • Ivor Tiefenbrun • JBL Paragon • Julian Vereker • Linn Products • Linn Isobarik • Linn Sondek LP12 • LS3/5A • NAD 3020 • Naim Audio • Naim Audio amplification • Naim NAIT • Rega Planar 3 • Quad Electroacoustics • Quad Electrostatic Loudspeaker‎ • Roksan Audio • Roksan Xerxes • Totem Acoustic • Yamaha NS-10. Do you have any other suggestions? -- Ohc ^¡digame! 14:09, 7 February 2014 (UTC)

Yes, I noted several of those. Something on cartridges might be good - I don't think we have much there at present. Just explaining the principles well would be nice. Where there any mega-selling cartridges worth individual note? Didn't Shure have one? Otherwise, for simple "notable from sheer numbers" there's the Dual C-505 and the Mission 700s. Heybroook HB-1s? I've a pair of those upstairs waiting for me to glue new foam surrounds into them. Andy Dingley (talk) 11:30, 8 February 2014 (UTC)

Rolls-Royce C range engines

I have an original Rolls-Royce Workshop Manual. There is no specific definition of these engine in terms of "range" or "series" but the word "range" appears in a couple of places. Bruce Agland 10/2/2014 —Preceding undated comment added 05:13, 10 February 2014 (UTC)

Blimps

Hi,

Since you reverted my edit to the Airship article, you may wish to contribute to the discussion at Wikipedia_talk:WikiProject_Aviation#Blimps. — Cheers, Steelpillow (Talk) 15:59, 10 February 2014 (UTC)

The Werieth/Betacommand sock

Hello Andy. Here is an up to date presentation of the reasons why Werieth and Betacommand are one and the same user. Obviously with Future Perfect's transparently corrupt threats hanging over your head, you probably shouldn't do any thing about it on-wiki, but I think you can see that it's enough that you would expect some sort of response if you, as an established Wikipedian, were to email arbcom asking why I have been blocked by SPI clerks of all people, and you have been threatened by an admin who is so obviously involved with the banned user, merely for pointing it out.

Reasons to believe Werieth is a sockpuppet:

• He's never editted like a new user on any WMF project
• His excuse for that is just having "watched stuff"
• He has never explained how any of the accusations are wrong
• He goes to extraordinary lengths to get the accusations hidden
• He claimed "SPI determined that I am not a sock" - that's obviously false

Reasons to believe Betacommand would evade a ban by socking:

• Category:Wikipedia sockpuppets of Betacommand
• He was familiar with CU/SPI processes (he even wrote an SPI clerk bot)

Reasons to believe Werieth is Betacommand:

• Betacommand's en.wiki ban gained majority support on 5 Feb 2012
• Werieth's first edit to any WMF project was on on 6 Feb 2012 (Simple Wikipedia)
• Werieth then waited 4 months before editing en.Wikipedia (CU data goes stale after 3)
• They are both utterly obsessed with NFCC
• They are both wikignomes
• There are 101 other behavioural similarities between the two:

the 101 reasons

Betacommand had a non-trivial amount of edits at Commons/Simple/Meta - so does Werieth Werieth's first (and in some cases all) edits to all WMF projects are all typical of Betacommand (read on) Betacommand made numerous edits to other projects for test/maintentance reasons - so does Werieth Werieth's knowledge of Wikipedia norms/practices/policy/precedents is not consistent with his experience - it is extremely consistent with Betacommand's though (see below) Betacommand would often fail to accurately recall his wiki history when it suited him - so does Werieth Betacommand edits thousands of Wikipedia articles, with no preferred topic - so has Werieth Betacommand's main interest in Wikipedia was NFCC enforcement/policy - so is Werieth's Betacommand's interest in NFCC appears to be at obsessive compulsive level - so is Werieth's Betacommand enforces NFCC using scripts & batch editting - so does Werieth Betacommand takes a hard line interpretation of NFCC (might==must, etc) - so does Werieth Betacommand's interpretation of NFCC was rigid, and impervious to feedback - so is Werieth's Betacommand was always "too busy" to fix obvious/trivial NFCC errors himself - so is Werieth Betacommand claimed it was not his responsiblity to fix obvious/trivial NFCC errors - so does Werieth Werieth's knowledge of NFCC discussions/precedents is not consistent with his experience - it is consistent with Betacommand's Werieth's knowledge of NFCC policy/guideline/essay links is not consistent with his experience - it is consistent with Betacommand's Betacommand had a side interest in batch run gnoming, including typo fixing, ref. expansion, file orphan tagging, external link formatting & various regex replacements - so does Werieth The vast majority of Betacommand's article space edits were script assisted batch runs - so are Werieth's Betacommand had a side interest in technical/VPT type issues, including bots, scripts, template coding, the spam black/white list - so does Werieth Betacommand had a total disinterest in actual article writing - so does Werieth Betacommand had a total disinterest in non-technical issues - so does Werieth Betacommand's total disinterest in the community aspect of Wikipedia was always reflected by his user page (devoid of anything helpful/personal, except soapboxing/demands to others) - Werieth's remains similarly devoid What little use Betacommand made of his user page was as just a testing sandbox - just like Werieth Betacommand had great difficulty in accepting he was ever wrong in policy - so does Werieth Betacommand always shied away from settling disputes through direct communication - so does Werieth Betacommand instead preferred to 'report' those people for 'action' - so does Werieth Betacommand used to frequently threaten to get opponents topic banned or blocked - so does Werieth Betacommand would often accuse critics of "harassment", "personal attacks" or "stalking" - so does Werieth Betacommand was always easily riled by any accusation, fair or foul, and displayed no ability to 'rise above it' whatsoever - so is Werieth Betacommand would often follow his own critics to unrelated venues to blacken their name - so does Werieth (against User:Andy Dingley) Betacommand used to call others incompetent or inexperienced, even 5+ year veterans - so does Werieth Betacommand used to express frustration & even contempt for any admin who didn't do what he wanted - so does Werieth Betacommand had a long standing difficulty in understanding what is and is not "vandalism" - so does Werieth (his attempts to silence me have even included reports to AIV) Betacommand would often revert a page 10+ times rather than seek help, or even after seeking help - so does Werieth Betacommand had frequent difficulties understanding 3RRNO - so does Werieth Betacommand had multiple blocks for edit warring - Werieth already has at least one 3RR block Betacommand would often sit out short term blocks without comment - Werieth did the same with his first legitimate block Betacommand used to alter the talk page headers made by critisc to belittle them - so does Werieth Betacommand used to avoid sanctions by making unofficial deals with admins - so does Werieth Betacommand used to then wikilawyer his way around those deals - so does Werieth Betacommand would often contact NFCC sympathetic admins Black Kite/Future Perfect/Masem rather than use AN/ANI - so does Werieth Black Kite used to try and distract people from scrutinising Betacommand - Black Kite did the same to me when I first raised this issue at AN/I Future Perfect at Sunrise was opposed to any ban of Betacommand - Future Perfect at Sunrise is trying his hardest to obstruct this investigation Masem used to frequently try to persuade/warn Betacommand to change his methods - Betacommand always ignored him, and Masem never followed that up. The same sequence of events has played out with Werieth/Masem Betacommand's frequent typos & other language uses were often indicative of some kind of underlying literacy issue - so are Werieth's (that's not to denigrate anyone with literacy issues, even Betacommand) Betacommand never uploaded non-free media to Wikipedia. Werieth does, but he is trying to use this as a smokescreen, but it's obviously a con: Werieth only uploads obviously acceptable non-free media to Wikipedia (book covers) Werieth only uploads book covers when he is being accused of sock-puppetry Werieth has no other discernible interest in book articles Werieth has no other discernible interest in using any other kind of non-free media

Bort Nort (talk) 19:22, 11 February 2014 (UTC)