alt Hacker NewsPublish on your own site, syndicate elsewhere
Comments
Add yourself to so called slashpage (https://slashpages.net) directories. I discovered a lot of personal blogs over the years from those.
Like:
- https://chrisburnell.github.io/interests-directory/
- https://bukmark.club/directory/
I find browsing and discovering fun. So, after years of lurking I decided to make my own directory. It is called Top Four (https://topfour.net).
A /top4 page is a personal webpage where you can share your definitive ranked list of your top 3 favorites and an honorable mention. In a specific topic, such as movies, albums, snacks, games, or anything else you feel strongly about. Or read the announcement: https://peterspath.net/blog/project-top-four/
We followed this practice at a Non-Profit I volunteered for some years ago. For us, it was motivated by a few reasons:
- we trained the community around us to look to our website first for the most recent news and information
- we did not want a social media platform to be able to cut us off from our community (on purpose or accident) by shuttering accounts or groups
- we did not want to require our users have accounts on any 3rd party platforms in order to access our postings
- but we still wanted to distribute our messaging across any platforms where large groups of our community members frequently engaged
Another aspect of our process that was specific to our situation and outside of POSSE - we only posted one topic/issue/announcement per blog post. We had a news letter that would summarize each of these. Many organizations like ours would post summaries of many things to a single blog post, basically the same as the newsletter. However, this was cumbersome. For example, if someone in the community had a question, it was much clearer to link to a single post on our site that answered the question AND ONLY answered that question. It made for much better community engagement, better search engine indexing, cleaner content management, and just a better experience for everyone involved.
One of the biggest steps down in Facebook history was their removal of RSS syndication. There was a time in the past when you could subscribe your Facebook account to external RSS feeds. The entries in those feeds would create new content on your "Facebook wall". This essentially let you use any third party that supported RSS to publish content into your Facebook feed.
Facebook removed that feature. The effect of this was that people had to create content within facebook instead of outside it. This reoriented the flow of content creation so that it must originate inside of Facebook, removing the ability to use FB as a passive consumer of content created in a workflow where the creators chose the entire flow.
IMHO this is one of the biggest steps down ever in FB history. It was one of the biggest attacks on the open web, and I'm sad to say that it mostly worked, and the internet at large is worse as a result.
I must say, it's delightful to see this on the front page of HN.
A lot of people have been following indieweb POSSE principles for almost 15 years: publishing on their own site and syndicating elsewhere. I built my own platform for it that I used for 11 years, but you can use just about anything.
What's superb about the indieweb principles is that they're as simple as the web itself. It's worth digging into microformats, webmention, micropub, and the other lightweight standards the community has nurtured. It's all really good work that will become even more useful as more people turn away from centralized social media and AI-saturated services towards human websites. The indieweb is a slow burn but a really vibrant, growing, human community.
This strategy is an alternative to PESOS (Publish Elsewhere, Syndicate (to your) Own Site) [0]. I really like this read on the indieweb website, it explains well why adopt this strategy for federation and emphasizes that "Friends are more important than federation", something a lot of nerds and hackers forget when defending their ideals.
I really like this philosophy. I've been using it for a couple of years now - everything goes on my personal site, then I post links on Mastodon, Bluesky and Twitter and sometimes (if I remember to do so) LinkedIn, plus copy and paste it all into a Substack email every week or so.
I really need to automate it though - hard on Twitter and LinkedIn but still pretty easy for Bluesky and Mastodon.
I am not so sure. You need to speak in the native voice of each community. A LinkedIn post vs Tweet vs E-Mail are different. You need to get value from the network directly without expecting a click thru. A lot of engagement + authority happens via the network itself
I think it's more accurate to see blogging as a distinct channel from other types of social media + content marketing
Great to see this here. I’ve been using EchoFeed (https://echofeed.app) to syndicate articles from my blog to social media (it uses RSS as the feed source). I also recently learned about POSSEparty (https://posseparty.com) which has more options but is self hosted.
RSS most certainly isn’t dead either. I run pagecord.com (indie blogging app) and the majority of traffic is from a huge variety of feed readers.
I've restarted blogging last year, going from a handful of blog post to, publishing consistently. All content gets published on my blog first. I've seen an ~8x increase of traffic. I was affected by zero-clicks from Google's AI overview, but the bulk of my traffic now comes from RSS readers.
I published a write up just this morning: https://idiallo.com/blog/what-its-like-blogging-in-2025
I've used Twitter to publish my thoughts for years. In the beginning, I'd write multiple threads to get my points across.
Then, when Twitter started supporting longer tweets, I started publishing essays and it got the job done.
But at the end of each year, it was really hard to trace all my posts and write reviews about them. That's exactly what brought me to POSSE. I've been maintaining my blog[1] since early 2020 and it feels really good to know that I own my stuff. Plus, over the years, it has opened up so many doors for me.
Too bad many of these walled-garden platforms have now started to demote posts if they contain external URLs. I'm battling that by posting the links as a comment to the original post, which contains a cover photo of the blog.
[1]: https://rednafi.com
I'd like to have a POSSE setup for video with a landing page, a static image and transcript, a download button for very slowly downloading the video, metadata and links to instantly-available external copies so that I can channel as much of the server costs that video entails to the big platforms.
Has anybody written about adapting POSSE for videos?
Q: While I agree strongly with the philosophy of this article, and twice I have set up static site generators for blogs hanging underneath my top level personal domain markwatson.com, each time I cause I could only blog when sitting at my computer, not when I was using an iPad or iPhone (I limit my daily time at a computer to just a few writing and coding sprints, otherwise I literally put my laptop away - out of sight out of mind).
Does anyone know of any mobile friendly static site generators?
I think I have about 3000 blog articles between Substack and Blogspot.
I take this approach with everything I post, though I only syndicate to Mastodon. I have an RSS and JSON feed for each of the content types (they all have different schema) on my site: posts, links, books, movies, concerts, status updates and a combined feed. I also maintain an ICS calendar subscription of upcoming album releases.
These items, in turn, can be optionally syndicated to Mastodon when published. For status updates, I have a field that supports Mastodon-specific text (for mentions and so forth).
I also expose an oembed endpoint that returns the appropriate data for each content type for platforms that support it.
Everything I read is from RSS feeds I follow via freshRSS. Links are saved to linkding and are transformed into TTS "podcasts" that are sent to audiobookshelf.
EchoFeed is a lovely service to enable this regardless of what service you use to publish on your own site (so long as it supports RSS/Atom/JSON). I've used it to good effect for my blog in the past.
Uplifting to see indieweb.org on HN!
However, I suffer from a lack of high-quality news sources, no matter whether they support RSS. They no longer publish online these days. And, realistically, I am not interested in most post from people I am interested in. So I just manually poll some times a month in my browser.
This parallels the learning paradigm of diving into some topic, write a blog post to solidify, practice, demonstrate your knowledge, and finally promote via social media. Which parallels the origin story of sharing your scientific research. It's The Way of knowledge on the internet.
I've noted here before a course from Arlington UT about this on Edx "Data, Analytics, and Learning" (2014).
Nice to have another way of describing this pattern of writing and publishing, even if it does have a funny name POSSE.
https://news.ycombinator.com/item?id=46015121 https://www.pure.ed.ac.uk/ws/portalfiles/portal/19117279/CSC...
A related idea that I'd like to see more people do. If you have 10-20 tweets on a subject, plug the holes and turn them into an essay on the real internet. My first step in writing https://news.ycombinator.com/item?id=46452763 was to copy a bunch of tweets into a doc.
Micro blogging is a great way to brainstorm and iterate on your thoughts over time, but eventually you have enough material to graduate from micro blogging to blogging, and more people should do it.
I don't do any syndication so my self-published site is simply a POS :'(
Somewhat related, predictions for the future of the web by IWC contritbutors:
Very similar to what I’m building with opal editor. The “site” is static markdown which lives and is stored in your browser, css, images, markdown and html. You can keep it as is with markdown or compile to html. From there you can easily push to vercel GitHub cloudflare netlify. Cheating the server less bit of it by using CORS proxies
https://github.com/rbbydotdev/opal
MIT and open source no documentation yet. But coming very soon
I just started building my own website today with Django. I’m doing it because I just enjoy doing it. Most of my work is in data and ML infrastructure and it is just killing me. Working on the front end has opened my mind to possibility and given me new inspiration.
I love hn and was inspired by all the devs who have their own site. I was drowning in work, but put the Django architecture together on vacation, started putting things together today and it’s been a blast.
I don’t enjoy social media and was thinking to posse intrinsically.
I appreciate this post and the authors perspective.
I recently found out about https://micro.blog/ which I think is in a similar vein (https://micro.blog/about/indieweb), but as a hosted service.
Just discovered https://posseparty.com/ to ease your cross-posting.
Read through the comments. Added RSS and subscribe to my blog!
I'd prefer to write markdown, publish to my static site, and cross-post to social media. I imagine I'd also want to get an overview of - or make an ad-hoc post from - one of several accounts on one of several platforms.
I came across Posse Party and Postiz, both of which are self-hosted. It doesn't seem like either is built for this use case.
Which direction would you go in?
Never stopped doing it. And my resolve strengthened when most blogs started doing summary feeds to force people to visit —- I kept doing full text feeds as a matter of course, and if it wasn’t for the Twittergeddon, I would still be automatically posting to Twitter (now I do it to Mastodon - https://mastodon.social/@taoofmac)
> Syndication can be done fully automatically by the server
At the risk of stating the obvious: this can get tricky, many popular social media platforms restrict automated posting. Policies around automation and/or api usage can change often and may not even be fully public as some might overlap anti spam measures.
reading how indie bloggers want to syndicate to big media that consistently crushes their dreams is kinda wild
>syndicate elsewhere
That's almost a job in itself because you have to constantly make sure not to get shadowbanned. This is probably only an option for people who already use "social media" sites in the first place. Putting a link to your site in forum signatures was the way to go. Unfortunately, forums are 99% dead.
The concept seems trivial and widely used by many existing bloggers (and the default for most media outlets) so I feel like I'm missing something.
What blog systems (either self hosted or easy to move) do folks recommend nowadays? I'm not interested in spending much time tinkering and updating, but have enough sysadmin experience to host one myself. Was last using blogger, though trying to de-googlify my life slowly
Downside is “elsewhere” is going to cut your reach when you post a link because they want their users to stay in their estate.
A problem I would like to see solved, is how I can post something on my site first, but still use BlueSky as a commenting platform.
I guess it could just be done as a multi phase post, as janky as that is.
Doesn't work with a lot of subreddits though, which ban posting links to your own site.
I really want to implement this, but i havent been able to figure out how to do it for Instagram (the only social media that is really relevant in my friend circle) and whatsapp/signal groups other than doing it manually. If anyone has tips, especially for Insta let me know...
Posse what? You can literally publish on your own site and syndicate elsewhere using anything whatsoever, including typing .html files into /var/www, if that's your thing.
Does this have a negative impact on SEO or search results in general? I'm clueless about this.
Because RSS readers are coming up in comments, if you are using one, which one would you recommend? For Linux AND Android?
You can tell it's a good idea because Facebook and other "big enough to crush instead of cooperate" media sites down-rank you for doing it
The concept is sound, but the syndicate part is becoming increasingly hostile to maintain. I used to have scripts that auto-posted to twitter, facebook and reddit. Over the last two years, almost all of those broke due to API paywalls or aggressive bot detection.
I've found that "POSSE" is shifting more toward "Publish on Own Site, Manually Link Elsewhere."
Paradoxically, ActivityPub (mastodon/fediverse) is the only place where true automated syndication is still reliable. I think the future of POSSE isn't trying to hack together API keys for walled gardens, but treating your personal site as a fedi instance so the syndication is native.
Philosophically this is what we need more, but linkedin is absolutely tanking engagement for posts that have links.
I still feel RSS was the pinnacle. Of course it’s a personal preference, but I much prefer letting people pull my content than pushing it onto them.
I really wish Bsky/mastodon has something like RSS so I can static host them for both publishing and aggregating .
Don't most social platforms tank reach if you add a link to your post or as a first comment?
It’s almost like HN is a great platform for the POSSE model!
Awesome share thanks for the link. Will send to a family member who is looking to gain viewership with their writing - they usually post on medium I think.
Is it really worked as Broadcast on other Blogs
How do we deal with the fact that billionaires’ social media platforms reduce the reach of posts with links? Will we always have our posts throttled?
Also, don't forget to set up an RSS or Atom feed for your website. Contrary to the recurring claim that RSS is dead, most of the traffic to my website still comes from RSS feeds, even in 2̶0̶2̶5̶ 2026! In fact, one of my silly little games became moderately popular because someone found it in my RSS feed and shared it on HN. [1]
From the referer (sic) data in my web server logs (which is not completely reliable but still offers some insight), the three largest sources of traffic to my website are:
1. RSS feeds - People using RSS aggregator services as well as local RSS reader tools.
2. Newsletters - I was surprised to discover just how many tech newsletters there are on the Web and how active their user bases are. Once in a while, a newsletter picks up one of my silly or quirky posts, which then brings a large number of visits from its followers.
3. Search engines - Traffic from Google, DuckDuckGo, Bing and similar search engines. This is usually for specific tools, games and HOWTO posts available on my website that some visitors tend to return to repeatedly.
[1] https://susam.net/from-web-feed-to-186850-hits.html