Privacy and One Post Wonder 9/25 '14
I don't like to spend my post for the day talking about the site itself, which sort of misses the point. But privacy is exceedingly important, and today I spoke cavalierly about it in a way that rebounded on me. As well it should have.
Other sites have been through some nasty issues around privacy lately. I am not bulletproof and need to take it at least as seriously. Especially with an audience of people who take it very seriously.
So what happened today? Nothing to do with the code or the privacy of your posts, I'm relieved to say. Just a dumb, dumb personal screwup in which I casually warned a friend (hopefully still a friend) that they had posted publicly. Because I wasn't paying enough attention to see that they hadn't.
"Tom that is totally ridiculous, you built this site! You know how it works, you coded it!" Yes it is totally ridiculous and I have no adequate explanation for my behavior. My inadequate explanation, if you care to hear it, is that I was rushing around doing way too damn much this evening and didn't think through what I was doing. I was not in programmer mode, I was in friend mode, and I was doing a crappy job of it.
However, learning from my dipshit mistakes— and owning my own frailties— is important. I'm thinking it's not enough to show a "this post is public" warning only when someone clicks reply.
I think there should be a lock icon visible to everyone who can read the post. If it ain't there, it's public. No ambiguity.
Although, obviously, it should not offer any details about exactly who is allowed to read it (except to the author), everyone reading a post should be able to tell instantly if it is public or not.
I will be working on this promptly. I will also be reviewing the steps I'm taking to secure the server against attack. If the server itself is compromised, everything else is a moot point. We do not actually know if this has ever happened to other social networks. We can only take their word for it.
This experience brought me up short and made me realize that while we haven't had an actual security breach yet, we will if I don't treat privacy as job one. I will be giving it an appropriate level of attention in future.
I also know never to type anything you wouldn't want to have your mom hear when read aloud as evidence in a courtroom... especially typing said things into a site that's still in beta. ;)
Loose lips sink ships, etc.
In other news, would it make sense to make an account called 'News' or 'Admin' or 'HolyCrap' that everyone is automatically subscribed to, so users can get info about site updates, etc. without you spending your one post?
Sounds like an honest mistake. Telling someone "your post is public" when it's not is a _lot_ less damaging than telling someone their post is private when it isn't. (Or at least that's how I'm reading it, feel free to correct me.)