by

Jetpack 7.1 Adds Feature Suggestions to Plugin Search Results. This is way over the line.

I use Jetpack on some of my sites, as well as some client sites. It provides a lot of features that site owners will need, without having to install a bunch of plugins, and does so reasonably accessibly. However, the latest release, (7.1), quietly adds Jetpack feature suggestions to the plugin search screen. From The Tavern:

If a user searches for a plugin that has a feature that is already offered by Jetpack, the plugin will insert an artificial (and dismissible) search result into the first plugin card slot, identifying the corresponding Jetpack feature.

This is so far over the line of what’s acceptable and what’s not, it’s not funny. I’d be livid if any other plugin did this, and the fact that Automattic is doing it, combined with its incredibly large amount of influence over the WordPress ecosystem, is enough to make me seriously consider uninstalling Jetpack from every one of my sites. The WordPress dashboard and administration screens are already choked with advertisements and useless nags thanks to other plugins and themes. The fact that Automattic is essentially giving this a blessing is, I suspect, going to make this problem worse than it is. The web is supposed to be independent and decentralized. Automattic is supposed to be helping to ensure that an open, independent web survives, or at least that’s what its CEO appears to be leading us to believe. Driving an ecosystem to use the features of one plugin over everything else is an attempt at centralization, which is obviously in direct opposition to an open, decentralized web. Getting back to the accessibility question, while Jetpack does some of the things it does reasonably accessibly, does this mean that Automattic is going to put some extra muscle behind making sure that every one of its features are accessible? If you’re going to exercise undue influence over plugin search results, effectively cutting off the air supply of anything that may provide a Jetpack feature more accessibly, then you take on the responsibility of ensuring that accessibility is looked after. I think I already know the answer to these questions, but I decided to pose them just in case. You know, in case I happen to be dead wrong in my supposition. At the end of the day though, I’d rather Automattic just not game the plugin search results.


Respond

Leave a Reply

Comment.

Comment

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.