Skip to main content

The obligation to BCC


Today I got a job-related rejection letter, delivered enmass to 151 candidates. I know it was 151 because the sender hit CC rather than BCC, so all of the recipients know. Furthermore, all of the recipients know who else was competing for the job, can look at their department profiles, and likely their CVs. For private individuals, academics tend to have a lot of Web presence, largely due to university/department websites. To a large extent, that's a good thing, but when combined with a leak like this one, that increased Web presence costs a good bit more privacy. Now, there are 151 candidates who get to take a peek at their competition, maybe stalk them on "the Facebook," maybe judge themselves and each other more harshly for it. At the same time, it is not unusual for departments to announce their new hires, so everyone also knows who got the job, enabling further judgement/comparison/stalking.

Situations like this really highlight how many informational traces we can leave while conducting what we could reasonably think of as our own business (and no one else's). One might think that respecting that sense of privacy would be a kind of professional ethic. Certainly, the system of recommendation letters, transcript deliveries, and application dossiers mean that there are a lot of individuals who may be clued in to the fact that a person is looking for a job. Yet, when it's not our business, we don't fish for more, put the clues together, and seek out further information. To so is considered a little creepy, right?


In general, being on the academic job market provides a window into a variety of university cultures and group norms. Unfortunately, one often learns a great deal about an institution's relationship to technology (or lack thereof). There is something about having your login credentials emailed to you in plaintext that just makes you feel...less than safe, especially considering the kinds of information provided to potential employers. Nevertheless, it's not neglect. I'm sure the folks "responsible" are really not aware of it as a problem.

Comments

Popular posts from this blog

Justifications for Intellectual Property Part 1: Utilitarianism

There is no way this tutorial series would be complete without some discussion of justifications for intellectual property. While not necessarily a matter of law, some knowledge of the philosophical foundations will provide a better sense of the values at stake in intellectual property debates. Notice, for instance, that the tutorials on fair use were punctuated with appeals to values, social goods, and individual rights. Without an understanding of the moral and political framework against which the law stands, one can very easily find oneself in a stalemate, with one value pitted against another and no way of deciding which should prevail. To understand the jurisprudence around intellectual property rights, one has to have some idea of the justifying theories to which attorneys and judges appeal in their arguments and decisions. So, without further ado, let's get to the tutorial. There are three main ways of justifying intellectual property rights: the Utilitarian theory, th

History and Identity

Yesterday the European Court of Justice issued an important ruling that has the tech policy world buzzing about privacy, search engines and personal history. In short, the court ruled that the EU Data Protection Directive gives a person the right to demand that old information be purged from search results. The particular case involves an attorney seeking removal of links to announcements about a real-estate auction connected with a debt settlement in 1998. While the ECJ made a number of interesting moves in the case (including a welcome argument that the distinction between data processors and data controllers does not make as much sense today as it did in 1995 when the Directive went into effect), the big consequence everyone is talking is the right to be forgotten. The long memory of the Internet is a feature it's hard not to love and fear at the same time. Whether you have something to hide or not, if it's on the Internet, it stays on the Internet (most of the time, at l

RPG Systems: An Analogy with UI Design

The current game in our weekly role-playing group is Deadlands. The previous game was Shadowrun. Both rule systems lie closer to the “chunky” side of the spectrum. Shadowrun has a particular reputation for its complex and somewhat cumbersome rules, and while Deadlands has less overall complexity, the system has a degree of granularity that interrupts play more often than it enhances narration. I enjoy role-playing games because I like participating in a good story. The rules system provides a set of constraints for the characters, the setting, and the conflicts. They help give the narrative structure, a background against which the story will take place. Too few rules, and telling an interesting and well-developed story becomes difficult. Too many rules tend to get in the way of individual scenes or events. With the right balance, it’s possible for the game master, usually me, to be sufficiently fluent in the rules system to resolve any conflict without extended consultation of on