Fixing that is easy but takes will to do so: it hinges on deprecation and removal of support for non-same-origin scripts.
-
-
Replying to @RichFelker @ra6bit
I have sketches of how this might be practical without horribly breaking things for ordinary users.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @ra6bit
Start by identifying top 99% or so of js libs loaded non-same-origin in real world usage, and hard code them in the browser.
1 reply 0 retweets 1 like -
Replying to @RichFelker @ra6bit
Only hard-code current version; anyone who wants to upgrade them has to copy the new version to their own site.
1 reply 0 retweets 1 like
Replying to @RichFelker @ra6bit
Then completely remove non-same-origin js support.
7:48 PM - 13 Dec 2016
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.