In reply to markk5.

The numbers quoted above are bytes of code -- not lines. If you want to count lines, the public 3.4.1 release has 90,889 of PHP, 16,997 lines of js, and 21,690 lines of css. Where you're pulling 2 million lines from I'll never understand. Core, by the way, in lines is 255,961 php, 58,222 js, and 80,836 css.

So for starters, if you're going to quote numbers, please actually get real numbers?

Next up, if a user is using Jetpack for just one feature, the majority of that code just goes away. It's never even included. So apart from having unused text files sitting on your server eating a couple megabytes, it's really not a big deal.

Local mode isn't something we try to hide, it's just something that isn't that useful for the experience of most users. There are some plugins that will toggle it on for you, they've even been written about right here on the Tavern -- https://wptavern.com/unplug-jetpack-use-jetpack-modules-without-connecting-to-wordpress-com

I've also written in depth about why we ship Jetpack as a single plugin, as opposed to thirty or so separate ones -- http://stephanis.info/2015/01/31/why-jetpack-isnt-a-collection-of-plugins-part-the-first/

Secrets aren't sent in plaintext with requests to/from Jetpacked sites -- the request itself is signed with the secret, and then the signature verified. You can see a bit more of how this works in `class.jetpack-signature.php` if you like.

Photon only works when there is an existing WordPress.com connection because that is what grants WordPress.com the right to host their images for them -- their agreeing to the terms of service through the connection.

And yes, thank you for your most generous counsel, I had not yet realized that being overweight is unhealthy.