Re:Apple will soon treat online web tracking the same as a s...
by reilly3000 on Sunday August 18, 2019 @06:35PM
(#20733394)
Thanks for sharing. That is really helpful.
I work with an enterprise publisher that has literally every item listed as an essential part of how it does business, from running programmatic ads to SSO and Google Analytics. The Unintended Impact and No Exceptions parts would mean a rework of that entire business for all of WebKit. That is true of most web publishers today. I cannot overstate what a vast impact this will have on web publishing.
Maybe those things need to change. We want to move towards a member driven model and move away from ads, but in order to fund that transition ads need to continue running as the product is developed and user base grows. Even then, since we use Okta for SSO, that would also break or require a significant reimplementation to server-side auth, which could also break cache for authenticated users.
We have a grand, beautiful plan for creating a publishing model that is trackerless except for a first party event logger that hashes all PII before it’s stored. We need data to operate, and some of it needs to come from the client. We would share client data with zero 3rd parties.
For now our pages are a brothel of 3rd party scripts. We hate it, we can’t survive with our it, and forcing this change could force us and most web publishers today out of business.
Below is a quote from the link above:
>Unintended Impact
There are practices on the web that we do not intend to disrupt, but which may be inadvertently affected because they rely on techniques that can also be used for tracking. We consider this to be unintended impact. These practices include:
Funding websites using targeted or personalized advertising (see Private Click Measurement below).
Measuring the effectiveness of advertising.
Federated login using a third-party login provider.
Single sign-on to multiple websites controlled by the same organization.
Embedded media that uses the user’s identity to respect their preferences.
“Like” buttons, federated comments, or other social widgets.
Fraud prevention.
Bot detection.
Improving the security of client authentication.
Analytics in the scope of a single website.
Audience measurement.
I work with an enterprise publisher that has literally every item listed as an essential part of how it does business, from running programmatic ads to SSO and Google Analytics. The Unintended Impact and No Exceptions parts would mean a rework of that entire business for all of WebKit. That is true of most web publishers today. I cannot overstate what a vast impact this will have on web publishing.
Maybe those things need to change. We want to move towards a member driven model and move away from ads, but in order to fund that transition ads need to continue running as the product is developed and user base grows. Even then, since we use Okta for SSO, that would also break or require a significant reimplementation to server-side auth, which could also break cache for authenticated users.
We have a grand, beautiful plan for creating a publishing model that is trackerless except for a first party event logger that hashes all PII before it’s stored. We need data to operate, and some of it needs to come from the client. We would share client data with zero 3rd parties.
For now our pages are a brothel of 3rd party scripts. We hate it, we can’t survive with our it, and forcing this change could force us and most web publishers today out of business.
Below is a quote from the link above:
>Unintended Impact There are practices on the web that we do not intend to disrupt, but which may be inadvertently affected because they rely on techniques that can also be used for tracking. We consider this to be unintended impact. These practices include:
Funding websites using targeted or personalized advertising (see Private Click Measurement below). Measuring the effectiveness of advertising. Federated login using a third-party login provider. Single sign-on to multiple websites controlled by the same organization. Embedded media that uses the user’s identity to respect their preferences. “Like” buttons, federated comments, or other social widgets. Fraud prevention. Bot detection. Improving the security of client authentication. Analytics in the scope of a single website. Audience measurement.