I do have a NNTP server set up, and I use some Usenet newsgroups too. I recommend using this. Note that this does not preclude the possibility to have a web int

I do have a NNTP server set up, and I use some Usenet newsgroups too. I recommend using this. Note that this does not preclude the possibility to have a web interface too, although they should contain text (visible in any browser, including Lynx) which specifies the NNTP service, so that you may use that if you prefer to do. Someone else also mentioned private blogs that are exposed both as NNTP and as HTTP(S)/HTML, and this would also be good; if you are doing a blog, you could reject articles without a References header (which must reference a blog post) unless you wrote them by yourself (the articles without a References header are the blog posts, while those with a References header are the comments). A subset of Markdown (without HTML, and maybe a few other things also removed) could be used if wanted, as long as it has a MIME type defined (so that you can identify NNTP articles which use it vs those which don't), and is perfectly readable without a Markdown parser. I thought of making up a URI scheme for referencing Usenet/Unusenet articles. They mandatorily include the message ID, and optionally include server name, timestamp, newsgroup name(s), and/or hash. (This is better than using Google URLs.) I would also suggest perhaps even with the Hacker News, to add a NNTP interface (or an extension to a NNTP client; at least for my "bystand" NNTP client software, protocol extensions are implemented as programs that communicate NNTP on stdin/stdout, and possibly those writing other NNTP clients might want to implement it too).