Attempting to rephrase why ads are bad. #64
Conversation
* 2: Removing redundant parenthetical * 3: Declaring that not using hosting isn't allowed (i.e. we will close your plugin) * 6: Due to GDPR we require ToS/Privacy * 7: Due to GDPR we require ToS/Privacy * 8: Formatting fixes. * 11: Simplify the explanations regarding advertising.
|
Maybe rephrase Seriously, changing the rules to allow your own advertizing is more than borderline. |
| @@ -1,6 +1,6 @@ | |||
| <h4>7. Plugins may not track users without their consent.</h4> | |||
|
|
|||
| In the interest of protecting user privacy, plugins may not contact external servers without <em>explicit</em> and authorized consent. This is commonly done via an 'opt in' method, requiring registration with a service or a checkbox within the plugin settings. Documentation on how any user data is collected, and used, should be included in the plugin’s readme, preferably with a clearly stated privacy policy. | |||
| In the interest of protecting user privacy, plugins may not contact external servers without <em>explicit</em> and authorized consent. This is commonly done via an 'opt in' method, requiring registration with a service, or a checkbox within the plugin settings. Documentation on how any user data is collected, and used, must be included in the plugin’s readme, with a link to a clearly stated privacy policy and/or terms of us. | |||
There was a problem hiding this comment.
I believe there is a small typo: It appears this should be "terms of use"
There was a problem hiding this comment.
Yes! Thank you. Patched in for the next edit :)
|
One more question: because these are advertisement guidelines, and they are now permitted, what are the guidelines surrounding tracking of these ads? Impressions / sites / actions taken (dismissed (which really is just snoozing)), so that we can calculate ROI. Can we implement A/B testing here? |
@javorszky They've always been permitted. This isn't new. "Discouraged" doesn't mean "not permitted". |
|
My observations:
On the whole, I like these changes. Thanks! |
|
Hey everyone, thanks for jumping in. This is NOT READY FOR PRIME TIME YET. I updated the description to explain that. This is MY idea, and mine alone. I’ve had the code on my laptop for a while, and made a pull so it could be looked at more easily as a whole. NOTHING WILL BE CHANGED WITHOUT A PUBLIC POST ON MAKE/PLUGINS Please. Calm down. The goal was to make things easier for some ESL developers who have difficulty understanding that SHOULD and MAY have different connotations. Hence saying ‘not permitted’ instead of MAY remove access. |
You read that backwards. MAY is the weaker sentence. By saying something IS NOT PERMITTED we are saying you CANNOT do it. And since we already say at the top that any violation may result in being removed, it’s redundant. |
Nothing has changed YET. This is NOT LIVE. Good lord, it’s like you’ve never seen a pull request before, |
|
I’m canceling this. Y’all jumped in before anything was remotely ready, |
|
See #66 for a more complete, and slightly closer to prime-time pull request. |
Please note: THIS IS NOT COMPLETE YET.
The reason it’s a pull request is to make it easier for us to see what was changed and discuss. As of April 2019, it is NOT considered ready. There will be a public call for comment on make.wordpress.org/plugins when we feel it’s at a good state.
Since everyone jumped in WAY too soon, I’m closing this. It was my bad, it’s too early to have this be considered. It’s NOT READY. Don’t assume anything else here.
This was my idea alone. No one else’s.