bm5k

When it's not opt-in, yes. As developers, we should know better.

FTA "the 1Password browser extension protects you from a more typical malware attack of pasteboard/clipboard sniffers."

Clearly, someone at agile bits has given thought to defending against a compromised machine. Therefore, I don't see how you can justify not obfuscating data sent over lo0. I also fail to see how obfuscating the data sent over lo0 would "have unpleasant side effects that risk user data in other ways."

> Before running your test suite and checking everything is fine, the first thing you do is probably to look for the changelogs of updated gems.

Uh, no, the first thing you do is run the test suite.

The first thing anyone should do when booting an OS X box for the first time is change this (IMO stupid) keyboard shortcut.

That’s kind of my point. The original sender compromised the info.

Social security numbers shouldn’t be emailed in the first place. That data was insecure from the moment the send button was clicked.

Publishing it _again_ is only marginally stupider than sending it in the first place.

I'd never heard of pgcommander, thanks!

Other than the fact that highrise is effectively abandonware?