I’ve talked about this before: As web designers, we can’t trust the network. Sure, we have to contend with mobile data “dead zones” and dropped connections as our users move about throughout the day, but there’s a lot more to the network that’s beyond our control.
Here’s a roundup of some of my “favorite” network issue related headlines from the last few years:
- Sky Broadband misclassified the jQuery CDN as a malware site and broke much of the web for their users.
- Comcast admitted to injecting self-promotional advertising into web pages served by their Xfinity routers. (They have also been called out for artificially inflating subscriber bandwidth usage with their own crap.)
- United was recently called out for blocking access to the New York Times on their in-flight Wi-Fi.
- Samsung smart TVs were found to be injecting video ads into video streaming apps.
Some of these issues can be avoided by serving content over HTTPS, but that still won’t enable you to bypass things like firewall blacklists (which led to the jQuery outage on Sky). Your best bet is to design defensively and make sure your users can still accomplish their goals on your site when some resources are missing or markup is altered.
We can’t control what happens to us in this world, we can only control our reaction to it.
@aardrian And that’s why I decided to switch today.
@AaronGustafson It’s been on my to-do list for a while, but your post was another gut-punch reminder that I gotta move faster.
- Moved to HTTPS
More Proof We Don’t Control Our Web Pages, From the Notebook of Aaron Gustafson ift.tt/1VYtn1F
Aaron collects some recent examples that demonstrate
- why we should use HTTPS and
- why we should use progressive enhancement.
And this is from aaron-gustafson.com/notebook/more-…
“More Proof We Don’t Control Our Web Pages” aaron-gustafson.com/notebook/more-…
Today’s Readings Aaron T. Grogg
Conclusion: everyone is awful aaron-gustafson.com/notebook/more-…
- Wednesday is Link Day!
- Content Security Policy, Your Future Best Friend