Good reasons for polluting/diluting useful resources with stubs and dead posts? O_o

Feedback Community Feedback
1

Could anyone explain to me why we need to keep these around and how they improve support provision and information organisation?

Also, when a post expired with zero responses, what is that for?

If nobody knows the answer, surely it should get flagged as a lack of knowledge in the community???

O_o

Edit: I can’t see any reason to keep these posts active and in the pool of searchable posts. Is the focus on solutions or trying to do as little housekeeping and curation as possible? O_o

Can anyone give a decent reason as to WHY these quite useless and uninformative and closed stubs in the main search index??? Solution ratings to help people find working solutions instead of dead, old, irrelevant posts?

There comes a point where it is inefficient to trawl through all the useless/stub/unanswered/old/irrelevant posts.

Come on, guys? Where’s the sense of organisation?? Or are you just giving into the poor, and unstructured forum software used to try and provide meaningful support to USERS (not developers)?

The posting template is a step in the right direction but there’s absolutely no accounting to input validation or organisation of submitted data elements (ie No categorisation by OS type, version, platform, architecture, software version, etc, etc, etc.)

It’s like you know the shortfalls of tech support but haven’t actually addressed most of them. :confused:

So, it’s not consistent and nobody knows what the rules are pmsl

How has everything even remotely technical or categorical, not just software functionality, become so nondeterministic in the last 20 years?? Damn. Run it and see what bugs we wrote? Very poor state of affairs. :cry:

The worst thing about ‘support forums’ is you never get to talk to the organ grinder, just the monkey. Very poor state indeed.

2

Posts expire after 30 days of inactivity. Within that time, it’s assumed the issue may have been resolved, updates may have fixed it, or the user has moved on.

With the volume of posts here, it’s challenging to keep revisiting older threads. Personally, I focus on users who actively engage and provide relevant details. If a post is too vague or inactive, it’s often not worth the time and energy to follow up. This might differ for official Support, but that’s how I approach it.

If no answer is provided, it’s usually because the post wasn’t seen, was forgotten, or simply got lost—not because nobody knows the answer. Often, questions do get researched if there’s uncertainty.

Transparency. It’s valuable to keep a record of how long issues have existed and ensure users don’t feel ignored or that posts are being arbitrarily removed. It also helps showcase the good and bad of community interactions.

3

I believe it’s now 2 months (60 days), not that it really matters :stuck_out_tongue_winking_eye:

4

Negative. Varies. But overall 1 month. For example:

image
image830×627 55.9 KB

image
image694×843 71.3 KB

But you’re right some will be longer, for example:

image
image670×614 83.2 KB

Seems like perhaps topics with no category are the ones defaulting to 2 months?

5

Oh fair enough, I was seeing 2 months the few times I was looking :man_shrugging:

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

8

@another_user_acount so I got the notification you quoted me, so seems you edited your post to add. I just reopened in case was anything further to need to address.

In terms of saying the support forums you never get to talk to the organ grinder, I can’t say I agree. @Mattches, Evan123, and others are regularly here replying to topics and solving issues

When you create a topic, it shows. Like the one you just created not long ago:

image
image810×124 5.56 KB

So that is pure as can be that if you or someone doesn’t comment, it will close after a month.

Now that I reopened this topic, I think it might remain open until manually closed or for whenever a timer is set for it? I say that because it doesn’t have the This topic will close after… indicator on the bottom.

9

  1. A big issue is that I can’t reopen my own posts after someone or a piece of code has deemed it should closed. I assume that nobody can re-open their own posts if someone else deems it should be stopped/closed;

  2. Original question is still unanswered. There’s no good reason to dilute relevant knowledge for the sake of ‘transparency’. Priorities in the appropriate order methinks - Is this a support forum or simply a chronological archive of questions and posts?;

  3. By ‘organ grinder’ I meant the developers of Brave, not other users. If anyone knows which logical conditions fires a specific error message (if it’s even visible or even caught in the first place), it’s going to be the people who wrote it initially and not by determining it’s source from visible behaviours;

Oh, are these guys Brave developers?

  1. ‘I think it might’… Seems a lot like another guess to me :confused:

Can we not get direct, accurate information any more? Low expectations are a burden to others.

My reasoning:

  1. Old questions no longer relate to current versions - Should be archived by Brave version number;
  2. Dead/unanswered posts should either remain open for that version of Brave;
  3. When entering a post and the ‘similar questions’ list is displayed, those posts should be open, relevant, recent and ready for commenting - not closed, unanswered, old or incorrect;
  4. Answers should be rated by the users and administrators/curators for their efficacy;
  5. Low-rated, dead, empty or old/irrelevant posts should NOT be included in solution/problem searches by default unless the user has specifically requested posts relating to a specific version(s) or have requested unanswered and closed posts (why would anyone do that when looking for answers eludes me);
  6. A proper template system for posts with normalised fields to aid in proper organisation, searching and categorisation;

Additionally, not only are threads open to closure by inactivity, they’re simultaneously NOT subject to removal if there are no answers… Although the site administrators have the right to close threads with impunity, the ‘community’ has no recourse to reopen their own threads to add comment or refine… Or even remove.

So, if someone wanted, they could simply keep adding new stub threads under different accounts and you would just keep them all, rendering the site unusable? A informational DoS? One could argue that putting unresolved threads in search results is a kind of a tar-pit, in that you’re overloading the user with useless information which the human has to then parse and filter-out manually? Eurgh :confused:

Anyway, if anyone thinks these are ridiculous or inactionable suggestions or that they would irreparably break site functionality, please do let me know.

I’m happy to go into detail if anyone is unsure as to how these changes could benefit the community.