POSSE – Publish on your Own Site, Syndicate Elsewhere

https://indieweb.org/POSSE

POSSE

POSSE is an abbreviation for 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.

IndieWeb
Nice that we have a name now for something that's pretty much standard and common practice. Not that we necessarily needed a name, but it's still nice to have one.
Agreed, and good to know other people also doing similar processes

> now

The idea is about 10 years old. At least that's when I first heard about it, with relation to RSS. It may go back earlier.

Edit: confirmed by the "See Also" section at the end of TFA.

> something that's pretty much standard and common practice

Is it? How many people publish to their sites small texts that they then syndicate to Twitter/Bluesky/whatever? How many people publish videos to their sites and then syndicate to Youtube?

The idea is not that you necessarily write a Twitter-length post on your website - you can write a full blog post, but then post links back to that post on social media.

I've always liked this idea.

However I am not sure about "perma-shortlinks", for discovery on other sites as the means of networking and discovering content. It seems clunky to maintain as it requires a human or some automation to curate/maintain the links. If a blog removes a link to another blog, then that pathway is closed.

It would be cool if we could solve that with a "DNS for tags/topics" a - Domain Content Server (DCS) e.g.

1. tomaytotomato.com ==> publishes to the DCS of topics (tech, java, travel)

2. DCS adds domain to those topics

3. Rating or evaluating of the content on website based on those tags (not sure the mechanics here, but it could be exploited or gamed)

You could have several DCS for topics servers run by organisations or individuals.

e.g. the Lobsters DNS for topics server would be really fussy about #tech or #computerscience blog posts, and would self select for more high brow stuff

Meanwhile a more casual tech group would score content higher for Youtube content or Toms Hardware articles.

This is just spit balling.

I follow this approach. It's mostly because I want to own the land I build on.

It works well, but it's hard to automate. In the end you must manually cross-post, and both the post and the discussion will vary by community. You end up being active in multiple different communities and still getting little traffic from the effort.

It's not such a great way to drive traffic. On the other hand, it's a wonderful way to work in public.

I like when I read something, and it has links to the "main" discussion on HN/reddit/etc. Most blogs don't have a very active comment field, and if I'm reading it a few days late, it's nice to still be able to find other's thoughts on the matter.

A cool feature for the small web would be:

1. I like your blog and subscribe to its RSS

2. I see new posts in my RSS reader with syndication links to (HN/reddit/twitter/etc).

3. I can go to those places to talk about it.

Low tech version is just linking to those discussions at the bottom of your post I guess.