Dave Winer: to comment on a blog you need to have a blog

Showing all posts about content production

Dave Winer: to comment on a blog you need to have a blog

1 December 2025

Dave Winer, an American software developer and blogger, is working on a blog discourse system. In short, this is a blog commenting system, allowing you to comment on someone’s else blog post, potentially this one you’re reading right now, but via your own blog or website:

The first thing to know is that all comments are blog posts. You write the comment on a blog that you own. And maybe that will be the only way anyone other than you will ever see it. But you don’t have to “go” to the blog to write the comment. You stay right where you are.

Presumably, if someone writes a comment, that is actually a post on their blog, in reply to something I’ve written here, I’m notified in some way. Further, I can then allow that comment/blog post to appear as a comment on my website, if I so decide. But there’s nothing new about writing responses to another person’s blog post, on your own blog.

Once upon a time, the only way to “comment” publicly on someone else’s blog post, or rather, an online journal entry, as they were once called, was to write a post on your website in response. This is because early blogs didn’t have commenting facilities. Back then, the tool closest to permitting any sort of on-site public interaction between website writers and visitors, were guestbooks.

But guestbooks — intended really only to allow visitors to leave brief, and usually complimentary messages — were hardly an appropriate forum for discussing blog posts, particularly if these conversations were in-depth and involved numerous participants. But unless a visitor told the writer about their post-in-response, just about the only way a writer might find out was through their referrer logs.

But writing blog posts as comments is a practice that has somewhat been revived by the IndieWeb/SmallWeb community. A blogger might respond to this post, on their website, using the title “Re: Dave Winer: to comment on a blog you need to have a blog”. They might also send a pingback, a webmention, or an email, advising me of their blog post.

Being able to reply to blog posts with comments though made for a convenient way to host a centralised discussion about an article, rather than having fragments of it scattered across the web. Centralisation can have some benefits. Readers no longer needed a website to respond to a blog post, and often only had to supply an email address, whether real or not, to air their thoughts.

And so the discussion flowed.

But we all know what happened next. Free-for-all commenting was a boon for spammers. Winer’s blog discourse system would create a hurdle for spammers, who likely would not have a website they could post comments to. Of course, serious comment spammers could setup a blog to publish their spam to, but perhaps the discourse system will have a way for dealing with that.

The blog discourse system also addresses another matter few people give much thought to: comment, and by definition content, ownership. Who “owns” a comment I leave on someone else’s blog? Me, or the website owner? If I append my name, I am identified as the writer — am I not? — and intellectual rights and what not, are mine, even though the publication is not.

Most likely that is the case. Perhaps though, somehow, someone with the same name as me, might claim the comment as theirs, particularly if they see some value in it. I don’t know how often that sort of thing happens, if at all, probably never, or incredibly rarely. But if my comments in reply to other people’s posts are published at my website, and then “syndicated” as an approved comment, the possibility of ownership conflict is removed.

What I wonder about though, is where do the comments I write, which are a response to a post on another person’s blog, end up on my website? Will these be funnelled into a separate content stream? I’m not sure I like the idea of comments intended for other blogs, featuring on the main feed of my blog, amongst my regular posts, even if I did compose the comments.

And will differing content management systems be able to talk each other? For instance will a comment-post made on a WordPress blog, post seamlessly onto, say, a Ghost blog? What of bona fide commenters who do not have blogs? Questions remain to be answered then. But I’m looking forward to finding out more about Winer’s discourse system, and seeing it in action.

AI information summaries eating away at Wikipedia reader base

29 October 2025

Just about every online publisher has experienced a decline in the number of people reading articles and information published on their websites. Search engines presently do such a good job of breaking down the main points of news reports, blog posts, and the like, that seekers of information are seldom reading the material at its source.

Online encyclopedia Wikipedia is no exception, and falls in visitors stand to threaten what is surely an invaluable resource, along with others such as Encyclopaedia Britannica.

What happens if we follow this shift in the way people obtain information to its absurd, yet logical, conclusion? If websites such as Wikipedia, Britannica, along with news sites, and many, many, others, are forced to close because no one visits them anymore, what is going to feed the search engine AI summaries we’ve become accustomed to?

In short, we’re going to see AI summaries eat the web, and then eat themselves. The onus here is on search engines, AKA answer engines, and whatever other services generate AI summaries, to use them more selectively, and wean information seekers off them.

Is that something anyone can see happening? No, I didn’t think so.

Answer engines: a new challenge for content writers, bloggers

25 September 2025

Press Gazette:

The biggest year-on-year declines were at Forbes (down 53% to 85.5 million visits — the steepest decline year on year for the second month in a row), Huffington Post (down 45% to 41.3 million), Business Insider (down 44% to 66.6 million), and News 18 (down 42% to 146.3 million). The Independent, CBC and Washington Post also closely followed with drops of 41% in year on year site visits.

Nearly all of the world’s top fifty English language websites have experienced declines in traffic, to greater or lesser degrees, in the last twelve months. Only one has bucked the trend, Substack, but I’m not sure that’s good news. But the reason for the sometimes sharp falls in visitors? AI overviews generated by many of the search engines, that’s what.

People searching for information online are increasingly satisfied with the AI generated summaries, that appear, as the first “result”, in response to a question they have. These overviews are created by drawing on webpages carrying relevant information, and spare search engines users from the need to visit said webpages.

It’s great for those looking for a quick answer to a query, provided of course the overview is accurate. It’s not so good for the people who wrote articles, or blog posts, that feed the AI generated overviews, as they no longer see a visit to their website. But this is the future of online search. Instead of search engines though, we will be using answer engines to source information.

In short, answer engines results will be similar to the AI overviews we see at present. Everything a searcher needs to know will be displayed in the result. There will be no need to visit individual webpages again.

From a content writer’s perspective, it can only be hoped answer engines will cite the sources used to concoct their response to a query. This for however many people who might still wish to verify the information provided by the answer engine, that is.

But not everyone writes content to be indexed by a search engine, and many actively prevent their websites from being looked at by the search engines. I get the feeling this may not be the case for answer engines though. Writers and bloggers are all too aware of AI scraper bots marauding their content, whether they like it or not, to train AI agents.

But going forward, this might be something content writers have to expect, accept even, it they want their work to be recognised. We can all see where this is going. The end of SEO, and the advent of — I don’t know — AEO, being Answer Engine Optimisation. Those wanting their content to be found by the answer engines are going to need to figure out how to optimise it thusly.

No doubt help will at be hand though. AEO experts and gurus will surely be among us soon, if they are not already. But that’s enough good news from me for one day.

Subscribe Openly, and (almost) one-click RSS feed subscriptions

23 September 2025

In an ideal world subscribing to a website/blog’s RSS feed should be as simple as following a page on the socials. Simply click the follow button, and that’s it. In the case of, say, Instagram all future posts of whoever you started following will be visible — algorithms permitting — in the main/home feed.

Of course, subscribing to a RSS feed isn’t difficult. If you know what you’re doing. But to those to don’t know much about RSS, clicking the subscribe button might result in confusion and frustration, and see them abandoning the process all together.

Sometimes clicking the subscribe button might only open the URL of the RSS feed, leaving a budding subscriber wondering what to do next. “Am I meant to bookmark this link?” they might wonder.

But before we ask people to subscribe to a RSS feed, we need them to understand they first need a RSS reader. A RSS reader is an app that allows people to subscribe to, and read, RSS feeds. But to the uninitiated, the process of installing a RSS reader might present another confusing hurdle, only further complicating matters.

Subscribe Openly, however, created by James, is a step in the right direction.

Instead of presenting a would-be RSS subscriber with a screen filled with the raw data of a RSS feed, when they click on the subscribe button, they are presented with a list of RSS readers they can install. Here’s what you’d see if you were subscribing to the RSS feed for my website this way.

Next it needs to be made understood to prospective RSS subscribers that setting up a reader app is not that difficult. They doubtless have numerous apps on their device already, a RSS reader would simply be just another app they need to install. Let’s get to it.

Perhaps though styling feeds so they’re coherent in a web browser is something publishers who syndicate content to RSS should consider. Having a RSS feed that renders like a webpage — that could be bookmarked like any other website — does of course seem like it defeats the purpose of having a RSS feed.

But, if people new to RSS see a coherent looking webpage when clicking the URL of a RSS feed, they might have more incentive to find out more about RSS.

Bloggers might have been syndicating content with ICE not RSS

11 September 2025

Ryan Farley, writing at Buttondown:

Not many people talk about how or why RSS won the content syndication war because few people are aware that a war ever took place. Everyone was so fixated on the drama over RSS’s competing standards (Atom vs RSS 2.0) that they barely registered the rise and fall of the Information and Content Exchange (ICE) specification, which had been created, funded, and eventually abandoned by Microsoft, Adobe, CNET, and other household names.

Here’s a slice of web history I was unaware of until now: an alternative blog content syndication specification that was — for a short time — in competition with RSS.

That Microsoft, as one of the backers of Information and Content Exchange (ICE) syndication, quietly began using RSS, says a lot. A lot about RSS, and Microsoft.

12 foot ladder, a website that circumvented paywalls, taken offline

19 July 2025

Emma Roth, writing for The Verge:

The News/Media Alliance, a trade association behind major news publishers, announced that it has “successfully secured” the removal of 12ft.io, a website that helped users bypass paywalls online.

Thomas Millar, the 12 Foot Ladder founder, saw his app as a way of “cleaning” web pages, by disabling scripts that blocked access to non-paying subscribers. The News/Media Alliance, on the other hand, viewed 12 Foot as an illegal tool, that deprived publishers and writers of subscription income.

After 25 years we still don’t know what the web is, what it could be

18 April 2025

Here’s some web history trivia for you: it’s been twenty-five years since A Dao of Web Design was published at A List Apart (ALA). Written by Australian product developer, and Web Directions co-founder John Allsopp, the article explored how the web, still seen then as an online variation of print, could find its own path, and evolve into something entirely different.

Reflecting on his ALA article earlier this week, John made the following comment:

The Web is its own thing — but we’ve still yet to really discover what that is. Don’t ask me, I don’t know what that is either. But a quarter of a century on I’m still just as interested in discovering what that is.

I think what we can say now though, is the web is no longer a child of print.

For additional historical trivia, see this article I wrote for the Sydney Morning Herald/The Age, about John and Westciv, a company he established with Maxine Sherrin. Westciv developed tools to assist web designers create compliant CSS, and web pages.

That was twenty-years ago — yes, mind blown — and was one of several articles I wrote for print publications, before becoming more focused on writing online. And while talking of ALA, it sadly appears only to be publishing sporadically nowadays.

A personal website is a website published by a person

10 March 2025

I’ve always regarded disassociated as a personal website. Others might see it differently.

For instance, I read a few of the IndieWeb blogs, and when compared with some of those people, my website is not personal. I don’t usually write “dear diary” like journal entries, although I do publish a variation thereof, which I post to my socials feeds. But I don’t delve too much what into about I’m thinking about on a personal level, or what I’m grappling with in my day-to-day life.

Still, it’s a good question to ask: how personal should a personal website be? But it’s one only the person who owns the website can really answer.

One personal website is enough for me

15 October 2024

I’m not sure disassociated always rates as a personal website, with its informational content style. But it’s owned personally by me, and I personally write the content, so on that basis it’s a personal website. A lot of what I post are my thoughts on the many and various things happening online and in the world, so much of what appears here is my personal perspective.

I think I’ve said it a few times before, writing diary-like posts here seems pointless. I’m not sure what interest the ins and outs of my day-to-day life would be to anyone else. But writing diary-like posts is the precise definition of a personal website for some people. I’ve always seen the web as self-publishing platform: a platform to publish whatever you want. So if that’s informational content, or diary-like posts, that’s all fine.

A website whether you consider it personal or otherwise, is yours to do with as you please. Within reason. In that context, one personal website has always been enough for me. But a post by Kev Quirk, about bloggers who have multiple personal websites and blogs, has struck a chord with a few of the people whose RSS feeds I read. For some of us, it seems, one personal website is not enough.

Well, this is the web, and that’s an individual’s call to make. But to my mind, even two personal websites is one too many. Why, I wonder, do some bloggers feel the need to split their web presence? Maybe it’s a throwback to the idea supposedly propagated by Google that we should only be publishing niche blogs? That is, blogs focussed — mainly — on a single topic. In addition to being useful for readers looking for information on a particular subject, niche blogs enjoyed better SERPs placement, or something. Or so the story went.

Mind you, I’m not even sure Google actually said that. Maybe the notion was simply picked up by the people who blogged about blogging, and ended up being bandied ceaselessly around the blogosphere. A lot of my traffic comes in through Google, so clearly they’ve never been bothered by my non-niche blogging style.

But when it comes to having multiple blogs, it’s possible some bloggers want to separate different types of content, or feel not everything they write is suited to a particular blog. That I get, because I post a bit of what I call off-topic content to social media. Back in the day that was Twitter, which made for a great “side-dish” to a blogger’s main website. I don’t use Twitter/X anymore, but still post the same sort of content to the socials I have today, albeit at a greatly reduced rate.

Not everyone wants to post content on social media though. In that case then, I can see the point of something like Micro.blog. I don’t know a whole lot about the platform, but it seems similar to the likes of Mastodon, Threads, or Bluesky: it’s basically for micro-blogging. But even with something like Micro.blog, you still come back to the problem of content ownership, and the concern such platforms, like the social media channels, could close-down just like that.

It’s probably not likely to happen, especially to the established platforms, but it could be a problem if it did. That’s what I like about a single website. Even if my website host closed down overnight, I have the database and other content (e.g. photos) backed-up (in one place, well, more), and ready to potentially transfer elsewhere. Very little, hopefully, would be lost. Trying to recover years’ worth of posts from a closed social media channel might be another matter.

The blogging CMS I use lets me — if I chose — hide selected categories from the main feed/stream (or at least there is a way to make that happen because I did it before), in addition to serving up a separate RSS feed for each post category. If using social media becomes untenable, for whatever reason, in the future, I could always setup a separate off-topic content stream that would only be visible on certain parts of this website.

That seems to me to be the way to go. Everything on your own, single, self-hosted, website. And all in the true spirit of IndieWeb, or whatever you like to call it.

Dense Discovery notches three hundred editions, opens reader community

7 August 2024

Melbourne based Australian designer and publisher Kai Brach’s weekly publication, Dense Discovery (DD), is one of the few newsletters I subscribe to. If you have an interest in, well, everything, then DD is for you. First published in September 2018, the three-hundredth edition was posted yesterday.

And to mark this most impressive of milestones, Brach launched a community space, the DD Lounge, especially for supporters, friends of DD. That a regular newsletter can go on to spawn a community says a lot. Yes, I know there are other similar such communities, but still it’s something.

Congratulations on publishing three-hundred editions DD.

RELATED CONTENT

content production, design, publishing

« older posts