Hi, @erikras here. The primary purpose for adding scarf as a dependency to this library was to gain some insights into just who is using this library. Nothing but the IP addresses of the computers running the npm install were ever recorded, which were back referenced to determine corporation identity. It was never "malware", but for sure it broke the contract assumption of "I can run npm install without anyone collecting data about me". Every day that assumption is more tenuous, as the 21st century internet continues the trend towards the default assumption being "someone is collecting data about me". But I, personally, don't feel right participating in that trend. The month or so that I had scarf installed confirmed that the largest Silicon Valley giants are using this library. Further spying will not produce more value. I would like to apologize for violating your trust.
That said, the psychosocial rot that is consuming Open Source is the broken funding model. If each of you would request the equivalent of one hour of your salary every month to go to libraries you use (and save you way more than one hour per month), we OSS devs would feel less compelled to search for funding solutions. Please consider adding a line item... ❤️
Changes
- Remove
scarfdep #361