Awesome! Thanks! I was initially sure the pedant was right, but my grammarly "research" was hasty and misapplied, and I thought I had learned a new thing I was doing wrong. I do a lot of those...
s38b35M5
Going to check out rethink now, Thx for the name drop!
I can't say with a straight face that I didn't see this coming.
We see it over and over. When consequences for malfeasance are barely noticeable compared to profits, there is no incentive to comply with laws. Just pay the tiny fine is our lawyers don't exhaust them first.
BTW, some mobile apps (I use Voyager) can retrieve the title for you in the new post submission UI.
This is why we need to ask the good questions, people. Good post; good result!
I never told anyone else the URL so no one will find it.
Who wants to tell them about DNS records and web crawlers?
My past employers have said the same, until I showed them they were already using apache, nginx, postgresql, MariaDB, and OpenWRT among other things.
A lot of shops think that using proprietary tools means they can demand fixes for critical vulnerabilities, but in my experience, even proprietary dev teams just reply that the code maintainers are aware and working on a fix.
Apache vuln? Here's the link to their acknowledgment of that CVE and exactly what modules are affected.
That may show that the flaw is in an unused module, like node.js, but even when it is applicable, they just wait for the code maintainers to address it. They take no responsibility themselves.
This reminds me of "Nyet," cat. (Not sure why, since their coloring is very different)