In fact, I’m building open source SaaS for every vertical and leveraging that to build an interoperable, decentralized marketplace.
Social media is a marketplace as well. The good being sold is people’s content and the cost you pay is with your attention. The marketplace’s cut is ads and selling your data.
I really need to automate it though - hard on Twitter and LinkedIn but still pretty easy for Bluesky and Mastodon.
But alas, Facebook pushed forward too fast to counter.
There's still a chance, but the software needs to focus on simplicity and ease of use. Publishing blobs of signed content that can be added to anything - HTML pages, P2P protocols, embedded into emails and tweets - maybe we can hijack the current systems and have distributed identity and publishing take over.
Ask HN: Is starting a personal blog still worth it in the age of AI?
https://news.ycombinator.com/item?id=46268055
A website to destroy all websites
Let's not throw out the baby with the bathwater
https://github.com/searlsco/posse_party/blob/main/LICENSE.tx...
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.
- 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.
I published a write up just this morning: https://idiallo.com/blog/what-its-like-blogging-in-2025
I want to add analytics to my blog too, haven't had any on my sites for about a decade.
Im a firm believer that data collected that doesnt have a clear action associated with it is meaningless - and i couldnt think of an action i would take if my traffic goes up or down on my personal blog - but tbh i mainly blog for myself not really to build an audience, so our objectives might differ
At the risk of stating the obvious: this can get tricky, many popular social media platforms restrict automated posting. Policies around api usage and automation can change often and may not even be fully public as some might overlap anti spam measures.
Buffer documents a number of workflows and limitations in their FAQs.
E.g. for a non-professional Instagram account, the user gets a notification to manually share a post via the Instagram app.
> you can prepare your post in Buffer, receive a notification on your mobile device when it’s time to post, then tap the notification and copy your post over to the social network to finish posting.
source: https://support.buffer.com/article/658-using-notification-pu...
Personally, I follow POSSE to a large extent (although I didn't know this term until recently; it is essentially how personal websites and sharing worked in the early 2000s). But I also post freely to microblogging services like Mastodon on instances run by someone else, without worrying too much about POSSE. Occasionally, a microblog post grows into something that needs more than a paragraph. When that happens, I turn it into a proper blog post on my own website and then share it back out.
If you run your own Mastodon instance, as many people do, there is a bit of an overlap between publishing on your own site (POS) and syndicating elsewhere (SE), since one of the places you are syndicating to lives on your own website. I do not do this myself, as I prefer to keep my hobby infrastructure simple: no heavy services, just Nginx serving static HTMLs as my POS and someone else's Mastodon instance for SE.
Somewhat related, predictions for the future of the web by IWC contritbutors:
I think it's more accurate to see blogging as a distinct channel from other types of social media + content marketing
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 exist 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.
When I talk about visitors arriving at my website from RSS feeds, I am not counting requests from feed aggregators or readers identified by their 'User-Agent' strings. Those are just software tools fetching the feed. I'm not talking about them. What I am referring to are visits to HTML pages on my website where the 'Referer' header indicates that the client came from an RSS aggregator service or feed reader.
It is entirely possible that many more people read my posts directly in their feed readers without ever visiting my site, and I will never be aware of them, as it should be. For the subset of readers who do click through from their feed reader and land on my website, those visits are recorded in my web server logs. My conclusions are based on that data.
doodlesdev•2h ago
[0]: https://indieweb.org/PESOS
kgwxd•1h ago
j45•1h ago
performative•35m ago