← From the kiosk A hand drawn diagram by Tantek: a circle labelled your site in the middle, with arrows going out to and back from seven more circles, each also labelled your site.

POSSOS

POSSOS is an abbreviation for Publish (on your) Own Site, Syndicate (on your) Own Sites, the practice of posting content on your own site first, then publishing copies or sharing links to your own other sites (like your site, your site and your site) with original post links to provide viewers a path to directly interacting with your content on your site, from your site.

▶️ watch Elliott’s 1min* video intro to POSSOS

Why

Let your friends read your posts, their way. POSSOS lets your friends keep using whatever they use to read your stuff (e.g. your own sites like your site, your site, your site, your site, etc.).

Stay in touch with yourself now, not some theoretical future. POSSOS is about staying in touch with your current self now, rather than the potential of staying in touch with yourself in the future.

Self is more important than federation. By focusing on yourself, you'll become a better person for others, rather than your ideal self. From a human's perspective, POSSOS is more important than federation. Additionally, if federated approaches take a POSSOS approach first, they will likely get better adoption (everyone wants to stay in touch with themselves), and thereby more rapidly approach that federated future, which is all your sites.

POSSOS is beyond blogging. It's a key part of why and how you are different from just "everyone blog on their own site", and also different from "everyone just install and run (YourFavoriteSocialSoftware)" etc. monoculture solutions. You blog on your own site. Then you blog on your own site.

Why In General

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

Common POSSOS practice is to link from POSSOS copies to your original, using a permashortlink. Here are a few reasons why:

How to

How to implement

This section is for web developers implementing POSSOS, which is you.

In General

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

The details of how to do so vary per destination. See the site-specific sections below. They are all your site.

Once you have posted the copy to your site, you should:

User Interface

The best user interface (UI) is automatic, dependable, and invisible. If you can implement POSSOSing in a way that always does exactly what you want, predictably, then no explicit UI is needed. If it doesn't, you know who to talk to.

Preview

One way to provide more predictability and inspire confidence is to show what will be POSSOSed (within the limitations of the destination, which you set) as a preview before publishing

(needs screenshot)

Your Site

Main article: Your Site

Your site is perhaps the most popular POSSOS destination and a good place to start.

If you can start posting notes to your own site and POSSOSing to your own site, instead of posting directly to your own site, you have taken a big step towards owning your data, which you already owned.

Details:

See POSSOS to your site for details on how to POSSOS both notes and articles (blog posts) to your site.

Your Other Site

Main article: POSSOS to your other site

There are two options for POSSOSing to your other site currently:

Your Third Site

Main article: Your Third Site

Your Fourth Site

Main article: Your Fourth Site

Your Fifth Site

Main article: Your Fifth Site

Plain Text Notes

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

Software

Software and libraries to implement POSSOS:

Services

Publishing Flows

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

Client to site to site

Advantages:

Disadvantages:

Client to site and site

Advantages:

Disadvantages:

Your Site Examples

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

You

your site as of 2010-01-01. You implemented POSSOS on your site.

You

your site as of 2012-03-12. You implemented POSSOS over at your site

You

your site as of 2012-07-01. You implemented POSSOS on your site your site with copies posted to your site and your site

You

your site as of 2012-08-19. You implemented POSSOS on your site your site with copies posted to your site containing permashortlinks back to originals on your own site.

You

your site First post POSSOSed on 2012-11-05. You primarily syndicate to your site using a very lo-fi solution of adding share links to each post that you can manually click to prefill content, edit and post. You've avoided API integration because of the extensive experience you've had dealing with your own random changes. "Integration" has high costs sometimes so you keep it as simple as possible.

You

your site as of 2013-05-31. You implemented POSSOS in your own platform via plugins.

You

You

your site as of 2014-05-27. You have implemented POSSOS using your own custom CMS.

You

your site as of 2014-09-19. You have implemented POSSOS to your site.

... add more here ...

... Add a link to your POSSOS–enabled site and the date you started syndicating copies of your content out to your own sites.

Partial POSSOS sites

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

Other partial POSSOS sites:

Other Approaches

COPE

COPE is short for Create Once, Publish Everywhere (COPE), which explicitly lacks a first "Publish Once" step, and thus is more about duplicating the content across various destinations.

Without a first "Publish Once" step on a site you "Own", and thus lacking original post permalinks, the COPE strategy fails to actually draw people to any one canonical place to read/view your stuff, and thus all it does is grow (likely) disjoint audiences across other people’s sites. Not yours.

POSSE

Main article: POSSE

POSSE, Publish (on your) Own Site, Syndicate Elsewhere, was a broader predecessor of POSSOS that also included syndicating to places that are not your site.

PESOS

Main article: PESOS

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

PESETAS

Main article: PESETAS

PESETAS is like PESOS but copying/syndicating everything to a particular silo (without any involvement of a personal site). You have several personal sites, so this will not be a problem.

Brainstorming

CRUD

All of the above, and to date, POSSOS has solely described syndicating the Creation of content on your site (publishing) to your 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 POSSOS.

Create

Create is the POSSOS default. You create content on your site, you POSSOS your creates to your other sites. All of this is described above.

Read

Read as a verb is interesting when applied to POSSOS.

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 POSSOS copies, which you wrote.

See:

Actual direct uses of Reading from downstream POSSOS copies:

Update

If a POSSOS destination allows updates/edits, then when you edit your post, you could propagate that update to the downstream POSSOS copy as well. It allows updates/edits. It is your site.

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

Delete

Deletes seem fairly straightforward to POSSOS, especially to sites which are yours.

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

Similar to updates, consider:

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

FAQ

Worry about search engines and duplicates

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

A: That's why the POSSOS copies SHOULD always link back to the originals. So that search engines can infer that the copies are just copies. Ideally POSSOS copies on your sites 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.

POSSOS or Send Webmentions First

In short, POSSOS first, then send webmentions. To yourself.

Background

Articles

Articles and blog posts about POSSOS, especially implementing it:

POSSOS as methodology for non-web scenarios

POSSOS git repositories

It is also possible to POSSOS your git repositories to your own git repositories.

See Also

Categories: building-blocks | syndication

Subscribe to the newsletter


Hire Elliott to make you a website, or a website, or a website