It would be tragic if public sector services adopted the JavaScript-heavy stacks that frontend influencers have popularised. Right?| Infrequently Noted
Third-party (AKA cross-site) cookies are harmful to the web, and must be removed from the web platform. This finding explains why they must be removed, and examines the challenges in removing them. We highlight some use cases that depend on third-party cookies and offer some examples of designed-for-purpose technologies that can replace them. Specification authors are expected to ensure they do not undermine the benefits of removing third-party cookies when proposing new web platform technolo...| www.w3.org
Unsanctioned Web Tracking| www.w3.org
Facebook probably needs no introduction; nonetheless, here is a quick history of the company. The world’s biggest and most-famous social network was launched by Mark Zuckerberg while he was a student at Harvard University, in early 2004. TheFacebook, as it was then known, was originally intended to serve a digitised version of the ‘face books’ held by Harvard’s various colleges, which were paper directories containing images and personal information about students. Initially limited t...| Business of Apps
Apple robbed the mob's bank. Mobile marketing and advertising, freemium monetization strategy, and marketing science. Mobile Dev Memo.| Mobile Dev Memo by Eric Seufert
Alex Russell on browsers, standards, and the process of progress.| Infrequently Noted
This document describes the web tracking practices that WebKit believes, as a matter of policy, should be prevented by default by web browsers.| WebKit
The W3C Technical Architecture Group explains how third-party cookies reduce users’ privacy and why they must be removed from the web. This blog post introduces the latest TAG finding, Third-party cookies must be removed.| W3C
When we invented Private Browsing back in 2005, our aim was to provide users with an easy way to keep their browsing private from anyone who shared the same device.| WebKit
In-App Browsers subvert user choice, stifle innovation, trap users into apps, break websites and enable applications to severely undermine user privacy. In-App Browsers hurt consumers, developers and damage the entire web ecosystem.| Open Web Advocacy
There are only two-and-a-half reasons to build a browser, and they couldn't be more different in intent and outcome, even when they look superficially similar.| Infrequently Noted
Privacy labels inform you of app privacy practices so you can make better choices. See how apps from Apple handle your data.| Apple