Hey Guys,

this might have been discussed before, but I can´t find anything related...

Most threads are about users reporting bugs / problems and asking for help or features.
Many issues are posted multiple times, resulting in endless threads with repeating posts that are hard to read. Answers already there are not found, very same questions are posted again and again. Users give up, don´t search anymore at all, making the problem even worse...

Would it be possible to add a "Sticky Post" to each thread that always appears before the newest post?

In this post the OP (and maybe everyone with a certain number of posts and/or thanks) may maintain a list of known issues and the related solutions...
(Something like a "Micro Wiki" ;-) )

Example:
I think this might be a way to reduce thread size as well as frustration among users...

What do you think? Possible?

But you're assuming that these offenders will read the sticky posts. They don't - instead choosing to jump straight in and create a new thread ignoring any existing threads, sticky or not.

I think thats a good idea it would help stop repeated threads common if i had 1 pound for every n900 memory corrupt / read only i would be richer than bill gates
P.M a mod and see what they reply

The current system has disadvantages that won't be solved by constantly spamming outselves not to offend against it.

It is not ideal to force a newbie to post his question on page 37 of a thread and then scold him because he doesn't know something that was clearly stated on page 8, then again on 14 and 24.

I don't think there is a really great way to fix things; nagging all of us for the offences committed by a few of us isn't my idea of an improvement.

Hard moderation. Proven to work on many many many forums.

Yes, it 'works' by scaring people into shutting up so their problems literally disappear. I think that light moderation is working well here. 'Prove' that it isn't, since you know so much about what has been proven.

The main reason many of these threads reach 37 pages is that people keep asking questions that have already been answered either:

1. On the same page of the thread.
2. In the first post of the thread, which devs often update following a new release.
3. In the changelog for the application, which users should read before installing updates.

Users should be prepared to accept a degree of personal responsibility (i.e. doing a bit of basic research and submitting proper bug reports) when installing software from extras-devel/testing. Otherwise they should stick to the stable software in extras, or at least refrain from complaining when they get their fingers burnt.

The idea is of merit but I believe a better solution might be to wiki-up solutions, rather than leave them languishing in tmo for people only to find with power search. What's more, wiki articles can be written in an all-encompassing instruction like manner, and added to if need be, whereas threads by their nature jump around with different people responding to different questions. It's up to us all to add the FAQ to wiki articles, especially if they're instructions.

Refering to Post #1 specifically, the troubleshooting page certainly needs some expansion. For example, the useful tip to sort out corrupt files isn't there (see post #3 of 72799). And, I've long thought a glossary would be very useful.

Incidentally, the info on how to create a new wiki article doesn't seem that up to date. The page is still a "draft" version and I can't find a way to create a blank wiki page the "create public document instructions don't quite fit with the links available (where's the "folder" button/link?).

Edit - addition: it would be useful if those asking for help in a new thread, would add the prefix [SOLVED] to the thread title so when others are searching for a how-to that's not in the wiki, it would be clear what worked and what didn't. Could a message to this effect be applied to the thread-start page?

One problem...The wiki is a dogshit of a mess.

Thanks everyone for your opinions!

Please let me clarify my thoughts and sum up a bit what was answered so far...

First, my intention was reducing repeating requests/posts within one thread blowing it up into one useless swamp...
Of course, in the end, an easier way to find answers might also reduce the number of redundant threads, at least that`s what I hope ;-)

Yes, I "assume" they read the sticky post before posting!
Heck, many users don´t read the last 3 or 4 posts, but hopefully they will at least read the one at the top of a thread! Especially when its specially marked and users get used to find answers there...one day hopefully ;-)

Exactly, thats why I suggest to collect the answers from page 8, 14 and 24 on a sticky post that appears always BEFORE the newest one...

Well, we want testers and participation in development, right? Hence, problems and and questions are inevitable...
Reporting of bugs is also welcome, but reporting a bug once is enough.
Unfortunately reality shows it doesn´t work as in the "perfect world" described by you. Training everyone to follow the rules of "bug reports" and "search before you post" seems to be a hopeless project to me. Just trying to find a workaround and have a cleaner more enjoyable and useful TMO.

Mentioned alternatives:
1) Changelog
Well, we all know people are lazy and don´t check changelog. Further changelog is not helpful to describe workarounds, known problems etc....
2) Post #1
Very close concept, but with 2 disadvantages:
First, users are too lazy to check Post #1 or simply don´t know that they can find answers there.
Second, not all OP´s follow the idea of updating Post #1 with relevant information and only OP´s CAN do that!
3) Wiki-Page
Sure, a wiki is the most powerful solution in case someone takes the effort of creating and updating AND users actually know there is one and where to find it...
In case someone takes the effort to create one, the sticky post can still be used to point users to the wiki page...

Would be nice if a mod could share his opinion and let us know if something like this is possible at all...

EDIT: Reported this thread, asking mod for feedback...