Follow
ひげ
@Svantovit apparently it wasn't a discord hack necessarily but it was a zendesk hack. it seems like zendesk was keeping them and not discord. pretty big fuck up.
>"Much safer to occasionally fuck up catastrophically..."
Well, humans are used to occasional catastrophes, I suppose. Even though things are never the same afterwards...
Well, humans are used to occasional catastrophes, I suppose. Even though things are never the same afterwards...
@apropos
It's actually even more retarded than not wanting to do it in house, most would opt to have that sort of access to your info to resell it.
The reason they don't is that when the breech inevitably happens they'll be accused of not using "industry standards" and their insurance won't pay out and leave the company on the hook to pay damages. This is true even if the security in place was better.
They would rather centralize everything and make one big target and ensure that everyone is fucked when the inevitable happens.
@Svantovit @beardalaxy
It's actually even more retarded than not wanting to do it in house, most would opt to have that sort of access to your info to resell it.
The reason they don't is that when the breech inevitably happens they'll be accused of not using "industry standards" and their insurance won't pay out and leave the company on the hook to pay damages. This is true even if the security in place was better.
They would rather centralize everything and make one big target and ensure that everyone is fucked when the inevitable happens.
@Svantovit @beardalaxy
I would rather them print out all of our IDs, scan them directly to an offline computer running Windows Vista, and leave them there ad aeternum.
Much safer to occasionally fuck up catastrophically while being able to say it's some other guy's fault!