View Single Post
Old 06-03-2023, 05:33 PM   #68
haertig
Wizard
haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.
 
Posts: 1,912
Karma: 32620480
Join Date: Sep 2017
Device: PW3, Galaxy Tab A9+, Moto G7
Quote:
Originally Posted by ZodWallop View Post
Amazon bought Ring in 2018, new weaknesses existed and did not correct them until 2019.
That's the thing when we blindly trust the news media. Amazon could have bought Ring on Dec 31, 2018 and corrected things one day later, on Jan 1, 2019. The media doesn't specify. They just say "2018" and "2019". So we could be talking a two year delay, or we could be talking a 1 day delay. Adding two factor authentication for a huge user base is not something that can be done in an hour. You've got to write the code - for different applications: Android, iOS, Web browsers, etc - you've got to test the code - you've got to do end-user acceptance testing - you've got to do regression testing to make sure you didn't break some previously existing feature - you've got to hold code quality reviews - you've got to actually deploy the code updates to millions of users - you've got to prepare a large scale rollback if things go awry in the deployment (and hope you never have to fall back to that!) "The code" is not insignificant. It's not just a one-liner in an app. You've got to design databases to track 2FA data for every single account, you have to test the speed and the scalability of your database design, you've got to coordinate multiple, redundant databases that are geographically dispersed to keep your app's uptime near 100% - you've got to take privacy into account, which usually means encrypting your database which definitely complicates things, but is required anyway - this is not trivial stuff as some seem to think. It does take a while when you are handed a pile of crap and told to turn it into a pile of gold. I've been there, done that, for software like this. Luckily I am retired now and don't have to put up with it, or the judgments of how things were handled, anymore.

Again, I am not pro-Amazon on this. But I am at least willing to look at "the other side of the story". "From 2018 to 2019" is not necessarily an unreasonably long timeframe depending on what had to be done, and the specific dates in each year that we are talking about.

I will freely admit that I often times miss the bandwagon, because I am loath to jump on it after the first reports that it's heading down the road. I usually sit back for a bit and try to determine if there is a different, unreported side, before I rush to judgement. Even when the popular thing is to rush to judgement. Which, I admit, tends to make my views unpopular. You can easily see this if you've read my posts here (and the responses to them) over the years. I often appear as the devil's advocate in presenting "the other side". The mods hate me for this, and so do many other users I'm sure. And like others here, I often fail in my attempts to see both sides, and I rush to judgement or respond based on emotion or bias rather than logic. I wish that part wasn't true, but it is.
haertig is offline   Reply With Quote