3 ms·
The fix itself depends on what the problem is - clearly they went for a “disable server side” route, but I’m sure they also tried to work out if they could filt
by olliej 8y ago
The fix itself depends on what the problem is - clearly they went for a “disable server side” route, but I’m sure they also tried to work out if they could filter on the server side. My guess is they can’t because the “call accepted” response is probably in the encrypted data stream.
Rolling a system update is also not immediate (eg you need to be sure that you don’t result in user flows resulting in no audio), hence the focus on server side fixes (that lead to today’s “kill server side”) fix.
But also “a week to fix” depends - it’s a week from the report, at which point it needs to be screened. So let’s say a day to get to an actual engineer - it may take longer to get appropriate security keywords attached - then the engineer would need to actually read it, which depends on what their current workload is, where they are in their release schedule, etc.
It’s not trivial - all big companies get thousands of big reports a day, and they just take time to get to the right place.
I agree with what other have said (telling a consumer to get an ADC account is clearly suboptimal). But in general the path from consumer to security big is challenging for everyone.