Jake Archibald writes in his blog about the bigger problem presented by importing third-party content into web pages. Even CSS is a problem as a CSS keylogger demo showed the other day.
A few days ago there was a lot of chatter about a 'keylogger' built in CSS.
Some folks called for browsers to 'fix' it. Some folks dug a bit deeper and saw that it only affected sites built in React-like frameworks, and pointed the finger at React. But the real problem is thinking that third party content is 'safe'.
While most are acutely aware, yet ignore, the danger presentd by third-party javascript and javascript in general, most forget about CSS. Jake reminds us and walks through quite a few exampled of how CSS can be misused by third-parties exporting it.
Source : Third party CSS is not safe
(Score: 2) by Pino P on Friday March 02 2018, @01:54AM (2 children)
A return from a commercially dominated web to a hobbyist-dominated web would decrease the demand among viewers for Internet access, which would in turn make it no longer economical for your ISP or its competitors in your area (if any) to continue to offer high-speed Internet access at an affordable rate.
(Score: 2) by Justin Case on Friday March 02 2018, @12:59PM (1 child)
You don't need high speed when a page is only 40K. And it was not only affordable, you had many providers to choose from, which kept prices down and service up.
(Score: 2) by Pino P on Friday March 02 2018, @03:59PM
Though dial-up was competitive, you did need a POTS line, and many households have long since given that up in favor of a cellphone.
How would amateur video be transmitted over such an infrastructure? Mail order DVD+R?