• youmaynotknow@lemmy.ml
    link
    fedilink
    arrow-up
    13
    ·
    7 months ago

    Let me see if I understand your logic. Microshit decides to push something sneakily on servers, and the OP mentions that he just found out about it, and never once does he mention that he doesn’t know what to do about it, but and you assume he doesn’t know, but and choose to blast him over your assumption.

    Did I miss something?

    • Spuddlesv2@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      7 months ago

      It wouldn’t have been installed at all if the OP did their job properly and had set the one config option. Microsoft doing shady things is hardly news. That’s why a good Windows sysadmin keeps and eye out for this sort of stuff.

      • youmaynotknow@lemmy.ml
        link
        fedilink
        arrow-up
        11
        ·
        7 months ago

        I get that, but we can’t go around assuming stuff and blasting people over assumptions. We don’t know if someone else in his team was in charge of that, and he found out while auditing the server, that’s certainly a possibility. Then there’s the fact that his post could help someone thinking about setting up a similar server rethink this and choose to move away from Microshit altogether. I agree that whomever is in charge should keep updated on information, issues and their potential solutions (I’d fire any sys admin not living by those rules, for sure). Now, if he is, in fact, responsible for that, shame on him, but he’s innocent until proven guilty.

        • Spuddlesv2@lemmy.ca
          link
          fedilink
          arrow-up
          4
          ·
          7 months ago

          The OP is re-tooting a toot of a screenshot of a tweet. My (mild) criticism isn’t aimed at OP, nor the OP of the OP, just the original Twitter OP. No one was “blasted” but even if they were, the Twitter OP is not likely to see my comments and have a bad case of the sads from it.