@toddlyden Perhaps this may help: http://indiewebcamp.com/Posting_from_mobile_devices It's more Android specific but iOS should have something similar.

@kevinmarks FYI, I added redirect from http://indiewebcamp.com/User:Www.kevin-marks.com to http://indiewebcamp.com/User:Kevinmarks.com so old links still work

I've noticed in many places on http://www.indiewebcamp.com your old URL still appears instead of your newer .xyz TLD. May want to swing by and update them. I tweaked the one at http://indiewebcamp.com/known which is probably the worst offender, though there are undoubtedly others.

.@christi3k Throw in some #indieweb goodness and you also get notifications/pings that @Medium doesn't have either http://indiewebcamp.com/WordPress

Happy New Year to you!

RE: Your blog vs. G+, what if I told you that you might have your cake and eat it too? I too have a WordPress blog, but I've tacked a few bits on to the back end and this allows me to use my blog as the primary hub for my work as you're suggesting you plan on doing. I then use platforms (walled silos) like Google+, Twitter, and Facebook to syndicate my material out to allow for a broader reach by leveraging social networks effects to my benefit. Even better, I've got things set up so that comments on platforms like Google+ feed back to my blog, which allows me to not only live on my own site, but it also allows me to "own" all of the content and commentary that's generated from it. (This way if Google+ is shut down next month, I'd still have all of the generated commentary, which could live indefinitely on my own site.) Thus your followers who prefer to read your material on other platforms (G+, in your case) aren't left without the content you're generating, but their commentary also appears back on the blog to add to the larger conversation.

First, consider using the "Jetpack" module (free software built by the same company that makes WordPress) and its publicize functionality to connect your G+ account and auto-post (syndicate) your Azimuth content automatically to G+. (This also frees up a good bit of time to not have to do it manually.) If nothing else, this will help to keep some of your audience engaged.

Second, to port the comments from the syndicated G+ post back to your original post on Azimuth (comments from G+ will show up as comments in WordPress that you can approve/delete just like other WP comments; this also prevents you from spending so much time in G+ after you turn off comment notifications) you can follow the details at the IndieWebCamp site (http://indiewebcamp.com/Getting_Started_on_WordPress) to add/configure a few simple plugins as well as to connect http://brid.gy to allow social networks to communicate with your blog.

If you need help/assistance to make the technical hurdles a bit lower, I'm happy to help walk you through the details or even do it for you (gratis) if you'd like. All of the modules I've mentioned are free and open source and under very active development.

For a simple example see the comments on this post http://boffosocko.com/2014/07/05/the-mnemonic-major-system-and-gregg-shorthand-have-the-same-underlying-structure/#comment-27045 which originated from G+
https://plus.google.com/+ChrisAldrich1/posts/ZfvtRPmwhtj

For a brief overview, you might appreciate the opening few paragraphs of http://indiewebcamp.com/.

@jgmac1106 You can + #indieweb to jgregorymcverry.com with plugin/instructions from http://indiewebcamp.com/wordpress & https://wordpress.org/plugins/indieweb/

Sorry for the delay, but my work schedule and travel have been awfully heavy lately. It does sound like the issue I'm having is somewhat related to the discussion on https://github.com/raamdev/independent-publisher/issues/155

I've got two separate installs with the same IndieWeb plugins installed. One uses Independent Publisher and the other is a slightly older version of the Academica Theme (v1.2.3 downloadable from https://www.dropbox.com/sh/ym0c78uyzltpeu1/AAByejNd8MG83I2MVOFXOuPaa?dl=0) which is outputting the facebook likes, twitter favorites, and reposts properly (or at least as I would expect.)

For some reason Independent Publisher isn't outputting Brid.gy likes, favorites, or resahares from Twitter and Facebook out of the box the way that Academica (or even WP common themes like Twenty Fourteen or Twenty Fifteen) does. They're not showing up at all. On the site with Academica Theme, I've tried doing a "Live Preview" of the Independent Publisher theme and there, it also seems to be "eating" (not showing) these additional comments from Brid.gy while all the other traditional comments do show up.

However, while you're tracking down the issue(s), you might also consider tweaking one additional output issue with respect to these types of comments. From a UI standpoint for themes using IndieWeb, I would recommend that the comment section sort out the comments and display them somewhat differently. For simple Facebook likes and Twitter favorites, it might be best to aggregate all of them into a facepile [http://indiewebcamp.com/facepile] with a simple header ("Liked on Facebook"/"Favorited on Twitter") followed by the photo icons of the people who liked/favorited the article within those platforms. (This is similar to how most Wordpress sites handle Likes/Stars natively within WordPress.) Following this it could create a facepile of people who reposted/reshared the post. Then after this the rest of the comments should be sorted by date/time as comments traditionally are as this will allow people to more easily read/consume the actual commentary.

This post has an example of a combination of likes/favorites/reposts and actual comments that would be better sorted into a facepile section followed by a more "traditional" comments section. http://boffosocko.com/2015/07/27/algebraic-number-theory-ucla-extension/

I'm supposing that it's how Independent Publisher is rendering the output of wp_commentmeta into its comment section that causes some of these brid.gy-fed likes/favorites/reposts to disappear.

If it helps, I'll also point out a previous and possibly related issue I'd run across vis-a-vis IndieWeb and output of comments: https://github.com/pfefferle/wordpress-webmention-for-comments/issues/1. The solution was most likely the way that the Semantic Linkbacks plugin (an IndieWeb WP-specific plugin) was handling its output. Here it's likely that @dshanske or pfefferle may be of more assistance in sorting things out if necessary.

Drupal & #IndieWeb? @KevinMarks I'm making plans for @LADrupal #DrupalCamp in 2 weeks & was considering a #BoF session to introduce people to the movement.

I've dabbled in #IndieWeb for a while via WordPress and @WithKnown, but I'm curious if anyone can give me some advice/help/pointers with logistics from the IndieWebCamp side? It's been a while since there was something in the LA area (http://indiewebcamp.com/2013/Hollywood), but it would be nice to have the relatively large developer community here more engaged on a regular basis. Perhaps this meeting of about 500 at the UC Irvine campus can help to spill over into regular meetings in the Los Angeles and Southern California areas?

Is there anyone in the area who's available August 29th (preferably) or 30th that would like to join me in doing this?

#OpenSource

@raumzeit77 http://indiewebcamp.com/wordpress has some pretty great resources for implementing IndieWeb on WordPress.

If it helps, try following some of what @pfefferle and @dshanske are doing here on GitHub as they seem to be two of the foremost IndieWeb-ers in the WordPress space. They've got wealth of plugins and know far more than I, though I do my best to dabble as I have time.
#IndieWeb

My @Quora answer to Is there a quick way to republish Twitter updates onto a blog? http://www.quora.com/Is-there-a-quick-way-to-republish-Twitter-updates-onto-a-blog/answer/Chris-Aldrich?srid=qkX

There are a small variety of answers here some of which (including Ashton Kutcher's suggestion of the formerly awesome ping.fm) are already defunct in less than a year or two, which indicates the fickle and rapidly changing nature of the internet.

I'll start by not accepting the premise of the question, but modifying the conceptualization to something more interesting and robust. Since there are hundreds upon hundreds of defunct web services many of which have died with little to no advance warning and which more often than not were information silos that didn't allow their users to export their data (see: site-deaths - IndieWebCamp [http://indiewebcamp.com/site_deaths]), I would highly recommend asking the following question instead:
"Is there a quick way to cross-publish or syndicate my content to Twitter?"

The hidden sentiment of the original question: "how can I easily keep my own data in the eventuality that Twitter disappears?" is really the root of the problem and is one which the IndieWeb movement has been diligently working on for several years. I'll let them speak for themselves:

Your content is yours
When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.

You are better connected
Your articles and status messages can go to all services, not just one, allowing you to engage with everyone. Even replies and likes on other services can come back to your sites o they’re all in one place.

You are in control
You can post anything you want, in any format you want, with no one monitoring you. In addition, you share simple readable links such as Page on example.com. These links arepermanent and will always work.
-- Source: IndieWebCamp [http://indiewebcamp.com/]

The general philosophy is that it is easy enough to own your own site, own your own data, and then syndicate it out to any of the variety of content silos that exist (while sucking additionally created follow-on data, such as comments, likes, etc. back into your own site), so that you can simultaneously take advantage of the network effects of these silos while still owning everything and not chancing that it will disappear without warning. I'd highly recommend surfing around the IndieWebCamp site for a bit, but I imagine that most will find it actually describes the way many wished the internet worked.

Now that we've got the background philosophy of the question sorted out, let's take a look at the semantics of the solution. The question is essentially asking about the IndieWeb concept of Publish (on your) Own Site, Syndicate Elsewhere (aka POSSE [http://indiewebcamp.com/POSSE]). The mechanics are somewhat different depending on the home platform on which one builds one's site, but almost all platforms allow one to at least post the "headline" of their post along with a permalink manually. IndieWeb forward platforms like Wordpress, Tumblr, Drupal, and WithKnown either have the functionality to cross-post to twitter automatically or do so fairly easily with simple and free plugins (e.g.: WordPress's ubiquitous plugin has a "publicize" functionality that allows crossposting to major silos like Facebook, Twitter, Google+, Tumblr, and LinkedIn among others). Most of these also have either built in or plugin functionality to pull comments, likes, and reshares from the specific silo back to the original content, so that all of it is memorialized in the same place. For those that need it, the POSSE page at IndieWebCamp (linked above) has a variety of ideas and resources for a variety of platforms.