• funkyb@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    that’s both unreasonable and not the right way to approach this. Your assumption is that if you knew the names of all possible processes that you could then be in a position to make better decisions. the problem is names are useless - it’s trivial for software to run under different names, so believing names can help you somehow is a waste of time.

    • Melody Fwygon@lemmy.one
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      This is blatantly false. Name and fucking shame each variety of software. These cockroaches can’t stand the light of public attention. The more people who know how to spot and identify malicious and suspicious boss-ware behavior, the better. It protects the user to know that the software exists; as they can better be prepared to combat and deter abuses of this software by unprofessional and shitty bosses.

      No; it isn’t going to be foolproof. That’s not the intent here. The intent is for everyone to be able to name, shame, and identify when software that their employer is deploying is going to be behaving in a manner that blatantly violates their rights to privacy in a non-constructive way that threatens them.

      • jet@hackertalks.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Just assume anything that work controls is monitored by your work. And act accordingly.

        Don’t install work software on personal devices. And you’ll be fine