sundries

[rm]

Patty is home, and it's been super New York-y already: the other people in Terminal 8 were so excited to see their loved-ones they were blocking folks from getting out; the cab said his credit card thing was broken; the sound of the heating pipes woke us up; and there was some seriously creepy bird action this morning. Thumbs up.

Zuckerberg is Time's person of the year. How pissed do you think Assange is?

Meanwhile, the US Air Force has blocked access to news sites that have published the leaks. can someone explain this to me? Is it anything other than "these secret things aren't secret anymore, but we're going to pretend they are, even if it means you're working from a deficit of what is now common information?"

Someone is stealing New York's junked appliances.

On splitting the check. I understand the complaint. I don't understand why it's necessary. I've almost NEVER run into this, though. We all figure out what we owe, chuck it in, and since I've been over the age of about 25, we've usually had too much money, not too little.

A bill has been introduced in California to add historical contributions of LGBT people to school textbooks. A similar legislation passed four years ago, but was vetoed by the governor.

The academics I know keep posting this, but I still love it every time I see it: The Snake Fight Portion of Your Thesis Defense.

Comments

[wcg.livejournal.com]

About the Air Force blocking news sites, I suspect this is a combination of what I call "security weenie mentality" and the IT folks wanting to cover their asses. If classified information ends up on an unclassified machine, regardless of the source, DoD policy requires that the machine has to be taken offline and purged. (Typically a hard drive wipe and clean reinstall of the OS.) In this case I think the Air Force is being overly zealous, since the rest of DoD is content with the all-hands warning that went out.