Oh great Fedibrain, I have a burning question!

I would like to cut through all of the SEO garbage in search about effective workplace and safety communication. I'm looking for teachable models that ensure conversations result in a standardized approach to:

• Raising issues
• Responding to concerns
• Getting attention or focus on hazards
• Ensuring everyone understands what those mean
• Ensuring everyone understands the appropriate response
• Knowing when an issue is complete, and understanding indicators that the issue is closed.

I've seen this in different locations. The US Army has a pedagogy around this. Many organizations that do safety inspections have an entire culture around this (SGS, for example). Japan has models of some of this behavior, where in many places a person points and says, in a specific manner, what to watch out for.

I'm looking for short classes on this, or books people can reference, something I can suggest to some management folks.

If you live in Colorado, you may want to get on the phone directly to your legislator about SB 26-051 which is going to force age verification into every aspect of an OS.

#HardenedBSD

After looking at open source api docs last night, do you know what would be really helpful, especially with the Linux focused ones (because most of those assume dependency on search)?

If the people writing the API docs would stop using common words for modules, calls, etc. Even better is if the docs for the API entry are exact matches for what is written in the code.

A module called "stasis" is a terrible name. Worse is naming something m.stasis but documenting it in the API docs as Stasis. Searching for "Stasis" or other common dictionary words is a bad idea. Not much better than naming calls and modules: a, the, and, so, huh, and that.

Maybe I should write a worst practices example app for April 1.

Any thoughts on alternatives to DUO for heterogeneous self-hosted MFA managed systems? Would like to explore something NOT integrating with Persona.

https://infosec.exchange/@tinker/116142810017259522

Oh, for fuck's sake, why the hell are SSL certs being issued now for only 200 days instead of a year?

Why not make it 199 days? 32 days? 1.3 days? 4.32 hours?

The last two weeks of support from a well known storage provider has been abysmal. This prompted me to go through our reports for the last year. Across all of them, all support has been awful, as in catastrophically bad.

I can't think of a single product or service vendor that didn't cause an outage for us in the last year, bad.

These aren't just the low end contracts or low end vendors. This is the major names. Everything about them has been decoupled from the feedback loops which allowed the support organizations to thrive. Every single group now has anonymized support teams where we rarely see the same person twice for subject matter where staff is not easy to replace. Most of our tickets bounce through multiple queues and we are regularly lied to about the status of work or who is doing the work, or if any work was actually being done. The true subject matter experts are often one or two people, if the org is lucky to have even those staff left.

Everything about the support management process has become noticeably worse. This adds pressure on small teams like mine, where we are already stretched and cannot continue to compensate for the lack of engineering level support for complicated products that no longer have accurate, complete or updated product or service documentation.

No wonder people are either leaving IT, or refusing to major in IT related studies. This field is being killed off.