mcc on Nostr: I have a npm module I published in 2016, which to my knowledge has not worked since ...
I have a npm module I published in 2016, which to my knowledge has not worked since about 2018 (due to my failure to correctly use package-lock.json— in my defense, introduced in 2017). At some point in the last few years npm started getting very worried about supply chain attacks, so they started trying to get everyone to enable 2FA on their npm account, so frequently they send me emails asking for my phone number, and that's very reasonable, but also I think it's reasonable for me to not care
Published at
2024-08-12 03:45:27Event JSON
{
"id": "13f5322a31333dd298ccfa2dced837a102ffa2331a8de91dcd2e68f2af9266c4",
"pubkey": "a3162b9720f6b515ac4bd22d5ea4abf0f85f5685130dca40f46fe684fe85b255",
"created_at": 1723434327,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/mcc/statuses/112946992067710637",
"activitypub"
]
],
"content": "I have a npm module I published in 2016, which to my knowledge has not worked since about 2018 (due to my failure to correctly use package-lock.json— in my defense, introduced in 2017). At some point in the last few years npm started getting very worried about supply chain attacks, so they started trying to get everyone to enable 2FA on their npm account, so frequently they send me emails asking for my phone number, and that's very reasonable, but also I think it's reasonable for me to not care",
"sig": "b0a944709c32d5f071865d6ea9f58efba30ee3ef5523922ad01a92c83db4a5480b21e3f3f78e6c8094a6e54dd45d7cc54f01cc437fa10bb275498101fc52cd30"
}
