syndication formats

Content hosted under your domain should be presented as semantically marked up HTML+microformats. If you have not yet done this, go do it now!

Here's an example of a densely marked-up note:

http://public.waterpigs.co.uk/images/syndication/semantic-microblog.png

and here's it's code:

Once you have well-marked-up data under your domain, you should make it available as a feed, and you'll probably want to syndicate it out to 3rd party services.

3rd party services will inevitably require your data to be of lower quality than it is under your domain (length limit, no microformats, no markup). For example, here's a representation of the above example as it appeared on twitter:

http://public.waterpigs.co.uk/images/syndication/nonsemantic-microblog.png

No microformats on the web version, a truncated link, network-specific user references and no  markup on the alt.

Feeds
When you're syndicating content using feeds (atom, activitystrea.ms), preferably use the same/very similar markup to you do on the web. This has the following advantages:


 * Dumb feed readers still get lots of useful links, images as tags, working youtube embeds etc.
 * Smart feed readers get a vast amount of useful data, e.g.

Twitter
When syndicating content to Twitter, bear the following in mind:


 * Not only the 280 char limit, but you may want to allow for the extra characters added when retweeting
 * No HTML is displayed, but most clients will auto-parse image links into images, video links into players
 * #tags will be parsed into twitter-specific tag URLs
 * @names will be parsed into twitter-specific user references

Implementation Details


 * I write my notes using tweet microsyntax, send the raw copy to twitter and turn the microsyntax into more useful formats (e.g. @name ->, #tag to   url) --Waterpigs.co.uk 12:26, 22 September 2012 (PDT)

Truncation and Backlinks
The exact formatting of backlinks (see POSSE) is varied in nature. The user should immediately be able to discern whether or not there’s any extra content to be seen if they click through (clicking through to find content repeated, not amplified is a known usability issue.

Syndicating Notes (AKA tweets)
If the content has to be truncated for syndication, add an ellipsis and the URL for the rest of the content, e.g:

"Dear #ireality #ireality2012 speakers, what to do about those trying to revert to the past? eg undo teaching ... http://ttk.me/t4Kp1"

If adding the permalink doesn’t cause the content be to be truncated, put it in parentheses, e.g:

"Built and released today: ~ THE TRUNCENATOR ~ github.com/indieweb/php-truncenator #indieweb (waterpigs.co.uk/notes/356)"

A variation of this is to use Whistle-like short URLs and separate the domain from the path by a space, e.g:

"If Twitter is for posting updates, why do 'Updates from Twitter' use email? http://i.qkme.me/3r3ove.jpg #philosoraptor (ttk.me t4LA1)"

The advantage of this is that Twitter does not wrap it in a t.co URL, leaving it easier for people to retrieve if when t.co goes down. Also, it’s 14 characters long, leaving 6 more than you would have with a 20-char t.co URL (which is only likely to go up)

Syndicating Blog Posts
There are a whole load of different methods in use to indicate a blog post. The commonest is the Title-colon-link pattern, e.g:

"I dream of BBSes: http://www.onebigfluke.com/2012/09/i-dream-of-bbses.html"

People Formatting Back–links Like This

 * Aaron Parecki (e.g: amplified note repeated note blog post)
 * Barnaby Walters (e.g: amplified noterepeated note blog post)
 * Brett Slatkin (e.g: blog post)
 * Tantek Çelik (e.g: amplified note repeated note blog post)
 * …Add yourself if you use this format

Tools

 * ~ THE TRUNCENATOR ~ (PHP) is a highly-configurable function for nicely squishing content and a back–link into a given character limit