[wp-trac] [WordPress Trac] #53069: Consider implications of FLoC and any actions to be taken on the provider (WordPress) front

[WordPress Trac]

#53069: Consider implications of FLoC and any actions to be taken on the provider
(WordPress) front
----------------------------+----------------------
 Reporter:  helen           |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  5.8
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  privacy
----------------------------+----------------------

Comment (by roytanck):

 In many ways, this is an unprecedented situation. It's not every day that
 a built-in, on-by-default browser feature is introduced. And in this case
 it's a feature that actively harms visitor privacy for the benefit of ad
 tech companies.

 Instead fo comparing FLoC to its predecessor, third party cookies, I feel
 it's actually more like the Facebook Pixel. Mostly in the sense that it's
 controlled by a single surveilance capital company. FLoC may not be quite
 as nefarious, but I feel it should be something website owners conciously
 opt in to.

 WordPress has always advocated for a free and open web, and FLoC appears
 to actively harm that goal. I think WordPress should take a stand against
 this, and do it now.

 I feel like adding the HTTP header is currently mostly a political
 statement. It's a project/website's way of voicing our concern about the
 trial. In its current state, I support blocking FLoC by default. If the
 eventual implementation of FLoC warrants it, we can revert back to an opt-
 out option in whatever the following release is at that point.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53069#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform