That's the problem, a cheap smartphone is not reliable. I've had my 2FA manually reset because of a defective smartphone twice now which took around a week each and I simply never bothered to try the 2FA system once more because is such a hassle as long as you're completely reliable on a device that, at any time point in time, is simply too fragile (gravity, fluids, and theft for example) to be classified as anything but unreliable, does not work for me and I'm sure there are others that think the same way.Wouldn't mind, there isn't a reason not to have it.A cheap smartphone isn't a hard price to pay to not have to repay hundreds in scammed repayment
I agree something needs to be done, but I'm not entirely certain forcing 2FA is the solution.
One could argue that the reason I got hacked was the lack of 2FA, but it is more likely that, on top of my status, this just made me a target. My password was unique and secure, my computer was clean and nothing else was touched. Everyone else that had their Sythe account hacked tells us the same story and none of us are really connected through any other means than Sythe. This should lead any reasonable mind to believe it's more likely a flaw in Sythe's security than all of us being a victim of any (ridiculously specific) malicious software at the same time. Be it as simple as a brute-force or something worse, it doesn't matter if this is an issue with Sythe's security it should be dealt with as such.A cheap smartphone isn't a hard price to pay to not have to repay hundreds in scammed repayment
Until now, the 2FA system has always been optional, unless you are an active staff member. Therefore, as an ex-mod, 2FA is optional and can not take away Sythe's liability towards this supposed security issue and should be investigated as such. Perhaps even in the format of a report, as we surely would do if it were anyone else were (unintentionally) causing any malicious activities.
Honestly, I am astonished by the fact that the hacking victims are forced to refund the victims without actually looking into what caused the hack and who should be held responsible. It is generally accepted that these cases are linked and should definitely be treated as such. Especially when debating liability. I know for a fact that most of the staff agrees, I know for a fact that Richard is(was?) looking into what happened in Sythe's back-end and and I also know for a fact that a captcha system was added to discourage (possibly disable) brute-forcing.
Why should we, the people, have to refund the victims if we are not at fault when, arguably, Sythe's security system, is!































































