New Netiquette
These thoughts have been spinning around in my head—and not just mine; I admit, I'm probably repeating a few things I've read over the past six months, as well as adding my own spin—but have started to solidify into something almost blog-worthy.
Over the past few days I've been watching a mini-kerfuffle happening on LITA-L (arguably one of the more tech-savvy mailing lists in libraryland, which might be the source of my surprise), wherein a number of people wrote to the entire list to ask for Google Wave invites—and I won't pretend I didn't let out a tiny annoyed huff and eye-roll, myself, when I saw the flood of short "please give me Google Wave" messages—and a number more wrote back (with a new subject line!), expressing stern opinions about the decline of netiquette and the inappropriateness of sending "short 'me too'" messages out to a list. Then a number more replied to the stern ones, saying, in essence, "Use Gmail and get over it." Then that, too, got discussed, with the "use Gmail" mentality being boiled down, by the stern ones, to victim-blaming. I've seen this argument hashed out and rehashed on other, sometimes far less civil, mailing lists. And, I've found, my views on this subject have evolved from the stern to the, if you want to call it that, victim-blaming.
Now, like I said, I'm running the risk of repeating things others have already said, here. Looking back over my Reader feeds for the past few months, this is definitely one of the things that have affected my thinking on this. There are others. (Neal Stephenson may have had a bit of an effect, as well.) It's hard to say what all the influences in my thinking really are; I'm exposed to more information than I know what to do with, every single day. So, I hope, are you.
Which sort of brings me to my point. This isn't 1990, and to cling [and try to force others to cling] to the netiquette of 1990, in lieu of taking control of your own information influx, seems to me to be backwards-thinking. For the LITA-L list, specifically, people must know that the library field, the IT field, and the crossover between them are huge. Even if everyone follows all the old school rules of netiquette, sending only what's necessary to mailing lists, there's still so much there. And that's without Twitter and Facebook and RSS feeds and the like. Anyone who reads every message coming across every relevant list and RSS feed is clearly not getting any real work done.
What we need to be doing—and we, as librarians, should be helping to train our patrons/customers/users [that terminology is a fight for another blog post] to do—is intelligently filtering all of it, to get the very best of what's out there. There's no perfect system for doing this, yet, but we need to do what we can with the tools we have, even while keeping our eyes open for other tools. For a very easy start, nobody should be reading mailing list traffic without a mail client that supports threading. (Hint: pretty much all of them do, particularly since Gmail came on the scene. Odds are, you can have threading-by-subject in your email without ever giving over your private information to the Google Monster and without leaving your corporate Exchange server.) In this case, when a thread turns into a hundred "me toos," dump it. Easy.
Filtering in RSS readers, Facebook, and Twitter is harder. Certainly, Twitter is trying to help, with its new list functionality. And external tools like TweetDeck (and there are a million others, at this point, probably many I haven't heard of or looked at, hopefully some that do a more thorough job of filtering) can help you follow a conference (via hashtag), a set of users who consistently provide good information, or a particular word that interests you; you can even filter out any one word or phrase from the results. It's not perfect—you'll see junk, and you'll miss good stuff—but it's a start. Google Reader doesn't really seem to allow filtering, beyond which feeds you follow and what folders or tags you want to assign, but I feel fairly confident that it will, eventually, or some better tool will come along that does. I'll go a step further and say, actually, I'm fairly confident that there's already a tool that does this, though I admit I don't know what it is. Facebook is trying to intelligently filter for you, with its News Feed (instead of Live Feed), and it's doing a so-so job, at least for me; I still find that I see more of what interests me by following the Live Feed, turning off certain people, and skimming past anything that does not seem immediately useful, but the News Feed is not entirely useless, either.
This discussion goes beyond email, RSS, and social networking services, though: even if Google Wave supplants all of these, or if we all eventually end up only accessing the Internet through something like World of Warcraft or Second Life, instead of a browser, we're still facing a different information age than the one in which "netiquette" could save us all. As an information consumer in today's world, everyone has the responsibility to filter their own content; sometimes, yes, this means adding tools to their tools (here, I fight the meme urge). And, for the next few years, yeah, it's going to be patchy. We will all have to master the art of letting go; you will not see every message in your Twitter stream, either because you are a master filterer or because you have mastered the Zen necessary to read 20 messages here and 20 there, wherever you have time. Nor will you see every message on every mailing list, every post on every blog, etc. That's the world we live in.
What I'd like to see, instead of librarians arguing about netiquette, about listservs vs. fora, about blogs vs. Twitter, and the like, is librarians helping other librarians—and through them, all of the people we should all be helping—to get a handle on the tidal wave of information coming to all of us through all of these media every single day. Perhaps we should be building tools to do some of this filtering, even.
(If I hadn't exhausted myself, I would now be expanding this discussion to metasearch of libraries' collections and the sheer volume of material produced about pretty much every subject under the sun, nowadays. Thing is, if we can't all master this viewpoint for our own information needs, we're not going to implement it to help our users, are we?)
Labels: technology


5 Comments:
I think that's pretty interesting. I admit that I spend a lot of time practicing filtering in my own head (IE I am of the school that dips in for twenty tweets here, and five there as I have time).
I admit that the "me too" response irritates me about as much as the meme on blogs, which is why things come off my feed reader, and get muted ruthlessly on e-mail. I wish I could train my client to start recognizing those things and doing it preemptively.
OTOH, I do think that as people get more used to the medium, they should learn some of the more common standards (such as not solely posting memetic content if they want an audience, or posting more of substance in an e-mail) and that perhaps we as veteran users should be rewarding that behavior, instead of penalizing "not that" behavior.
Well said!
I agree that everyone should just accept the fact that they're going to get email that would be a waste of their time to read, skip it, and move on with life.
But, at the same time, people who use a listserv should ALL know by now not to reply to the list when you just want to email the list's sender! It's not that hard to check before you hit send. Furthermore, it's not that hard for list adminsitrators to set up the list so that the default is "reply to sender" rather than "reply to list." Yeah, it's not that hard to just ignore the messages, but it's so easy for the sender to avoid sending the messages to the whole list in the first place that it's still darn annoying when they don't.
Thank you all for the comments!
What I didn't explain, in this particular instance, is that the "me too" replies were actually worthwhile to send to the list, sort of, since any one person only gets 20 Wave invites. The hope was that others would be reading the list and give the invites to them. So their intended communication was still one-to-many, meaning, in my opinion, they did nothing really wrong (again, in this case), besides naively assuming that people would risk wasting their Wave invites (since I don't think there's a feedback mechanism for "that person has already been invited"). [There were better ways to do it, and I wish one of them would have thought to start a Google doc or something, early on.]
More generally, sure, I agree there's a balance. I don't think we should throw common sense or etiquette out the window, as individuals. Though I'm going to make rather a bold claim, here: as the number of participants in a medium increases, the probability of idiotic behavior approaches one. Rapidly. (I think I'll Twitter that. :))
As far as enforcement of norms, I'm just not convinced it's a good use of anyone's time, in part because of the Idiocy Rule, but also because we've seen, over and over, that it is useless in preventing future abuses. It just compounds the wasted time.
@Rowan: While I agree, in theory, with rewarding the positive, it's hard to reward someone holding back inane comments--because you never see them!--so you end up with a culture that punishes the bad, rather than rewarding the good. Which makes nobody happy.
@Carol: Maybe I'm being unnecessarily negative, but I've noticed that a lot of librarians are really bad at following listserv etiquette. My library school class epically failed to use our listserv right on two separate occasions. And I get a "please unsubscribe me from this list" sent out to the whole list at least a few times a week. (Perhaps my attempts to let go of that frustration have had some hand in my developing the viewpoint I'm now espousing. ;))
@coral I know how hard it is...working with students has taught me that the behaviors I'd really like to see (like neatly filled out paperwork and orderly lines) is pretty hard to reward. I'm still puzzling on how to do it.
Post a Comment
Links to this post:
Create a Link
<< Home