I found your post through the POSSE'd version on Medium, so cheers for discovery through syndication! But since neither your nor I would "own" this comment and you'd be less likely to see it if I posted it on Medium, I'm replying from my own site instead. Thanks for writing such a nice and lucid piece on the #IndieWeb!

Today, I started experimenting using SNAP as part of my POSSE regimen and noticed the following quirk with syndication-links installed:


SNAP seems to be adding the top line saying "Also on" along with the three written text social networks Facebook, Tumblr, and Twitter (verified by disabling SNAP), while syndication-links plugin adds the bottom line saying "Syndicated to:" followed by the much prettier social media icons. (For comparison, the Google+ and LinkedIn icons are as a result of manually placing the URLs into syndication-links's box on the post's editor.)

Naturally, I'd much prefer (and I'm sure most others would as well) syndication-links's method of output given that it's more flexible and customizable. The question is how can one hide/disable the output from SNAP, but while still keeping the additional URL data they're backporting from POSSE for display into syndication-links?

Is it worth adding a configuration toggle in the settings to disable the SNAP output version for future cases/conflicts like this?

@kevinmarks Reminiscent of @JeffJarvis idea to allow content to be more flexible/portable (including ads) so it has a better post-POSSE life

@kevinmarks @benwerd: Native posts within a particular silo always seem to get better engagement, which is an issue with POSSE sometimes.

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.