Re:PyCon Code of Conduct changed to avoid public shaming
by freehunter on Thursday March 21, 2013 @12:46PM
(#5416568)
People use POP email at work all the time. I can see their plaintext passwords coming through the network monitor (which it's my job to review), and I've seen some patently offensive passwords being used. This brings up two of your points: First, I ignore the fact that I can see their username and password. The responsible thing to do is to completely forget that you can see it. I have no business with their login information. I'm completely aware that the only thing I can do with this information will cause damage to myself and to the person who unwittingly gave me this information. Secondly, I ignore the words on the screen. Because it's not something that was designed for me to see in the first place.
Re:PyCon Code of Conduct changed to avoid public shaming
by rbanffy on Thursday March 21, 2013 @01:39PM
(#5417194)
Shouldn't you advise them to use POP over SSL?
Re:PyCon Code of Conduct changed to avoid public shaming
by freehunter on Thursday March 21, 2013 @01:55PM
(#5417369)
We can advise them to use whatever we want, the trick is getting them to listen. Our corporate email disallows POP, but we aren't in the business of blocking their personal email on our non-secure network.
Admins has the same problems. A co-worker ask them for help fixing their emails, and the content of those email are just there. How can they not see the conversation about sexual diseases being present in the inbox. And from there to complain on twitter about it is just a small step.
Polite behavior is to sometimes not look/listen/read even if its being done right in front of you. At least one should have the decency of not go out and post it on twitter, even if one is "offended" by what you saw/heard.