Comment

Comment by twisteriffic

> The incident was caused by a third-party caching client library that was recently integrated into our system. This client library received unprecedented load conditions caused by devices coming back online all at once. As a result of increased demand, it mixed up device ID and user ID mapping and connected some data to incorrect accounts.

That seems like enough of a line of bullshit to steer me away from ever using wyze.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton