These days, our editorial staff is pretty much on top of plagiarism. Stolen or half-assedly altered text doesn’t stand a chance of making it to the bottom of New Writeups before at least one editor notices the offense. Back in the crummy old days this was not the case. Our staff was smaller, more scattered, and less able to communicate among itself and with users. When I was your age, we didn’t even have a Chatterbox.

For these reasons, and because the rules of kosher, legal noding were not yet set in stone, a lot of plagiarism slipped under the collective radar. I have recently been sorting through a lot of 2000-2002 material, and am finding abhorrent amounts of plagiarized work and violations of copyright. This ranges from very shitty paraphrases (altering a word in every other sentence does not make it original text), to credited but copyrighted text, to outright shameful copy-and-pasting claimed as the user’s own creation.

The worst news is, some of these long-fled noders are still much beloved here. One of them, I am surprised and sorry to say, was an editor. If these people were still active on the site I would be more than happy to work with them on rewriting their text. But they’re not here, so all I can do is delete.

I would be a bit of a wank if I started naming names of people who are not here to speak up for themselves. I am posting this log because I know at some point, somebody is gonna plotz over the overnight disappearance of half their favoritest noder’s body of work.

If you feel you might plotz, please pause before accusing the editorial staff, or me, of some kind of wack baseless secret mass deletions. Consider that past noders simply lived up to past editorial expectations, which were a lot more free & loose than they are today. I certainly copied and pasted in my fair share of cowboy slang and crop disease definitions, before I understood why that wasn’t cool. The difference is, I’m still around to remove my own mistakes, but these fled noders are not. So I’m sweeping up.

Fellow editors, if you have questions about any nuked writeup just let me know - I am keeping comprehensive notes as I track down plagiarized and infringey writeups. Some of them were hard as hell to ferret out (copied from now-defunct sources, etc.), but I’m not deleting anything until I am absolutely sure it’s a ripoff of someone else’s copyrighted work.

A great many of these writeups were long, impressively detailed biographies of various cultural figures. Over the years nobody has written anything here on Robert Frost, I assume because the guy already appeared to be well-covered. And he was; it was a lovely writeup. But it was stolen, so it’s gone. Similarly, we now have no writeups on ABBA, Shel Silverstein, David Mamet, or Nebuchadnezzar.

As always, if anyone runs into an apparently plagiarized writeup, old or new, by fled or active user, please feel free to msg me and I will be happy to handle it.

The following topics are empty or lacking as a result of this ongoing sweep. They are great starting points, if you're stumped or just bored. Please let me know if you fill any, so I can remove them from the list. More empty topics on my scratchpad.

And a whole bunch of dinosaurs:

Last Month

Locking accounts

A recent tempest in a teapot makes me think that I should restate our policy and process on limiting and/or locking user accounts. I think that I have covered some of this before, but it's good to be open about how this works.

The senior admins, a.k.a. 'the gods' (ref: The Power Structure of Everything2) have both punitive and beneficial powers for managing the user base, over and above the content-management powers* with which we are all familiar.

Punitive powers and their usage have evolved considerably from the early days of e2. In the elder days the punitive tools were rather coarse: locking accounts by replacing the user password, silencing a user in the catbox with EDB, and 'cursing' users by removing XP. dem bones long ago began moving us away from these negative-feedback options. As well, the e2 coders gave us more fine-grained control over user permissions. As such both the 'curse' and EDB are largely retired, and account locking, while still sometimes used, is reserved for a last resort.

In preference to fully locking an account, which denies a user all access, we can restrict an account from posting writeups. This power is used not infrequently to control overt trolling, posting of commercial content and hate speech, and other antisocial-to-e2 behaviour. I have used this a few times in 2006. Reasons include blocking semi-commercial content from a user with an amateur porn site and to prevent the continual reposting of semi coherent holocaust denial material. In the vast majority of cases, this power is used to block level 1 users who have no intention of really contributing to the site.

Senior admins can also suspend a user's ability to cool, vote, or post home node pics. I can't remember the last time that any of these was used ... usually folks who have earned the levels that grant these powers don't abuse them.

Accounts are rarely fully locked. If they are it is typically for flagrant anti-social behaviour, such as abuse of fellow noders in the chatterbox. Instead of password changing we now have a "lock/unlock" function which simply disables user log-in. It if very rare that an active user with a history of acceptable content will have an account locked. Usually these folks value the community and know our rules of conduct.

Sometimes users themselves ask for the account to be locked as part of leaving the site. More often they want the account deleted. Why don't we do that? It is more problematic for us than it seems -- much of the code and data keeps hooks to the user account (node heaven, message tables, etc.) so we prefer to simply lock accounts. In cases where the user insists that the account be 'deleted' we can rename the account and clear any personal data from it. I've taken to renaming an account using the nodeID in such cases, so if I was removing, say, Dman I'd rename his account something like DMan12345. This also lets me 'free up' the account names of long-fled users when someone else wants to use the same name.

In closing, two things: First, you can assume that if a user account is locked, the entire admin team will be aware of the reasons and in agreement, and that I'll tell you about it here if I possibly can. Second, sometimes a rumour of barbarous and Draconian admin behaviour is just that, a rumour.

Magic powers of Lord Brawl

Simply put, there are none. Some folks seem to think I have special access to e2's innards. Nope. I have the same powers as all of my peers in e2gods. Any advantages I have are largely due to longevity on the site, so that I know how and where to do things. My programming background also occasionally lets me manipulate minor things in perl. I'm deathly afraid of corrupting the database or bringing down the site, though, so I'm ultraconservative about messing with the code.

Slow times in New Writeups

There's been talk that we're having a content drought. Perhaps so, but I don't think it's because we are frightening away droves of new users. Perhaps we need to freshen up the look -- ktherjoker's proposed new front pages may help when ready. Maybe we need to recruit new users more actively? Where would we find the sort of folks who would like it here? Well, odds are you all know someone. Invite them to e2! If that's something you're not comfortable with, I'd love to know why. Day logs might be the best place for responses to this question -- private messages to me will take a while to collate and post. If a theme or themes emerge, I'll try to fix any problems that I am able to tackle.

Which brings us to another item. paraclete has presented a proposal on her home node:

Limited terms for Content Editors

While I'll assume you've just popped off to read it, and are now back, I'll recap it so that she can remove it later on and this log will still be somewhat coherent. In a nutshell, paraclete opines:

  • that the pool of Content Editors is a little stagnant.
  • there was very little in the way of rotation of new blood.
  • some CEs have been hanging onto their sheriff's badge for over 4 years now.

Let me address some of those points. When I took over for dem bones back in November, I spent a month or two getting used to the different demands of the role, and then I embarked on a project to refresh the CE pool. I also wanted to make the process more transparent, to reduce the appearance of cronyism. In December I asked for bios from current and potential CEs. I then spent most of two months confirming the interest of current CEs, talking to applicants, and trying to pick a balanced crew of people for my first CE intake.

I think that worked pretty well. I tried to pick folks with different perspectives, to respect the input of current admins and senior users, and get a team of folks who'd loved e2 and would try hard. Not everyone was happy and there was some pain, but in the main I think the new folks are doing well. I mishandled communications with some of the folks I didn't pick, which was probably my biggest mistake.

At the time, dann and I had discussed the idea that all admins ought to be *active* users of the site. I was reluctant for a couple of reasons - I hadn't yet gotten a good feel for what every admin was doing, and I myself wasn't noding the way I wanted to. I wasn't going to ask the CE team to do something that I wasn't doing myself!

Enough time has passed that I now feel comfortable making 'active noder' a requirement for the Content Editor team. For now this will simply mean "has made meaningful contributions to the database in 2006" but I expect to make it more concrete (maybe "contributes a meaningful writeup every month") down the road. This means that some longtime CEs will be asked to step up or step out.

After some thought (not to mention getting privately ripped!) I am not going to hold the e2gods team to the same standard. I'm going to strongly recommend it, but not require it. MY main reason for this is that a number of the e2gods contribute to the site in specific ways that don't generate writeups. Some of them are our coders. Some offer us legal advice and guidance. Some are responsible for e2's servers and/or access to U. Mich. bandwidth. In short, there are folks in 'gods' who are important to the site in ways that the user base can't always see. In an ideal world they would be in a different category than 'gods'. However they often need some admin access, and this is a case where the site design thwarts major change. It tends to say "if god or CE" on permissions in several hundred places, each in slightly different ways. It's just not worth the hassle of trying to make a big change. So, not all of the e2gods will be active noders. (one or two current CEs are moving to the e2gods team for this reason.)

I'll promise you this -- gods who are actively working as CEs, editing user content, marking writeups for removal, etc. will be held to the same standard as the CEs.

Ahem. Dude! Limited terms for Content Editors?

Oh yeah, right. I'm not yet ready to go there. I see the appeal in some ways - I'd love to be actively rotating in qualified users, and to give some current CEs a break so they could node more and enjoy the site. At the same time, I have a number of qualms. Among them:

  • Managing CEs is a bunch of work for me. I manage at my real job, and now I manage at my hobby. I am not eager to make my hobby into yet more work.
  • Some of the long-time CEs are the backbone of e2 - they have been a long time in the traces, but they're active, helpful, and not too obviously loco. I don't want to lose the services of these folks due to a time limit. But I also don't want to create yet another class of editors. And I don't want to solve this by making even more e2gods.

It may be possible to solve these problems, but I'll need some time to think of the ramifications, and talk to some folks. So I'll do that and report back in a future ed. log. In the meantime, perhaps some of the CEs will volunteer to take sabbatical.

Paraclete touched on a few other items:

  • The level system and opportunity for 'advancement': This is a big topic which I'll leave for now, in hopes of doing justice to it later.
  • The "one out, one in policy" for CEs that she alludes to isn't fully accurate. It's more the case that I thought the CE pool was overstocked. I really want less CEs who are more active, but at the same time I want CEs from different time zones, specialties, etc. which drives the numbers up. 30 seems to be a "sweet spot" in terms of having CEs around without swarming the site, and without overloading my span of control. But it's not an absolute.
  • "There may be users out there who would be just as good, given the chance. But who just aren't being given the chance, and just won't ever be, under the current system." I've managed the CE alias for just over 6 months and have made one set of changes. I've been planning to make another set soon anyway, and this gives me the necessary nudge to get it done now. I think I can keep it reasonably dynamic without term limits. I'm not sure I can make a specific commitment though - again, I need to consider and discuss this further.

dann suggested to me once in another context that we hold some sort of vote. An e2 election has all kinds of interesting implications: campaigning, voting, ballot stuffing, and possible victory by a "troll ticket" (I'll let you guess who I imagine would be on it). Yet the idea of letting the user base vote on some CE positions does have appeal. If nothing else it'd be an interesting way to generate a short list for a new CE intake. But yet again, the mechanism and controls need some thought.

This raises the obvious question "Who is Lord Brawl that he gets to decide all these things?" Fair enough. I'm someone that dann (and dem bones) picked to manage the CEs. Somebody has to do it, I had lots of admin experience here, and I think I do a decent job of it so far. The time may come when it's my turn to take a sabbatical, too -- but not quite yet, I think. In the meantime the admins and I do try to listen to your comments and criticism and to make e2 an open place. Please keep asking, suggesting, and questioning.

Next Month


* One of my peers notes that I could also mention "the 5 XP penalty that was sometimes invoked when nuking a wu." To be honest, I don't remember this mechanism clearly. Long discarded, I think. In any case, writeup removal on e2 as implemented today subtracts 1 XP, to balance the 1 XP that was granted when the writeup was created.

I'd like to talk about Paraclete's concern about the letters to the editor. I'll take the hit for that one. Short answer: it was a breakdown of communication.

Long answer: The e2 gmail account is a massive spam-trap, and finding the real stuff was sometimes difficult. Also, there was very little. I haven't seen anything useful in months - what there was was essentially the collection enclosed in the first letters to the editor writeup and Paraclete's writeup.

To help with that, and as the sort-of unspoken secretary of that email address (mostly because I set it up, though it was Borgo's project. I just kept the dust bunnies away), I did three things: I flagged spam, I fielded standard editorial questions that I felt didn't need a letters to the editor-type response, and I flagged interesting questions for somebody else to take care of.

The problem was, I kinda assumed that someone would notice the writeups flagged as 'letters' and, you know, do something to them, be it answer it themselves or pass it up the chain of command. This was all unspoken, by the way. We didn't organize this so much as it fell into place. And after interest in the project slaked off, I failed to notice that Paraclete's writeup was still there and not responded to. I'll cop to that one. Hopefully you'll get an honest-to-god thought on the rest of paraclete's daylog shortly.

It was a trial run, and it failed in some ways. I'll try to do something about that.

Having said all of this, this information bears repeating: The e2 email address is e2editors at da gmail (dot) com. Which the exception of paraclete's letter, which I'm sorry about missing, we've seen nothing in quite awhile, probably because the notice has disappeared off of NFN. Talk to us; we'll try to make things clearer for you.

Well, I'm annoyed. No, not at the recent controversies surrounding editors and letters to 'em, but my usual, points of grammar.

One day at work, while perusing the somewhat interesting news items on our intranet, I came across an article reposted from the Business Roundtable. It had to do with the United States' lack of preparedness for a “cyber catastrophe”. As I read on, I saw terms such as “cyber infrastructure”, “cyber security”, “cyber disaster”, and so on.

Now, the last time I looked (, cyber was not a word unto itself. A prefix, yes, and requiring either a hyphen following it: cyber-security, cyber-terrorism; or to be joined to the word following: cybercop, Cybermen, and so forth.

As I read along, my indignation grew to the point that it was all I could do to finish the article. Particularly when I reached this quote:

“If our nation is hit by a cyber Katrina that wipes out large parts of the Internet, there is no coordinated plan in place to restart and restore the Internet.”

What, I might ask, being the pedant I am, is a “cyber Katrina”? Though words brought together to make a compound may be written, at times, without a hyphen, I reiterate that 'cyber' is not a word – unless you use it in its slang sense, generally taken to mean cybersex, and I doubt if that's what the Roundtable had in mind (one never knows, though).

Though, thankfully, we don't appear to have this problem occuring in E2 writeups, I still encourage everyone to revisit the uses of the humble hyphen. Perdue University points the way:

Meanwhile, back at the desk …

Rendering assistance:

Recycled nodegel:

  • E2 Nuke Request by eruhgon – Advised noder to take it to the daylogs. Turns out I was mistaken in nuking this one!


The original Business Roundtable article is located at
See if you can make it to the end.

Log in or register to write something here or to contact authors.