[wp-trac] [WordPress Trac] #43981: Privacy notices page: improve UX and readability

[WordPress Trac]

#43981: Privacy notices page: improve UX and readability
--------------------------+------------------------
 Reporter:  idea15        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  gdpr          |     Focuses:
--------------------------+------------------------

Comment (by xkon):

 Replying to [comment:8 danieliser]:
 >If your plugin needs to add sections that shouldn't be a problem.

 So that will result in a page having 1000 sections because that's what
 plugin authors decided to do? There's a first problem that I see.


 > WordPress is supposed to be easy for users to get going.

 WordPress yes, the regulations / laws / policies are not. So there's a
 really really thin fine line that we shouldn't step over imho.

 > I will have to start with the core policy suggestions, rewrite
 accordingly, then move on to manually merge in the data from 10+ plugins
 one at a time, each having different data that has to be merged into the
 same policy template core already suggested, not just appended to.

 And that's what you would/should do if you had 3 plugins saying 'We gather
 analytics' under the data section you would again have to filter the 2
 extras out and re-write it to the tone that you speak with your users.

 > Plugin A's cookies shouldn't be listed at the bottom by themselves, that
 makes no sense, yet that is how I imagine most of my own users (very lay)
 doing it. These penalties can be applied to the smallest of blogs
 (unlikely but possible), so assuming that every site owner is going to
 hire a lawyer is a very bad assumption. People writing small blogs
 occasionally are not gonna spend the time or the $.

 I didn't understand at all here. `cookies shouldn't be listed at the
 bottom by themselves` what bottom? My plugins cookies will be listed on
 the policy that I'm pushing to core. You can take that and do as you
 please with it as with any other information that I might be adding.

 > If your fear is having to write 5 different filters instead of 1, in my
 opinion as someone who runs multiple plugins that will have to use these
 new functionalities, I'd say you strongly need to reconsider, you will
 thank yourself later when you are not answering needless support tickets
 or having your users get sued out of oblivion for non compliance.

 I don't have a problem writing 10 filters even, but like I said
 'communicating' is something that each individual does in a different way,
 Core can't pre-define that in no means.

 > Our users problems are our problems. If we can solve them with a little
 extra effort on the plugin devs part, that is a no-brainer, which is an
 underlying principle of WP, cough-cough backward compatibility.

 I'm just saying that each of ways comes with negatives and positives. The
 idea is to give freedom to any website owner + plugin author to write
 their policy and notices as they see fit since that's not Cores territory.

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