You're right, it should be on our to-do list to make this page make sense again.
I think Ben's point (and a good one) is that the actual implementation was shite.... I think we agree there's value in the idea.. its just that at the moment all it provides is a long list of (largely) useless pap....
Some kind of interface that allows admins to decide what kinds of linked info should be shown sounds more sensible.
We should "make this page make sense".
Leave it to Lars outline the essence of and the solution to the problem with five words or less.
When I try to tell people about what community software is, I use Amazon.com's functionality (which is actually a suggesion of Philip's). I would not be surprised if Amazon's db servers have as much if not more user contributed content as editorial content. More than once I've ended up purchasing a book that I learned about from an entirely unrelated review of another book. This was because I was able to follow a trail of user contributed content.
This functionality is, of course, the same that exists at photo.net and at here. The problem, as Simon says, is that in oacs4 it's total crap.
Perhaps this should be another item that use-case experts should take on as a design task?
So the TODO item should be something along the lines of working towards fleshing out the service contract used by profile provider and user profile and adding code to packages to supply the necessary items.