3 ms·
I am a former maintainer / librarian on cdnJS. I helped out some years ago when I wanted to learn how version control and git worked. This was in the pre-automa
by petecooper 7y ago
I am a former maintainer / librarian on cdnJS. I helped out some years ago when I wanted to learn how version control and git worked. This was in the pre-automation era (2013 to 2014 in my case), and I went through the existing libraries to find outdated instances, located new versions of the same, raised the PR to update it. All good.
Back then, and I don't know how much has changed, the libraries were maintained on GitHub and CloudFlare did the hosting. I wasn't aware of any problems with either organisation doing what they were doing, the system worked just fine. The founders (see https://cdnjs.com/about https://cdnjs.com/about for confirmation) Thomas and Ryan were around, but not super active. Thomas was involved in building out some of the automation infrastructure, but the day-to-day of updating the repo was largely undertaken by the maintainers, and that was fine. I never 'met' either founder, but we had occasional email back and forth and they were grateful for my maintainer-ing.
I used the GitHub Mac app because I was finding my way. Whenever I changed any library, the action of the app checking a HUGE repo for any changes pegged my laptop for a few minutes every time. Not ideal, but the process of doing this librarian-ing helped me learn about a heap of stuff.
According to [1] I stopped on cdnJS mid-2014. Things got a bit twitchy for me when a library (edit: jPlayer) was pulled from the file structure because it was compromised (edit: XSS) or found malicious at release. I had a couple of user complaints directed at me because I was the one that added it in good faith originally (it passed the malware checks I ran on it). The founders stepped up to explain it wasn't me that was to blame, and one person didn't take that too well -- basically they found me on other software forums, posted threats to me and explained how the library that I had added, and someone else had removed, was crucial to their business and they'd lost such-and-such dollars in revenue with that library 404-ing without notice and that they were coming to find me and extract the money from me by force. It all died down a few weeks later.
[1] https://github.com/petecooper?tab=overview&from=2014-12-01&to=2014-12-31 https://github.com/petecooper?tab=overview&from=2014-12-01&t...
Edits: clarity.
- jlokier 7y ago> they found me on other software forums, posted threats to me and explained how the library that I had added, and someone else had removed, was crucial to their business and they'd lost such-and-such dollars in revenue with that library 404-ing without notice and that they were coming to find me and extract the money from me by force Wow, that really takes "open source maintainer abuse" to a whole other level.
- wongarsu 7y agoIf cdnjs was an enterprise offering it would be reasonable to expect either a notification of removal and a generous transition period, or just cdnjs disinfecting the package behind the scenes (and then boasting about it). But expecting the same from a free service is unreasonable. Stalking people and asking for damages because they didn't meet an unreasonable expectation is beyond unreasonable.
- diggan 7y ago> it would be reasonable to expect either a notification of removal and a generous transition period For security issues like XSS in live and deployed libraries? I mean, I don't agree that the library should ever be removed, but if you are of the opinion that vulnerable libraries should be pulled, they should be pulled quickly no?
- wongarsu 7y agoWhat's worse: uninterrupted service with a time window where you are vulnerable to a known XSS attack, or your service suddenly going offline, customers calling your support but all you can tell them is that you will be back in a few days, but at least they are not vulnerable to XSS in the meantime? Of course for a small startup a few days notice before removal is enough, but for a large company a few days may be barely better than no heads up at all. Not everyone can move with the same agility. If you don't pull it at all you risk people staying on the library forever because they don't want to touch a working system.
- jlokier 7y agoNote that in this case, the person being stalked & threatened isn't even the same person as who removed the library. Essentially, they were physically threatened over an open source change done by someone else.