Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:and for students that don't want to be tracked? (Score 1) 168

If a person discusses their own medical history with someone else, HIPAA does not apply. If they talk about it in public and someone overhears it and somehow uses that information, including a marketer, somehow, HIPAA has nothing to do with that.

Now, there may be an expectation of a certain amount of privacy when discussing something over email, but if that information is somehow obtained -- even by a breach of the email servers, and assuming neither server/individual is a hospital/doctor/insurer/etc or an employee of such -- HIPAA does not somehow magically apply. Just because it is medical information, it is not immediately protected by HIPAA.

Censorship

Joining Lavabit Et Al, Groklaw Shuts Down Because of NSA Dragnet 986

An anonymous reader was the first to write with news that Groklaw is shutting down: "There is now no shield from forced exposure. Nothing in that parenthetical thought list is terrorism-related, but no one can feel protected enough from forced exposure any more to say anything the least bit like that to anyone in an email, particularly from the U.S. out or to the U.S. in, but really anywhere. You don't expect a stranger to read your private communications to a friend. And once you know they can, what is there to say? Constricted and distracted. That's it exactly. That's how I feel. So. There we are. The foundation of Groklaw is over. I can't do Groklaw without your input. I was never exaggerating about that when we won awards. It really was a collaborative effort, and there is now no private way, evidently, to collaborate." Why it's a big deal.
Communications

Ask Slashdot: Name Conflicts In Automatically Generated Email Addresses? 383

New submitter matteocorti writes "I work at medium-sized university and we are considering reducing the number of domains used for email addresses (now around 350): the goal is to have all the 30K personal addresses in a single domain. This will increase the clashes for the local part of the address for people with the same first and last name (1.6%). We are considering several options: one of them is to use 'username@domain.tld' and the other is to use 'first.last@domain.tld.' The first case will avoid any conflict in the addresses (usernames are unique) but the second is fancier. Which approach does your organization use? How are name conflicts (homonyms) solved? Manually or automatically (e.g., by adding a number)?"

Comment Re:Which holiday? (Score 1) 304

I say Happy Holidays if I want someone to have happy holidays. I say Merry Christmas if I want them to have a Merry Christmas and then contract AIDS while being raped by rabid gorillas on New Years Day, which happens to be another upcoming holiday... I mean New Years, not Gorilla Rape Day: that's no fun at all.

Slashdot Top Deals

You knew the job was dangerous when you took it, Fred. -- Superchicken

Working...