Let me see if I comprehend the ask slashdot system fully, based on what I have observed:
Step 1: Someone has a question, and feels that, for reasons I can't even guess at, the slashdot forum regulars can provide a sensible, useful answer. Maybe I should have labelled this "Mistake 1". The question is usually something that could be answered more quickly by the standard application of a web search engine, or in unusual cases, a good library.
Step 2: The brain-dump. Fifty posts are made, detailing everything that the individual posters know on the subject (around six lines apiece), without coming close to answering the question, but enabling readers to determine by subtraction, the depth of each poster's ignorance.
Step 3: The discussion proceeds to lose contact with reality, as the initial posts are dissected and analysed by a second wave of cretins. Since no new information is introduced at this point, the discussion relies on pure imagination and pettifogging to provide it with additional steam.
Step 4: The answer is provided, in a one line post that is now completely buried by the two hundred other posts above it. If this post is noticed at all, it is probably rated -1:redundant.
Writing a Server: The discussion forks early, with half the comments addressing a question about memory leaks, while the on-topic answers are split between several recommendations for the same book, and interestingly daft suggestions such as "Just use Java!"
Is There a PGP Key Repository?: The question is mildly silly. The answers are a carnival of idiocy. Almost everyone misses the point of the question, in their haste to argue over the particulars of the "web of trust".
Echelon Protection: The mind boggles.
In short, I would like to know what you want in an "Ask k5" section. Presumably something that is not provided in "Ask Slashdot", such as answers, but you could get those from usenet, mailing lists, etc.