5 ms·
> Wyze blamed "a third-party caching client library that was recently integrated into our system" for the trouble. Yes, of course. Blame a third party library
by gerwim 3y ago
> Wyze blamed "a third-party caching client library that was recently integrated into our system" for the trouble.
Yes, of course. Blame a third party library which was probably created by an open source maintainer instead of testing your own systems.
- summarity 3y agoAlso "was recently integrated" - by ... magic?
- _obviously 3y agoOf course, the reason this keeps happening is the infrastructure is designed to let it happen in certain cases. Notice how they explicitly say, they need to fix it in the front end. They can't fix it in the backend because that would break eavesdropping.
- cromka 3y agoThat’s a bit tinfoily take
- deleted 3y ago[deleted]