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
OK, so if I can't use the unhandledrejection event, how do I catch all unhandled promise rejections and show the user a "something went wrong" page?
If you want to protect yourself against misbehaving browser plugins, I think the answer is fundamentally that you can't. Ultimately you're running the code in an unknown dynamic environment with arbitrary third party code running within it. Can't have it both ways
Seems like the best bet might be to just sniff for known bad plugins and skipping this behavior or showing the user an additional message in this case (trying to do this per-error instead of globally seems like a lost cause IMO)
So you're saying the best bet is a list of special-cased ignored errors, but that's probably not going to work out well in practice because of the effort required to maintain it?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
