IMO, this is *not* a good thing.

This consumed a *huge* amount of energy of the security community, just from my (very distant) perspective. That energy wasn't being spent idly on random unimportant things. There isn't some boundless supply of energy on short notice either.

The direct consequence of the publicity has been to prioritize these "issues" *above* other security work that will not get done or get done later.

While I *do* want these issues addressed, they were not more important than the security work displaced. =[

Anyways, my 2 cents.

I should further clarify -- security isn't my day job. Any of my work disrupted, who knows, maybe it was less important. Definitely not security work.

But I got to watch a bunch of full-time security folks deluged by this, and the above is my view on the impact it had there.

Ok, another PS... sorry...

But I want to clarify, I am 100% happy about the research, and 100% happy about the disclosure. Big fan of disclosure here.

It's the active and misleading publicity that I take issue with. That's what (IMO) caused a harmful priority inversion.

@chandlerc1024 The Twitter compiler is affected too 🤡

x.com/lbherrera_/sta…