Cody Taylor

While no one may have a real reason to spy on you, relying solely on security through obscurity has always been a poor policy to live by. Because of this, encryption is the only real option you can trust. We teach you how to put your emails in a lockbox before sending them off to their destinations.

exmoron writes “I work at a small university (5,500 students) and am in a position to potentially influence future software purchasing decisions. I use a number of FOSS solutions at home (OpenOffice.org, Zotero, GIMP, VirtualBox). My university, on the other hand, is a Microsoft and proprietary software groupie (Vista boxes running MS Office 2007, Exchange email server, Endnote, Photoshop, Blackboard, etc.). I’d like to make an argument that going open source would save the university money and think through a gradual transition process to open source software (starting small, with something like replacing Endnote with Zotero, then MS Office with OpenOffice.org, and so on). Unfortunately, I can’t find very good information online on site licenses for proprietary software. How much does a site-license for Endnote cost? What about a site license for MS Office for 2,000 computers? In short, what’s the skinny on moving to open source? How much money could a university like mine save? Additionally, what other benefits are there to moving to open source that I could try to sell the university on? And what are the drawbacks (other than people whining about change)?”

Read more of this story at Slashdot.

Google is pretty fast-moving, as company cultures go, rolling out new products on a regular basis. And yet its popular Gmail service is only just now getting around to providing offline e-mail access, a feature that open-source Zimbra has had for nearly two years.

schneecrash writes “Submitting bug reports — and waiting for responses etc — seems to be SOP for developers and users alike, these days. Every project has some sort of bug-tracker — bugzilla, trac, mailing list, etc. E.g., we currently track 200+ external bugs across ~40 OSS projects. Half the bugs depend on something else getting fixed, first. Every bug has its own email thread, etc. Management asks ‘How we doin’ overall?,’ and suddenly everyone involved gets to work removing dried gum from the bottom of their shoe. What do Slashdotters use/recommend for centrally keeping track of all the bugs you track across all those different bugtrackers? In particular, managing communications and dependencies across bugs? So far, the best method I’ve managed to use is bunches of PostIt-notes stuck to the screen of an out-of-commission 32″ TV (glossy, non-matte screen, of course!).”

Read more of this story at Slashdot.

Here we reproduce a complaint letter sent to Sir Richard Branson, which is currently being emailed globally and is considered by many to be the world’s funniest passenger complaint letter.

Monster.com was attacked by hackers again. Monster is recommending that all users change their passwords and be on the watch for phishing emails.