That's debatable. Every best-practice arose to solve a real problem within a context, and is only "best" if that context applies.
If you apply best-practices without a regard for that context, you end up with a dull, cargo-culted checklist of must-haves to beat people over the head with, without deriving any true human value.
The compiler of this artifact is making a judgement call[0] of what best practices apply somewhat universally (to every "decent website"). I haven't yet been convinced of their standing or judgement to make that decision.
[0]: Charitably, I'm assuming they have, rather than, e.g. delegating the judgement to an opaque model's weights.
Some requirements have force of law, e.g. complying with GPC in California or Colorado. So do accessibility features in many jurisdictions. Some are just basic decency, like providing alt txt for images.
The approach of marking items as required/recommended/optional addresses your concern. Too bad this specific checklist is LLM-generated.
I saw this posted on LinkedIn[1], where the author wrote:
> I got tired of pointing at six different sources to back a single recommendation. WHATWG for HTML. WCAG for accessibility. IETF for headers. schema.org for structured data. MDN, web.dev, Google Search Central for everything else.
> There was no single, opinionated, platform-agnostic spec for "what does a modern website actually need to do?"
Probably a repo for the Muslim affinity group within GitHub. You'll also see repos for the blacktocats, octoqueer, octogatos, christian-hubbers. Everything in GitHub has a repo.
Large organisations have advocacy, support and friendship groups for many underrepresented or protected groups, such as those for religions, mental health issues, physical disabilities etc. I imagine this is simply one of those internal group's organisational repos.
Just an opinion. There is more AC in Asia and South Asia and more heat waves related deaths.
You number, approximately right but means nothing and the link AC => Less deaths by Heat Wave isn't supported by any fact.
Others factors like percent of the population > 70y, difference between usual temp / mean temperature in an heat wave and access to fresh and clean water should be more correlated than "AC implantation per hundred inhab".
The compute power needed use to be of the order of 5s per password try.
So it effectively mitigate brute force back them, you need a absurd compute power to crack them.
Moore law did its thing, now you can do it with a lot less computer power.
> Moore law did its thing, now you can do it with a lot less computer power.
s/power/time/ maybe? Or on second thought: so energy-efficicient that it actually uses less power in the same-or-shorter time… which brings me back to "less compute power".
reply