We use Atlassian's Confluence. Confluence is a nice collaboration tool built on wiki concepts. Us techies used a wiki prior but Atlassian's almost-a-wiki-but-not-as-scary-as-one is now so popular that it is a major issue when Confluence is down. It is pretty much company-wide now and updated almost every minute.
Yes, it's not free (or Free) and is made by a pretty established company, but it's a solid product, Wiki enough that if you want to get into it, there is a lot fo customization and detail that you can do, but at he same time friendly enough that if you don't care, you can just use the WYSIWYG editor to make your point. It also integrates nicely with JIRA, although I doubt that's used by much of the HN crowd.
As for getting people to use it, my team made a rule that if you sent us a question that (in our opinion) belonged in the wiki, we'd answer it there and send you back a link. After a few weeks of doing that, people just stopped asking and went there first.
The idea of user-editable content isn't the problem. But wikis are an unknown quantity and a slippery concept for non-nerds to grasp. There are no affordances, no guidance, no structures to help orient people[1], and while wiki syntax is awful that's only a contributing problem.
It's like if a carpenter/handyman/car repair guy handed you a smooth, featureless egg-shaped object and said "This is a Ziki. You can do everything with this tool. Now, check my tire pressure."
Even if you knew how to check tire pressure in general, you'd be SOL.
Second issue is that people use wikis for things other than collaborative documentation, just like people use blogs for project management (just because they're easy to install), and that's not helping the adoption problem.
[1] I don't mean the document tree, either. People are used to structured content.