12 Comments

  1. Dylan
    · Reply

    This is actually a fantastic idea; I really hope they integrate it into core.

    A standardized API for this would really help consolidate everything for my own plugins, especially since, for example, consent is only needed if the site owner enables certain features.

    Report

  2. Kadai Crosshansen
    · Reply

    Like Dylan says above, this is indeed a fantastic idea.

    Right now, we need to roll out our own consent method or mess up with plugins to enforce that setting… Depending how it is implemented in each case.

    In any case, having a single option that can be checked for this would make life easy for everyone.

    Report

  3. Brandon Still
    · Reply

    This absolutely should be folded into the core. Consent is something that will only become more prevalent moving forward.

    Providing a standard for the development community will only improve the way we go about things.

    Report

  4. Harvard
    · Reply

    I think this Idea is welcome.

    Report

  5. Bashir Aliyu Zubair
    · Reply

    If this happens, honestly we do appreciate WordPress. this Idea is welcome.

    Report

  6. Martin Riiel
    · Reply

    Absolutely great idea, this makes a lot of sense going forward to a more user preferences / privacy-respecting internet future.

    Report

  7. Garrett Hyder
    · Reply

    Thanks for the article Justin and everyone for the support, glad to hear there’s interest out there. All feedback, testing and contributions are greatly appreciated. All the best

    Report

  8. Philip Ingram
    · Reply

    So ironic. A consent API coming from core who doesn’t care about consent when it comes to forcing new features that considerably change core without a site owners consent such as auto-updating core (opted in by default since 3.7), the recent large image dimension restriction (opted in by default since 5.3), and forcing of the new editor to be full screen (opted in by default since 5.4) as if these were in high demand by people other than core contributors who…let’s be honest here, mostly wanted accolades to place under their names for notoriety.

    All of these should be feature plugins or opt-in only features, not forced by default requiring one to opt-out after the fact. Do you know how many pro photoblogger websites I had to patch to allow hi-res images, not cool!

    Yeah, “consent”, but only when it’s on OUR terms. Now this will likely be enveloped into core as well, most likely… without anyone’s consent.

    It’s like we forgot the core concepts behind how open source works. When I share something with someone and give it to them 100% to do with as they please, I am sure they will appreciate I do it without keeping one-hand on it and forcing my future desires on them even if I believe it’s what’s best for them.

    Report

    • Justin Tadlock
      · Reply

      Developers do not need consent from end-users to continue developing new features or making changes to the software. That’s not how the process works. If that were the case, WordPress would have never advanced to the point it is at now. We can’t all point to our particular dislikes and say they shouldn’t be in the platform because we didn’t consent to them.

      As for auto-updating old installs without consent, I vehemently argued against doing that. Software should never be updated without consent (either through terms or an option). If the software says it’s an opt-out feature, that’s fair. Just don’t do it retroactively for installs where it was previously an opt-in feature.

      Report

      • Philip Ingram
        · Reply

        Agree, with varying degrees of consent severity, such as “in principal”, that which we should never stray vs generally just being kind to one’s user base and how it impacts them, hopefully weighing for better or for worse if it should be – the new default.

        “Like” function seems to be bugging atm. +1 like

        p.s. I recall your points.

        Report

  9. Philip Ingram
    · Reply

    I realize I forgot to balance my comment with some of the positives as I was overcome with shock that “consent” was at the forefront of the topic while ignoring what seemed to me the most obvious of recent scandals regarding consent that anyone can see simply skimming the core comment threads where many voice the same concerns I did.

    Thanks for the article Justin and I am glad we are considering this Consent API provided it is implemented in a way a site owner can choose to take advantage of it – i.e. they give “consent”. Otherwise (to some) the name implies that which it is not.

    Report

  10. Artem
    · Reply

    Just released my first plugin and it’s cookie consent popup)
    https://wordpress.org/plugins/cookie-notice-and-consent-banner/
    Great proposal, I would like to contribute!

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: