@TechLifeWeb Not sure if you'd run across it yet, but are you attending #IndieWeb Camp in LA this year? http://indiewebcamp.com/2016/LA

Hugo, I'd written up some details specifically for Known a while back: http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and there's a roughly equivalent set at the camp: http://indiewebcamp.com/Posting_from_mobile_devices

@mjane_h It dawns on me that you might find the #IndieWeb Summit this weekend in your back yard to be interesting http://indiewebcamp.com/2016

This is hopefully a simple, but useful feature request:
I appreciate that there's a filter for jetpack_allow_per_post_subscriptions, however it appears to only default to unchecked. It would be great if it could also be set (programattically or otherwise) to unchecked so that posts would always default to NOT be emailed to subscribers.

In my particular preferred use case, I'm using some advanced indiewebcamp.com related tools like micropub to allow services like Instagram (via OwnYourGram.com) and Foursquare/Swarm to post directly to my WordPress installation. In these cases, I'm posting with a remote service (perhaps similar to posting via email) and don't have access to the post interface to toggle the checkbox so that these posts don't automatically email subscribers. Conversely, when I'm using the direct posting interface, it's simple enough to toggle the checkbox manually.

To put it another way: Is there a way to add a line of code to the subscription filter [https://jetpack.com/support/subscriptions/#filters] so that the checkbox is both available AND it appears checked automatically?

For the same reason, if it doesn't already exist, it would also be nice to have the ability to toggle the checkboxes on the JetPack publicize feature as well. (If this already exists, then it's likely easy to borrow the code to accomplish the same thing for emailing subscribers).

Thanks to the entire team as always for a great product!

Why am I never around in real time when @dshanske says things like "I appreciate how Chris Aldrich and his enthusiasm keeps moving the needle" http://indiewebcamp.com/irc/2016-05-18/line/1463597857406

Jay, I don't think the author David spends much time in the fora here, and I know he's been diligently developing several other plugins in the https://wordpress.org/plugins/indieweb/ suite. If you're still interested, the base code for Bridgy Publish is is on GitHub https://github.com/dshanske/bridgy-publish, where you'll also find code for most other things IndieWeb too.

If you have questions or need help, you can find him on IRC via http://www.indiewebcamp.com. He and others there are more than happy to help!

Welcome to the #IndieWeb! There are lots of other goodies and help to be found at http://indiewebcamp.com/WordPress

Congratulations! If you're not using the SemPress theme, you might also enjoy https://github.com/pfefferle/wordpress-uf2 which will do some of the mf2 material (as best it can) without remarking up your theme by hand. I've used a handful of WP themes with IndieWeb and not had problems sending/receiving webmentions (to my knowledge) or using other indiewebcamp.com goodness.

You might also appreciate the Independent Publisher theme, which is not only beautiful, but has some custom code for displaying comments, pingbacks/trackbacks, and even webmentions and will shortly have additional mf2 mark up as well (or should, in it's next release which is right around the corner.) The Github code is ahead of the official release on WordPress.org if you want to test it out.

Thanks @snarfed, I'll see if I can't manage to get it sorted. Looks like I'm going to have to hack my theme a good bit to support this and other fun. I'll see if I can't post the details to IndieWebCamp and other relevant locations for others shortly as well. Thanks as always for having done the lion's share of the heavy lifting.

You could start with http://indiewebcamp.com/Getting_Started_on_WordPress which will walk you through most of the process. You should start with the Webmention Plugin and Semantic Linkbacks to send/receive webmention support and to help comments look better respectively. Brid.gy connects your blog to responses from sites such as Facebook, Twitter, et al.

Keep in mind that some of the other plugins you'll run across may have small bugs or quirks as they're being actively developed. Most of the plugins in the WordPress.org repository are usually more stable than some you'll run across on GitHub, but those also are dated in terms of development work, so you'll have a better idea how current they are. You can usually find one or more of us via IRC, or in social media if you need help.

@mrkrndvs In case you haven't seen it, you should be aware of http://indiewebcamp.com/wordpress. Let us know if we can be of help: http://indiewebcamp.com/WordPress_Outreach_Club

@scott_gruber Are you aware of Homebrew Website Club in LA? http://indiewebcamp.com/next-hwc It'd be great to have another WordPress compatriot.

I just put together a fresh install and ran the import, but it maxed out at 3200 tweets, which only gets me back to early 2013 rather than my total of 5k+ tweets going back to early 2008. Does Twitter have a hard limit for pulling in tweets historically or is this a bug in the plugin? Or even a daily rate limit?

I know Twitter has a download of one's entire history. Could this data store be used to improve initial import while still maintaining completeness?

This is a great concept and fits right in with the IndieWebCamp.com philosophy. I suspect many in the community there would use this.