A suggestion for future updates, give the admin control of the priority for the add_filter so that we can control the display order on our pages. For example, for sharedaddy in sharing-service.php the default is:
add_filter( ‘the_content’, ‘sharing_display’, 19 );
add_filter( ‘the_excerpt’, ‘sharing_display’, 19 );

Now, the default priority is 10, so 19 is a low priority. That pretty much ensures it displays after any other plugin – for example, Outbrain. But what if we want to prioritize the sharing links higher, so that they don’t get buried? In this case Outbrain doesn’t set their priority, so it is 10 (default), and changing the lines to:
add_filter( ‘the_content’, ‘sharing_display’, 9 );
add_filter( ‘the_excerpt’, ‘sharing_display’, 9 );

Means they’ll display before Outbrain. But doing this means editing the file and remembering to do it every time you upgrade because it steps on the changes. If this were exposed as a setting in the admin interface it would survive upgrades and would just generally be easier.

I never know, but does anyone like if Akismet was added into the Jetpack Plugin? It seems like a lot of people use it, and the thing is less plugins seem so much better! And maybe a contact form builder too! Something we all want for a long time!

You have all these things on this blog, where I’m commenting right now, which isn’t a wordpress.com blog. So why can’t we get it in Jetpack? I don’t see why it has to be exclusive for wordpress.com blogs.

I remember reading an article about Comment Plus in which was commented that Jetpack is coming with the Twitter/Facebook etc login feature soon. I would post a link to the article, but I can not remember for the life of me what I was searching for at the time.

If you Google “wordpress jetpack plugin sql injection vulnerability” the results are a bit unsettling.

Can you tell us the status of any possible vulnerabilities? I would love to recommend Jetpack to my clients. Please point us to your public acknowledgement of this issue and tell us the current status. Also, on WordPress.org the current status = Not enough data (31 say it works; 44 say it’s broken).

The one exploit report (the top result in Google) has been reported to us and we have been unable to replicate an issue. We have had several of our staff look into this issue and none could find an exploitable condition as given in this report.

Please be assured that we research any potential security issues and resolve those that we can reproduce in testing.