A former Twitter employee, Gary Rooney, won about $600,000 for unfair dismissal after Twitter assumed he resigned by not responding to Elon Musk’s “hardcore” work email.

The case highlighted the importance of clear communication between employers and employees, especially regarding significant changes in employment terms.

Rooney’s private Slack messages, where he discussed leaving, were used as evidence by Twitter, underscoring that internal communication on platforms like Slack is not always private and can be used in legal disputes.

  • sylver_dragon@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    1
    ·
    9 days ago

    When I worked as a US FedGov contractor, I was greeted with a long warning banner every time I logged into my computer. The tl;dr version of it is “fuck your privacy”. Being that I was part of cybersecurity for the site I was working at, I was one of the people doing the fucking. While we didn’t read everything from everyone all the time, we were logging it and could pull it up, if we were performing an investigation. We also had some automated stuff scanning for patterns and keywords on a regular basis, which could trigger an investigation.

    While I’m no longer in the FedGov space (thank the gods), I still assume that everything I do on my work system or with work accounts is being logged. Also, I’m still working in cybersecurity and am often still the one doing the privacy fucking. Yes, everything is being logged. We may not look at it today, we may not look at it tomorrow. But, when HR and Legal ask us about a user’s activity, we can usually be pretty detailed. Act accordingly.

    • CosmicTurtle0@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      9 days ago

      My company is better than most I’ve worked for. They tell you, upfront, anything on their equipment can be monitored for any reason with no warning.

      But then, as part of the HR and acceptable use policy, no one will monitor your activities without just cause and investigation. Meaning in practice, “We’re not going to look over your shoulder while you watch YouTube videos but if we notice you’re watching a lot of or you start visiting porn sites, we’re going to start monitoring you.”

      Now all that said, I still assume that my company knows every key I type on their laptop.

      • lightnsfw@reddthat.com
        link
        fedilink
        arrow-up
        3
        ·
        9 days ago

        Mines the same way. It’s actually kind of difficult to get approval to monitor someone. Has to be approved by two VPs.

      • sylver_dragon@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        8 days ago

        I would assume they have some basic stuff running 24x7. I can’t imagine a network which doesn’t have Endpoint Detection and Response (EDR) running 24x7 these days. There’s also things like firewall logs, which are almost certainly being captured (or at least netflow). Stuff like screen recording and mouse monitoring is probably saved for extreme cases. That said, my own experience has been pretty close to:

        We’re not going to look over your shoulder while you watch YouTube videos but if we notice you’re watching a lot of or you start visiting porn sites, we’re going to start monitoring you.

        Quite frankly, no one’s got time for that shit. I work at an organization with a bit north of 25,000 employees, and we have less than a dozen security analysts. While I could run a search against our firewall logs and see evidence of folks dicking around. I have much better things to do, like running down abnormal processes and writing up reports on users who got their systems infected while dicking around. And that’s really the way it comes to our attention, most of the time. Someone is out trying to download movies or software on their work laptop (you’d think people would know better…) and they pickup malware. We get an alert and start investigating. While trying to determine the source, we pull browser history and see the user out on “SketchyMovieSite[.]xyz”. And then their dicking around becomes our problem, mostly because the site had a malicious redirect, which is where the infection came from.

        So ya, they may not be looking, but I’d always bet they are recording. Logging isn’t useful if it isn’t recording at the time of the compromise.