I’m a proponent for security and the principle behind this action (one of my comments is featured in this article) but what I don’t like is the approach and seemingly “forced”-ness of this action. I personally run things on the bleeding edge wherever possible. I also want to highlight I am a big fan of the recent movements the core team (and the rest of WP) have taken and the direction in which WP is going! But this isn’t right.

I can’t help but feel that this is pathing the way for something else… this definitely lays the foundation for giving WordPress a LOT of power on the internet. There was a thread where it was mentioned that plugin and theme auto-updates could follow this… really?!

The distinction between .com and .org needs to be managed here. Just because WP can, doesn’t mean WP should.

Not doing this in no way kills WordPress, as suggested by “PP”. Why is it WP’s fault if a user remains on an old version? Why is it WP’s vault if a user uses an old PHP version? What next… they define our themes for us? Why can the rest of the internet/world manage this in a more suitable manner, but WP has to take this approach? How is WP going to manage the support for all of the sites/user workflows they break?

This should 100% be opt-in, NOT opt-out. Simple. Implied consent is not consent.