• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle
  • Friend, you're right, I am missing your point.

    I wasn't trying to engage in a conversation with you at any point. I don't know why you keep replying.

    We seem to mostly be in alignment on the issue of liberals and Nazis not being the same. I was offering my viewpoint to the original commenter I replied to, just in the same way that you did, when you came at me with this "I'm standing right here" bullshit.

    If you're hurt because I've insulted your instance, that's tough. If you hang out with Anarchists all the time, you aren't allowed to get upset if someone calls you an Anarchist. I'm far from the only person who has pointed out the frequency of viewpoints that lack any connection to reality coming out of Hexbear. My comment was a PSA and I won't apologize for calling it out.




  • You're standing right here, on Lemmy.zip, not on your home instance, and the comment I was responding to was a response to a different Hexbear user who was literally saying that there is no difference between liberals and Nazis.

    If I meant to reply to your comment, I would have done that.

    It was incredibly jarring when I first got to Lemmy and started running into nutjobs who seem to be on some sort of crusade, spouting ideas so far out of touch that they're either straight up trolling or they are state propaganda assets from a western adversary. Sometimes when people ask where these people are coming from, I like to provide something of an orientation, as the community will never survive off of nutjobs alone.




  • It sounds like someone got ahold of a 6 year old copy of Google's risk register. Based on my reading of the article it sounds like Google has a robust process for identifying, prioritizing, and resolving risks that are identified internally. This is not only necessary for an organization their size, but is also indicative of a risk culture that incentivizes self reporting risks.

    In contrast, I'd point to an organization like Boeing, which has recently been shown to have provided incentives to the opposite effect - prioritizing throughput over safety.

    If the author had found a number of issues that were identified 6+ years ago and were still shown to be persistent within the environment, that might be some cause for alarm. But, per the reporting, it seems that when a bug, misconfiguration, or other type of risk is identified internally, Google takes steps to resolve the issue, and does so at a pace commensurate with the level of risk that the issue creates for the business.

    Bottom line, while I have no doubt that the author of this article was well-intentioned, their lack of experience in information security / risk management seems obvious, and ultimately this article poses a number of questions that are shown to have innocuous answers.