3 ms·
> It’s interesting to note that they don’t say when they’ll finally remove it. It's right at the start of the detailed timeline section: "While we will enforc
by iudqnolq 5y ago
> It’s interesting to note that they don’t say when they’ll finally remove it.
It's right at the start of the detailed timeline section:
"While we will enforce a minimum of TLS 1.2 beginning October 4, 2021, we will also take steps to alert affected users to this change ahead of the deprecation."
- kevincox 5y agoIt is a bit odd that it isn't in the timeline though. I also got to the end of the timeline and though for a second "what about the full disable" before reading the start of the article again and finding it.
- chrismorgan 5y agoFailing to notice that (twice, even, apparently!) was surprisingly careless of me. Thanks for the correction. But yeah, I do think it would be significantly better restructured to put that at the end of the bullet list. … actually, reading this all more carefully now, I retract my praise of this as “a genuine deprecation”. They’ve abused the word deprecation like so many others. I fear the word will soon be lost to us, as more and more people misuse it. “This year, we will similarly deprecate non-HTTPS access and TLS 1.0 and TLS 1.1 for npmjs.com, the public npm registry.” No, you will similarly remove it. “we will also take steps to alert affected users to this change ahead of the deprecation.” — no, you’ve deprecated it now, and are taking steps to alert users ahead of the removal. “The npm registry is removing TLS 1.0 and TLS 1.1 support” would have been a more accurate title.
- iudqnolq 5y agoI agree it's strange
- nerdponx 5y agoRight. It is now currently deprecated as a result of this announcement. It will then be removed according to the schedule in the announcement. Super confusing because they do not mean the same thing and I can't imagine why anyone would think they do.