Vladomir Prelovac made note of a new plugin on ManageWP.org today that caught my attention, and also caught the attention of Sarah Gooding of WPTavern. The plugin, called Unplug Jetpack, created by Tanner Moushey, gives access to all of the Jetpack modules that do not require a connection to WordPress.com. The plugin does this by putting Jetpack into developer mode. I’m not sure what effect that might have on things now or in the future, but it is an interesting way to handle the problem of wanting to use some of Jetpack’s modules, without having to connect to WordPress.com in order to do so.
Which Jetpack modules require a WordPress.com connection – and which don’t?
This plugin got me to thinking. Which Jetpack modules actually require a WordPress.com connection – and which don’t? I couldn’t find any mention of that anywhere, so I took the time to install the Unplug Jetpack plugin, and activated every module possible without being logged into a WordPress.com account. Then I took some screenshots, moved things around to make the screenshots look good, and ended up with the two images below. One shows all the Jetpack modules that do require a WordPress.com account and one shows all the modules that do not require a WordPress.com account.
I know George Stephanis has given one reason for the whole Jetpack bundling issue, but I’m hoping to hear an acceptable reason in George’s next post for forcing users to always connect to WordPress.com to use Jetpack at all – even if they only want to use the modules that don’t require connection. Perhaps Jetpack should at least be separated out into two bundles? Just a thought. What do you think?