I guess we now live in the post-"ads in the npm install log" erapic.twitter.com/pSnBnMDNSg
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Be right back, inventing uBlock Origin for npm install scripts
At present, the way this ad works is that `standard` has a dependency on another new package, `funding`, which does nothing but print one of a hard-coded group of ads at install time https://github.com/feross/funding/blob/master/messages.json …
So I guess we're not at the point yet where one's machine is dynamically downloading and executing advertisers' code during npm installation. But let's check back in 15 minutes
This is probably a good time to start investigating mitigations for the kind of scenario where an npm install script tries to make HTTP requests
Because an npm install script which dynamically loads ad code is a really amazing opportunity to inject "ad" code which, I don't know, scoops up secrets from the local environment and sends them somewhere
To be clear: we got to this point because people want money. As long as we live in a capitalist society, there's no point where people stop wanting more money. That means ads will eventually permeate every electron of our universe. It is/was inevitable
No amount of revamping open source software funding structures would have prevented this from happening eventually, nor can it make this go away now it's begun
Advertising in your install log is going to be as simple as dropping a banner ad on your website. Install log ads are going to have all the same problems and very familiar solutions
"Vim is Charityware. You can use and copy it as much as you like, but you are encouraged to make a donation for needy children in Uganda."
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.