Somewhere in SV: "npm is great; we get to share our bloated server code with our frontends, then we add tools to fix it. Full employment!"https://twitter.com/andreysitnik/status/913131548777570305 …
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
I have so many opinions on this. Don't even know where to start. But, the goal should not be to increase divergence.
Making server side more restricted could also have benefits.
Dunno, the crypto hack Signal just did seems like it could be extended indefinitely 
the browserify path for a couple native modules is horrendous. request is like 2MB (my bad) and require('crypto') is insane.
it's why I moved to using sodium crypto libraries that has specific target paths for Node.js and the browser.
I've also spent days traversing paths that marshal binary data back and forth between Buffer and ArrayBuffer APIs.
Buffer shims for the browser are a foot gun.
I started to hear dev talk about microservices in Frontend, is it even possible?
It's the same as building modular smartphone. There are tradeoffs. Modularity <-> performance
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.