You are viewing a single comment's thread.

view the rest of the comments →

PuttItOut ago

I see both sides. But from Voat's side I will never transfer production data to a public testing environment because this is a potential security issue. Say for example there was a bug in anon logic and the testing site was populated with prod data... well you see the issue. What if PM's were exposed through a bug?

Right now our unit test suite populates known data to test against and we will continue to expand this. If we discover a production issue that arises from data we will populate data to mirror and reproduce this in our unit test suite.

We've lost out on some big help offers because we were unwilling to expose data (from our determination we couldn't even anonymize it enough to prevent identification) so live data is out. It's just too much of a risk and I'd rather error on having a bug that we didn't trap than exposing user data.

10198666? ago

I'd rather error on having a bug that we didn't trap than exposing user data.

"* @Genghis_Khan made me fix this.".

Concerning the actual content of your comment: Right on!

PuttItOut ago

You see this is a programming issue. Programmers will err on this 9 / 10 times because it's just a subconscious thing.

I'm sticking with this theory

10198791? ago

Seems legit.