/2018/01
-
Third-party scripts are probably the #1 cause of poor performance and bad UX on the web.
Chris Coyer collects a range of sources that explain why third-party scripts on websites – and handing control over them to the marketing department – is bad for performance, security and privacy.
-
Amen!
-
Free/libre Google Analytics -alternative Piwik is now "Matomo": no matter the name, the tool remains #1 choice for independent web analytics. #GDPR
-
Marcus Povey describes why a website should not show webmentions with embedded images from the source site (as it could allow the publisher of the source site to track the audience of the cited site).
This is not Webmention or Indieweb specific, but a general privacy risk: whenever loading resources from a third party, that might enable them to track a user.
(Not mentioned in the post, but the suggested solution of caching the images of course opens yet another can of worms: strictly speaking that might be a copyright infringement, unless the owner of the profile image has consented to it being copied.)
-
We have built the digital world too rapidly. It was constructed layer upon layer, and many of the early layers were never meant to guard so many valuable things: our personal correspondence, our finances, the very infrastructure of our lives.
Zeynep Tufekci pinpoints the vulnerabilities of computers due to the technological debt they carry along; why aren't computer bugs scrutinized with the same rigor as for example plane crashes?
-
The internet is a great thing. It is also the biggest machine on earth, and it runs mostly on coal, which is bad news for our climate.
The Planet Friendly Web Guide is an ongoing work-in-progress, written in the open (which in itself makes this an interesting project), that aims to be an educational resource based on a clear mental model:
The planet friendly web guide is an open source, freely available guide, combining an easy-to-understand mental model to help you think through what you can do and why, with focussed guides showing how you can make these changes, drawing on techniques from fields ranging from service design, user experience, web performance optimisation, and technical architecture.
-
A fictional story showcasing a smart (social engineering) exploit to use npm packages as a backdoor vector for malicious code.
On any page that collects any data that you don’t want me (or my fellow attackers) to have, don’t use npm modules. Or Google Tag Manager, or ad networks, or analytics, or any code that isn’t yours.
The author even illustrates how a CSP header will not fully prevent this kind of attack. In the end, it boils down to the summary of the article:
My goal (as it turns out) is simply to point out that any site that includes third party code is alarmingly vulnerable, in a completely undetectable way.
The recommendation would be to use sandboxed iframes with hand-crafted JS for any sensitive input pages.
-
Kick off 2018 with a bang? Final call for @btconf
#Munich, Jan 15-17! Fantastic web&design inspiration; my previous experiences