seemslegit

Key quote:

>In addition, the team is working with renowned art historian and curator Dr. Lowery Stokes Sims, who is providing additional mentorship and professional development.

In art as in politics - nothing says grassroots like the additional mentorship and professional development by a renowned establishment member.

I recently implemented my own npm vulnerability audit tool for the CIO department of a major org - it just adds 'vulnerability' in red next to any npm-based project in their spreadsheet.

That's such a presumptuous title, the author does not know what other powerful tools my toolbox lacks.

Practically speaking, that's the only approach that can.

Although it's often hard to tell, most software developers aspire to being treated like professionals rather than specialized serfs, and part of being a professional is accepting responsibility for your work.

Of course it doesn't preclude holding their employers responsible as well.

This is a losing proposition that will only lend credence to the inherently violent opt-out approach to data collection.

Instead how about a do-not-hire-or-collaborate-with registry of the individual contributors participating in projects that employ those tactics and see how they like trying to opt out of it.

Nah that was the old MS, new MS just replaces own with rent.

C#, F#, Typescript, JavaScript via npm

And the next language to become unusable without a microsoft-controlled ecosystem is...

Loving the "are we ok with this ?" take - as if anyone cares.

It's not affectionate, it's condescending - much like 'geek' when used unironically and not by geeks to refer to themselves.

Boffins ? I haven't realized theregister employs such classy people as Thomas Claburn.

Username checks out.

What are the odds that the chips that don't feature AMT/ME don't have it physically as opposed to it just being crippled in firmware ? In which case if one is worried about government backdoors this should alleviate exactly zero concerns.