If your intention is to share information then I"d opt for a Wiki based approach. Dokiwiki stores its pages as plain text files and offers revision control. The Dokuwiki syntax is optimized for providing documentation.
On the other hand, if your intention is to trigger interactivity then a blog would be a better means of providing content. I picked Wordpress for my own blog but there are a lot of alternatives.

As for (self-)hosting: I chose to self-host my Wikis as well as my Blog and in addition I an using a sqlite database for my blog. This makes it possible - and easy - for me to create and store backups. And since both Dokuwiki and Wordpress are popular open source products, when they go out of business you can be fairly sure that someone will continue development in some compatible form.

A Wordpress blog can be exported and then re-imported if you want to switch from self-hosted to hosted, or from sqlite to mysql, or back. But in terms of perennity, I see no issues with either software or either form of hosting.

2 members found this post helpful.

Yes, you're right. Sorry.

your blog (unixgarden.wordpress.com) looks quite nice as is, wordpress will keep going on the long term even though people complain about the bloat and punctual security issues. Maybe stick w/ it & don't change anything ?

Have seen ruby friends using jekyllrb.com & octopress.org and gave it a shot.
It fit my need perfectly, simple, static, command line base, understandable directory tree, perennity relying on ruby.
Adding comments is feasible in both, easier in octopress w/ disqus: link
Thinking about it, twitter is supported by both tools, meaning every time you post a blog entry you have a twitter button/handle to interact w/ the post.
Maybe this can serve as comment tool ?