A Second Tea Breach Reveals Users’ DMs About Abortions and Cheating

Comments

• limer@lemmy.ml ⁨6⁩ ⁨hours⁩ ago

  It is too bad all these people trusted a bad company which cared little about them or their privacy.

  source

  • jacksilver@lemmy.world ⁨2⁩ ⁨hours⁩ ago

    It has nothing to do with the company, it’s an issue about privacy and not sharing personal information so freely.

    I mean the company was incompetent, but the primary issue is privacy.

    source

    • limer@lemmy.ml ⁨2⁩ ⁨hours⁩ ago

      I design systems similar to this; in my mindset the competency and privacy are the same.

      There is simply no way anyone competent or knowledgeable would have made this series of mistakes in good faith. And it’s very hard for someone not knowledgeable about the tech to understand the magnitude.

      It’s rather like designing and selling car with bad breaks, and your car gets into an accident which could have been avoided had the breaks worked. But nobody could test the breaks fully?

      source

      • -> View More Comments
  • anyhow2503@lemmy.world ⁨4⁩ ⁨hours⁩ ago

    This isn’t an issue if you give private information to “good” companies since they don’t suffer data breaches. Make sure to check their website for the authentic “good company” seal.

    source

    • limer@lemmy.ml ⁨4⁩ ⁨hours⁩ ago

      Indeed, how can anyone know?

      I think failures like this will be readily apparent, within months after launch, to technically minded people only. But only if people have summaries in their news feeds or know how to research the opinions of others…

      Perhaps non technical people should wait at least a year or two of before trying a new service? By then the worst of them will have crashed or be found out.

      This will not be the last time it happens. With llm coding, I think there will be dozens similar to this in a few years

      source