Is this a good summary of your argument?

NNTP was a great solution to a lot of the problems caused by mailing lists. The main ones being:

• content duplication - mailing lists are bad because everyone gets their own copy of each article.
• reduced content accessibility - mailing lists suck because you miss out on great articles if they were sent before you were part of the mailing list.

We are facing similar problems now. A lot of people have their own sites where they host their own content. We either miss out on great content if we don't trawl through a ton of different sites or we try to make lesswrong a central source for content and face problems with:

• content duplication - through needing to cross post content (essentially duplicating it)
• harder content accessibility - the alternative to cross posting is providing a link, but this is an annoying solution that can be jarring as you need to go to an entirely different site to access the content you want.

NNTP would solve the problems we have now in a similar way to how it solved the problems with mailing lists. That is, it would provide a central repository for content and a way to access this content.

I am currently thinking that the best way to think about the last point is that it means that we should set up a Web API similar to the Blogger Web API. Discussing NNTP, at least to me, is making the solution appear a lot more complicated than it needs to be. Although, I don't know much about NNTP, so I could be overlooking something very important and am interested about what your future posts will explore.

With a Less Wrong Web API, websites could be created that act like views in a database. They would show only the content from a particular group or author. This content would, of course, be styled according to the style rules on the website.

These websites could be free, dns name and web development costs aside, using services like github pages. This is because there should be no need for a back-end as the content and user information is all hosted on Less Wrong. You post, retrieve content and vote using the API. It should also be fairly easy to create more complicated websites that could aggregate and show posts based on user preferences or even to create mobile applications.