• @[email protected]
    link
    fedilink
    English
    321 day ago

    Not to excuse them, but this is from 2019. Yes, that behavior was so outrageous at the time, but hopefully it is no longer happening

    • @[email protected]
      link
      fedilink
      English
      22
      edit-2
      23 hours ago

      Also, nobody reads the actual posts, just the headlines. They were accidentally stored in logs:

      As part of a security review in 2019, we found that a subset of FB users’ passwords were temporarily logged in a readable format within our internal data systems,

      which is something I’ve seen at other companies too. For example, if you have error logging that logs the entire HTTP request when an error happens, but forget to filter out sensitive fields.

      • @[email protected]
        link
        fedilink
        English
        421 hours ago

        I worked at a company that handled sensitive data and we always had to pay special attention to logs in code reviews to make sure someone wasn’t inadvertently logging something that could potentially be private.

        • @[email protected]
          link
          fedilink
          English
          421 hours ago

          There’s sometimes cases people don’t think of ahead of time. For example if you log stack traces, they may contain details about the arguments passed to functions.

    • Obinice
      link
      fedilink
      English
      1023 hours ago

      2019 isn’t some ancient far away time though, it’s just a few years ago. If Facebook were doing stuff like this then, think who else is still doing it.

    • @[email protected]
      link
      fedilink
      English
      51 day ago

      I’m sure we can just trust that it’s better now. The small dent fee that falls under the category of "write-off’ on Meta’s budget probably really straightened up their behavior…