[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 robscott):

 Thanks for listing this here @helen - I was sorry I couldn't make the core
 dev chat, but caught up with it on Slack.

 This statement:

 "If WordPress were to send the explicit opt-out header by default, what
 sort of impact would this have on individual users (both providers and
 consumers) and ad/targeting technology at large?"

 I think we don't need to consider this to be a be-all and end-all "we've
 opted everyone in WordPress in or out!" Situation. A core setting, similar
 in nature to the robots meta opt-out, would be an enhancement, empowering
 webmaster to make decision for themselves?

 The question then would be if we would opt out by default - but I don't
 see why (should the experiment move to production) we shouldn't empower WP
 website owners to make this decision without having to use a filter to add
 the header.

 Is it plugin territory? Well, for me it fits with Privacy settings,
 regardless of political stance, we don't need to take a view: some people
 want to disable it, we should enable them to make this decision. (maybe!)?

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