Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content. (View Highlight)
Let your friends read your posts, their way. POSSE lets your friends keep using whatever they use to read your stuff (e.g. social media silos like Instagram, Tumblr, Twitter, Neocities, etc.). (View Highlight)
Stay in touch with friends now, not some theoretical future. POSSE is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future. (View Highlight)
Friends are more important than federation. By focusing on relationships that matter to people rather than architectural ideals, from a human perspective, POSSE is more important than federation. 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. (View Highlight)
POSSE is beyond blogging. 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. monoculture solutions. (View Highlight)
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. On the contrary with PESOS, when the 3rd party site is down, you are unable to add content. (View Highlight)
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). (View Highlight)
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) (View Highlight)
Better search. 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. Twitter for a while only showed recent tweets in search results. Facebook still has very poor search results). (View Highlight)
backfeed can be used to pull in (reverse syndicate) responses from other services (View Highlight)
Common POSSE practice is to link from POSSE copies to your original, using a permashortlink. Here are a few reasons why: (View Highlight)
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 (View Highlight)
Subvert spammers who copy your posts. When spammers (e.g. @sin3rss) 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. “2011-01-09 internet aikido” of a sort. (View Highlight)
Better ranking for your original posts. If/when your POSSE copies are themselves copied by others and (re)posted elsewhere (e.g. 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. (View Highlight)
Once you have posted the copy to the silo, you should:
• link to the syndicated copy from the original in a posts-elsewhere section on your post (View Highlight)
The best user interface (UI) is automatic, dependable, and invisible. If you can implement POSSEing in a way that always does exactly what you want, predictably, then no explicit UI is needed. (View Highlight)
Twitter is perhaps the most popular POSSE destination and a good place to start. (View Highlight)
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. (View Highlight)
IFTTT allows automatically reposting content with an RSS or Atom feed to a number of silos incuding Twitter, Tumblr, and Facebook (View Highlight)
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 (View Highlight)
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 (View Highlight)
The server publishes the content, generates a permalink and summary (and/or customized content suited to 3rd party services) if necessary (View Highlight)
• User only has to interact with one site over the internet, their own
• Syndication can be done fully automatically by the serve (View Highlight)
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. (View Highlight)
POSE, Publish Once Syndicate Everywhere, was a broader predecessor of POSSE that also included publishing once on one particular silo, and then syndicating out to other silos. (View Highlight)
A similar but opposite approach is PESOS where content is posted first to 3rd party services and then copied/syndicated into a personal site. (View Highlight)
PESETAS is like PESOS but copying/syndicating everything to a particular silo (without any involvement of a personal site). (View Highlight)
If a POSSE destination allows updates/edits, then when you edit your post, you could propagate that update to the downstream POSSE copy as well. (View Highlight)