A place to cache linked articles (think custom and personal wayback machine)
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

index.md 27KB

title: POSSE - IndieWebCamp url: https://indiewebcamp.com/POSSE hash_url: 5fc43f9c6c

POSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, a content publishing model that starts with posting content on your own domain first, then syndicating out copies to 3rd party services with permashortlinks back to the original on your site.


POSSE lets your friends keep using whatever they use to read your stuff (e.g. silo aggregators like Facebook, Tumblr, Twitter, etc.).

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 StatusNet/Diaspora” etc. monoculture solutions.

POSSE is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future.

As such, POSSE is more important than federation. In addition, 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.


POSSE is considered a robust and preferable syndication model for the following reasons:

  • Ownership. 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).
  • Reduce 3rd party dependence. 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
  • Own canonical URLs to your content. Canonical URLs to your content are on your domain.
  • Copies can cite the original. By posting content first to your own site (and thus creating a permalink 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)
  • Discovery of your original content. discovery of your original content from the copies on 3rd party services is enabled by the permashortlinks to your originals posted on said services
  • Better search. Searching public content on your own domain (with any web search engine of your choice) works better than depending on Twitter exclusively to search your tweets.[1]. And 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.
  • backfeed can be used to pull in (reverse syndicate) responses from other services
  • allows taking advantage of other services’ social layers and aggregation features while storing the canonical copy of your content on your own site

How To Implement

In General

In general, when your content posting software posts something, it should also post a copy to the silo destinations of your choice, with a permashortlink (or permashortcitation) back to your original.

The details of how to do so vary per destination. See the silo-specific sections below.

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

  • link to the copy from the original in a posts-elsewhere section on your post.


Twitter is perhaps the most popular POSSE destination and a good place to start.

If you can start posting notes (tweets) to your own site and POSSEing to Twitter, instead of posting directly to Twitter, you have taken a big step towards owning your data.


  • API Access - posting new tweets works nicely due to permanent API tokens, and the return value contains a URL to the posted
  • Supports very complete web action endpoints, so semi-manual posting is easy to implement

See POSSE to Twitter for details on how to POSSE both notes and articles (blog posts) to Twitter.


  • API Access - New posts can be created through the API using the Publishing API
  • A web action endpoint (https://www.facebook.com/dialog/feed) is supplied by the Feed social plugin for semi-manual posting. Requires a facebook app id, but no authentication. It accepts a callback URL, to which it redirects with ?post_id GET param set, from which a URL can be constructed.

Google Plus

  • No write API (yet)
  • There are several endpoints which can be used as web action dialogs, but none of them support callbacks, so it’s trick to get the URL of the posted copy.


  • how does iamshane.com do it? (all his articles are POSSEd to Medium)


  • how does iamshane.com do it? (all his articles are POSSEd to WordPress)

Plain Text Notes

Some destinations (e.g. SMS or push notifications) may require a pure plain text representation.


Software and libraries to implement POSSE:

  • PHP
    • The POSSE namespace in php-helpers (might be moved to a separate package) contains various truncation, preparation and syndication functions including HTML => plaintext µblog syntax converter


Publishing Flows

There's at least two ways to implement a POSSE content posting flow:

Client to site to silo

  • The user writes a piece of content using a publishing client
    • Optional: client provides UI for selecting which 3rd party services to push to if it knows about them, with optional customizations for per service
  • Having finished the content, the user publishes content to their server (optionally: with metadata of which 3rd party services and any customizations thereof)
    • Optional: client can generate a permalink knowing the state of the server, and publish to that permalink
  • The server publishes the content, generates a permalink and summary (and/or customized content suited to 3rd party services) if necessary
  • The server posts copies with permalinks to 3rd party services


  • User only has to interact with one site over the internet, their own
  • Syndication can be done fully automatically by the server


Client to site and silo

  • The user writes a piece of content using a publishing client
  • Having finished the content, the user publishes it to their server
  • The client queries the server for the URL of the content it just pushed
  • The publishing client presents the user with an interface for selecting:
    • Which 3rd party services to publish to
    • The exact content published to the services, pre-filled with a summary based on the produced content
  • The user selects the services and submits the form
  • The publishing client posts the content summaries out to the 3rd party services


  • More user control over timing and editing of copies of content to 3rd party services


  • Syndication requires a manual step each time
  • Dependent on client connectivity directly to 3rd party services (problematic in flakey mobile situations, or when client is publishing using domain-censored internet access).

IndieWeb Examples

The following IndieWebCamp participants’ sites support a POSSE architecture. If you have an implementation, add it, make screenshots or a screencast or blog about it and post the details/link here. In date order (earliest first) :


Tantek.com as of 2010-01-01[2] (2010-01-26 Twitter syndication started[3] and caught up[4][5]). Tantek Çelik implemented POSSE in Falcon on tantek.com.

  • all self-hosted posts are openly with PuSH v0.4 + h-feed and Atom real-time syndicated with a PubsubHubbub hub to StatusNet, other subscribers etc. (also to Google Buzz til it shutdown)
  • note (and article titles), reply, RSVP posts are snowflake copied by the personal site server to Twitter with permashortlink citation links/references (see Whistle for details) back to the original. Copies of notes to Twitter are also automatically recopied from there to Facebook.
    • RSVPs to Facebook events are “copied” (more like propagated) to Facebook using Bridgy publish
  • likes of tweets are “copied” (more like propagated) to Twitter using Bridgy publish

Barnaby Walters

Waterpigs.co.uk as of 2012-03-12. Barnaby Walters implemented POSSE over at waterpigs.co.uk

  • as of 2012-09-25 all collections (notes, articles, activity) are PuSH-subscribable feeds.
  • Using the Client to Server to 3rd Parties flow --Waterpigs.co.uk 06:08, 25 September 2012 (PDT)
  • Syndicating to Twitter + Facebook
  • As of 2014-06-19 Taproot can now optionally post additional POSSE tweets when updating a note or article — example of updated note and POSSE tweet for the update. Note that Bridgy successfully backfeeds silo interactions from the update tweet as well as the original POSSE tweet

Brennan Novak

brennannovak.com as of 2012-07-01[6][7]. Brennan Novak implemented POSSE on his site brennannovak.com with copies posted to Twitter and Facebook

Aaron Parecki

aaronparecki.com as of 2012-08-19[8][9]. Aaron Parecki implemented POSSE on his site aaronparecki.com with copies posted to Twitter containing permashortlinks back to originals on his own site.

Sandeep Shetty

User:Sandeep.io First post POSSE’d on 2012-11-05. I primarily syndicate to Twitter using a very lo-fi solution of adding silo (Facebook, Twiiter, Google+) provided share links to each post that I can manually click to prefill content, edit and post. I’ve avoided API integration because of the extensive experience I’ve had using Facebook API and dealing with it’s random changes. “Integration” has high costs sometimes so I keep it as simple as possible.

Ben Werdmuller

werd.io as of 2013-05-31 [10]. Ben Werdmuller implemented POSSE in his idno platform via plugins. New content has an associated Activity Streams object type; POSSE plugins listen for post events associated with those object types and syndicate appropriately.

  • Notes and articles are syndicated to Twitter and Facebook
  • Images are syndicated to Facebook, Flickr and Twitter
  • Places are syndicated to Foursquare
  • More plugins are very easily possible; the Foursquare plugin took about an hour to build

Shane Becker

iamshane.com - need to copy example from rel-syndication page

Glenn Jones

glennjones.net as of 2014-01-14 Glenn Jones The blog implemented POSSE using a new version of transmat.io system. New content added to transmat is associated with objects types. A POSSE twitter plugins listens for post events syndicating content. At moment only notes are syndicated.

Jeremy Keith

adactio.com as of 2014-05-27 Jeremy Keith has implemented POSSE using his own custom CMS.

Shane Hudson

shanehudson.net as of 2014-09-19 Shane Hudson has implemented POSSE to Twitter for Craft CMS.

  • Previously working on Wordpress but he was not keen on the UX.
  • Has reply contexts working but has to manually copy the ID.
  • Not yet POSSEing photos but plans to.
  • Currently he has to manually copy the tweet from the main text box to a 140 character limit tweet text box. He plans to make that automatic.

… add more here …

… Add a link to your POSSE–enabled site and the date you started syndicating copies of your content out to 3rd party social sharing/publishing services.

Partial POSSE sites

Sites which only POSSE some of their content, and still post directly to the same silo they POSSE to.

Other partial POSSE sites:

  • User:Hupili.net implements a partial POSSE with the following setups:
    • SNSAPI is a lightweight middleware to unify the data structure and interfaces of different social networking services. It gives the scripting flexibility for developer users to manipulate social silos.
    • SNSRouter is a web UI built upon SNSAPI where one can read an aggregated timeline from different sites, mass forward messages, and update statuses on all channels.
    • Part of my daily usage is to go to my running SNSRouter, read messages and update statuses on it. The new status is written to the RSS feeds, http://hupili.net/feeds/all.xml , and other silos. ( This feed is indeed a mix of POSSE PESOS )
    • As is said in one of the description paragraph above, this model is not truly POSSE. One can not (hardly) distinguish original/ syndicated status. I’m planning to put a page with permlink on my site upon each status update and then use SNSAPI to syndicate to other silos.

Other Approaches


A similar but opposite approach is PESOS where content is posted first to 3rd party services and then copied/syndicated into a personal site.

If exact copies of content are posted on both a personal site and 3rd party services, there’s no way to tell (short of comparing possibly non-existent sub-second accurate published dates) whether a site is using POSSE or PESOS. Sites can provably support POSSE by including perma(short)links in syndicated copies that link/reference back to published originals.


PESETAS is like PESOS but copying/syndicating everything to a particular silo (without any involvement of a personal site).

For example, most silos support cross-posting to Twitter, thus you could connect everything to your Twitter account and always (auto-)cross-post there to keep a copy.

E.g. Tumblr has a UI for cross-posting to Twitter. See Webapps StackExchange post for documentation and screenshots of UI.

Tumblr is a better PESETAS destination however, since it is well established, allows for a wider variety of content, and allows more text, and links to URLs directly instead of linkwrapping them like Twitter does.



All of the above, and to date (2013-222), POSSE has solely described syndicating the Creation of content on your site (publishing) to other sites. This model has been quite successful and perhaps may be sufficient.

However, it is worth exploring the potential utility of a full CRUD protocol for POSSE.


Create is the POSSE default. You create content on your site, you POSSE your creates to other sites. All of this is described above, and in silo-specific details on silo pages.


Read as a verb is interesting when applied to POSSE.

At a minimum, it’s useful to implement storing links to syndicated copies of your content to provide for the future possibility of reading from downstream POSSE copies.


Actual direct uses of Reading from downstream POSSE copies:

  • reverse-syndication / backfeed of activity around the POSSE copy onto your original:

In addition, keeping a rel-syndication link to the POSSE copy enables deleting it to perform an Update or a Delete action, as described in the following sections.


If a downstream service allows updates/edits, then when you edit your post, you could propagate that update to the downstream POSSE copy as well. (Any existing POSSE destinations that allow this?)

It would be possible to POSSE updates to Twitter (or any other silo that disallows edits to posts) by deleting the POSSE tweet and reposting.

Consider only POSSEing updates to Twitter:

  • if no one has replied to it yet (otherwise you'd break a threaded conversation on Twitter)
  • if your changes would be shown in the truncated copy on Twitter (i.e. if your changes are past the 140 (more like 120) character horizon, no point in churning the Twitter copy).
  • within a very short time window, maybe like 2-5 minutes, because otherwise the update will be seen as a duplicate to people who are reading you on Twitter.

All of these concerns are regarding the experience that you provide to your friends reading your tweets on Twitter, which of course should be the whole (design) reason you're bothering to POSSE to Twitter in the first place.


Deletes seem fairly straightforward to POSSE, especially to services which themselves propagate deletes to clients.

E.g. one can delete a note on Twitter at any point.

Similar to updates, consider:

  • if there are already replies to a POSSE copy (or activity like favorites/retweets), consider keeping it to keep conversation threading (and others' favorites/retweets).

However, if you really feel like deleting the content from your site and POSSE copies (e.g. on Twitter), go ahead and do so.

Perhaps this is an opportunity for the UI for the deletion of a post to check to see if there's been any activity (replies, favorites, retweets) on the POSSE copy before performing the delete. One possible implementation could involve the UI informing the user of this activity (or lack of it) and reconfirming the delete request on a per-service basis.


Worry about search engines and duplicates

Q: Do we need to worry about search engines penalizing apparently duplicate posts?

A: That's why the POSSE copies SHOULD always link back to the originals. So that search engines can infer that the copies are just copies. Ideally POSSE copies on silos should use rel-canonical to link back to the originals, but even without explicit rel-canonical, the explicit link back to the original is a strong hint that it is an original.

This is also an advantage of POSSE over PESOS. With PESOS - there's no way to tell what's the original and what's the copy - so they do look like duplicates.

POSSE-post-discovery and backlinks

Q: Brid.gy can use posse-post-discovery to find the relationship between a syndicated post and the original when there is not explicit link. Does this mean I should stop adding backlinks to syndicated copies?

A: POSSEing without a backlink is considered a last resort, and has some costs associated with it. See posse-post-discovery#Tradeoffs for more details.

POSSE or Send Webmentions First

In short, POSSE first, then send webmentions.

See: Webmention FAQ: POSSE or Send Webmentions First for details and reasoning.