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

 @xkon How does it work now. Same result as what I proposed, just less
 intimidating. If your plugin needs to add sections that shouldn't be a
 problem. No one policy can possibly fit all, but we are currently
 basically generating what reads (with exception of the helper notes) as a
 complete policy. Do you think many users will think twice about just using
 it as is? That means that they will likely never merge in the needed info
 from dozens of plugins on their site. WordPress is supposed to be easy for
 users to get going. This currently will take days to put together a policy
 based on my own plugin usages, most of which are pretty common.

 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.

 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 prefer not to have to field 1000 questions on the subject over the next
 year, which means doing our best to generate as close to possible a ready
 to use policy. Anything less puts millions of sites at risk.

 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.

 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.

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