Comment on Disney hack leads to 1.2TB of Slack communications leaked online

• cmhe@lemmy.world ⁨2⁩ ⁨months⁩ ago

  Wgy would disney demand that?

  Why would they choose slack if they want to host, maintain and be responsible for the internal chat themselves?

  They choose slack because they do it for them so that they don’t have to do it themselves. That is the selling point for them.

  source

  • towerful@programming.dev ⁨2⁩ ⁨months⁩ ago

    They can still have support contracts and SLA etc from slack.
    It’s just that the servers slack runs on are on-prem and completely controlled by the business buying into the self hosted licence.
    The benefits should be tighter security (say, can only be accessed via VPN), and for many many MAU probably lower costs. Chances are, Disney already has datacenter ops and hardware contracts.

    And why choose slack? For quite a while, it was extremely common for developers (maybe even industry standard?). It had loads of features very small features of internal chat programs. And it’s easy to build extensions and integrations for.

    I’m not saying that Disney is running on-prem slack, but I wouldn’t be surprised if they were

    source
  • bane_killgrind@lemmy.ml ⁨2⁩ ⁨months⁩ ago

    Ostensibly better opsec

    source
• femtech@midwest.social ⁨2⁩ ⁨months⁩ ago

  [deleted]

  source

  • douglasg14b@lemmy.world ⁨2⁩ ⁨months⁩ ago

    Your logic isn’t making sense.

    The code would end up somewhere for others to use…? What?

    One-off products or beta offerings are often kept private, sometimes indefinitely.

    source

    • homesnatch@lemm.ee ⁨2⁩ ⁨months⁩ ago

      In this case, Disney is using Slack Cloud-hosted for internal communication, but I can definitely understand people interpreting it differently.

      source
  • anivia@lemmy.ml ⁨2⁩ ⁨months⁩ ago

    Providing Disney with an internally hostable version of Slack doesn’t require giving them the code. They can just ship them compiled binaries

    source