#Syndicate 2012 wiki how to#
#Syndicate 2012 wiki install#
#Syndicate 2012 wiki manual#
#Syndicate 2012 wiki software#

Software and libraries to implement POSSE:

h-entry_to_text is a method of generating a plain text representation from an arbitrary h-entry.

SMS or push notifications) may require a pure plain text representation.

#Syndicate 2012 wiki install#

Chris Aldrich uses a WordPress plugin WordPress Crosspost to POSSE from a self-hosted WordPress install to.How does do it? (all his articles are manually POSSEd to ).link to the syndicated copy from the original in a posts-elsewhere section on your post.

Once you have posted the copy to the silo, you should:

#Syndicate 2012 wiki how to#

The details of how to do so vary per destination. permashortlink or permashortcitation) back to your original. In general, when your content posting software posts something, it should also post a copy to the silo destinations of your choice, with an original post link (e.g.

#Syndicate 2012 wiki manual#

manual retweets, RSS bots etc.), when the copies link to your original posts, search engines figure that out by following those links back to the original and ranking it higher. If/when your POSSE copies are themselves copied by others and (re)posted elsewhere (e.g.

Better ranking for your original posts.

mindlessly copy from your POSSE copies and repost, they also copy the link back to the original, and thus provide more distribution for people to find and view your original post. discovery of your original content from the copies on 3rd party services is enabled by the permashortlinks to your originals posted on said services

allows taking advantage of other services' social layers and aggregation features while storing the canonical copy of your content on your own siteД¬ommon POSSE practice is to link from POSSE copies to your original, using a permashortlink.

backfeed can be used to pull in (reverse syndicate) responses from other services.

Facebook still has very poor search results). Twitter for a while only showed recent tweets in search results. Searching public content on your own domain (with any web search engine of your choice) works better than depending on silos exclusively to search your posts (e.g. By posting content first to your own site (and thus creating a for it), copies that you post on 3rd Party services can link or cite the original on your site (see syndication_formats and POSSE Notes to Twitter) Canonical URLs to your content are on your domain. By posting first on your own site, you create a direct ownership chain that can be traced back to you without any intervening 3rd party services (silos) TOS's getting in the way (which is a vulnerability of PESOS). On the contrary with PESOS, when the 3rd party site is down, you are unable to add content. By posting directly to your own site, you're not dependent on 3rd Party services to do so - if you can access your site, you can publish your content. POSSE is considered a robust and preferable syndication model for the following reasons: It's a key part of why and how the IndieWeb movement is different from just 'everyone blog on their own site', and also different from 'everyone just install and run (YourFavoriteSocialSoftware)' etc. Additionally, if federated approaches take a POSSE approach first, they will likely get better adoption (everyone wants to stay in touch with their friends), and thereby more rapidly approach that federated future. By focusing on actual social relationships that matter to people rather than architectural ideals, from a human perspective, POSSE is more important than federation. POSSE is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future.ДЇriends are more important than federation. Stay in touch with friends now, not some theoretical future. silo aggregators like Facebook, Tumblr, Twitter, etc.). POSSE lets your friends keep using whatever they use to read your stuff (e.g. Let your friends read your posts, their way.

9 POSSE as methodology for non-web scenarios.

6.1 Worry about search engines and duplicates.