Matt Cowley

> * https://github.com/ossf/great-mfa-project Heh looks like Node.js was meant to be part of that: https://github.com/nodejs/node/issues/41126

https://github.com/orgs/nodejs/people?query=two-factor%3Ainsecure will show a list for org owners.

> > https://github.com/orgs/nodejs/people?query=two-factor%3Ainsecure will show a list for org owners. > > The filter two-factor:insecure / two-factor:secure doesn't seem to be working. Unless I'm mistaken, you're not an owner of...

If someone outside the org works on this, one of us will still need to work with @kyliewd to get a post made on the account pointing folks to our...

I'm going to mark this as on-hold for now pending discussions in https://github.com/nodejs/admin/issues/977 and seeing what comes out of it in terms of the project's social media accounts going forward.

Really the pro is that it'd be typed correctly out of the box -- `oauth2` is untyped at present, and `createToken` within simple-oauth2 does not return the same type as...

What do we actually need nodevu's additional support data for? I am very much in favor of just relying on our our dist file with the LTS flag it has?

Yeh, all that date logic is what is causing us issues -- we can't just assume that because we've hit a given date that the release timeline has, that existing...

I haven't looked at whether this logic lies in our code or nodevu, but wherever we're determining support status, we need to be comparing the schedule date to the most...

Sorry, yes, EOL would still want to use current date for the comparison, but LTS (which is what I was referring to in the context of this issue) should check...