ocular rewritten

While searching for existing topics you wouldn't find closed duplicate topics; you'd find the original topic. And … I don't know why the Scratch Team would want to keep them; they serve no purpose.

Also,

ScolderCreations wrote:

maybe they should only be dustbinned after a short time, to allow a user to see what they did wrong.

What are your thoughts?

Support, maybe they should only be dustbinned after a short time, to allow a user to see what they did wrong.

We're not in a dire need of server space at the moment, but this is a pretty nice idea.

I think that the closed topic should stay closed for a week or month incase the OP wants to re-open it, but after that the topic will get dustbinned.

And the scratch team should have the option to timeout dustbin topics or not, as to prevent useful closed topics to be dustbinned.

Yellowsheep43 wrote:

We're not in a dire need of server space at the moment, but this is a pretty nice idea.

I think that the closed topic should stay closed for a week or month incase the OP wants to re-open it, but after that the topic will get dustbinned.

And the scratch team should have the option to timeout dustbin topics or not, as to prevent useful closed topics to be dustbinned.

This is only for duplicate suggestions. They aren't particularly “useful”, and I don't think the Scratch Team would reopen them.

Reev0102 wrote:

This is only for duplicate and rejected suggestions. They aren't particularly “useful”, and I don't think the Scratch Team would reopen them.

Right, but still. We're not in a dire need of server space. But I still like this idea, helping to clean out all the useless topics that are already resolved.

rejected suggestions are kept to make it easier to find duplicates

Reev0102 wrote:

It would probably go easy on the Scratch servers,

dustbinned posts are still kept, but they can only be seen by moderators.

potatophant wrote:

rejected suggestions are kept to make it easier to find duplicates

How does keeping rejected suggestions make it easier to find duplicates?

support
for reasons in op

Reev0102 wrote:

potatophant wrote:

rejected suggestions are kept to make it easier to find duplicates

How does keeping rejected suggestions make it easier to find duplicates?

Often, there is question of whether or not to remove something in TOLORS. Keeping rejected suggestions viewable to all makes it so that people can see the frequency with which it is suggested.

i need help deleting my mail please comment below to help me

Duplicates and rejections do not break the CG, if they were, they would already be dustbinned. The dustbin has a lot of topics and posts, so I guess that the Scratch Team wants to conserve space.

Bump

SUpport if there is a redirect, that 403 page is creepy…

mumu245 wrote:

SUpport if there is a redirect, that 403 page is creepy…

What 403 page?

I can see reasons to do this, but I can see reasons not to do this.

Reasons to implement this:
Easier to find the Original Topic.
“Declutters” the Suggestions forum a bit.

Reasons to not implement this:
Could mess with the way rejected suggests are decided to be put on TOLORS.
Duplicates can be handy in finding the original topic, too.

^^bump^^

Support, dustbin them after a week or so, so that we can delay the possibility of needing more server space.

It is useful TOLORS management to prove to za-chary that a suggestion has been suggested - so they do serve a purpose and shouldn't be dust binned. With duplicates - maybe since they don't really have a use, but they don't really break the guidelines, like prime689 said.

dertermenter wrote:

It is useful TOLORS management to prove to za-chary that a suggestion has been suggested - so they do serve a purpose and shouldn't be dust binned.

He meant duplicate rejected suggestions. Meaning a scratcher has suggested a suggestion that was previously rejected.

Yellowsheep43 wrote:

dertermenter wrote:

It is useful TOLORS management to prove to za-chary that a suggestion has been suggested - so they do serve a purpose and shouldn't be dust binned.

He meant duplicate rejected suggestions. Meaning a scratcher has suggested a suggestion that was previously rejected.

I don’t really understand what you mean.

Reev0102 wrote:

Yellowsheep43 wrote:

We're not in a dire need of server space at the moment, but this is a pretty nice idea.

I think that the closed topic should stay closed for a week or month incase the OP wants to re-open it, but after that the topic will get dustbinned.

And the scratch team should have the option to timeout dustbin topics or not, as to prevent useful closed topics to be dustbinned.

This is only for duplicate and rejected suggestions. They aren't particularly “useful”, and I don't think the Scratch Team would reopen them.

Edit: are you dating suggestions that are duplicates and rejected? That’s the same as a rejected suggestion, as all rejected suggestions have been suggested.

dertermenter wrote:

Yellowsheep43 wrote:

dertermenter wrote:

It is useful TOLORS management to prove to za-chary that a suggestion has been suggested - so they do serve a purpose and shouldn't be dust binned.

He meant duplicate rejected suggestions. Meaning a scratcher has suggested a suggestion that was previously rejected.

I don’t really understand what you mean.

Reev0102 wrote:

Yellowsheep43 wrote:

We're not in a dire need of server space at the moment, but this is a pretty nice idea.

I think that the closed topic should stay closed for a week or month incase the OP wants to re-open it, but after that the topic will get dustbinned.

And the scratch team should have the option to timeout dustbin topics or not, as to prevent useful closed topics to be dustbinned.

This is only for duplicate and rejected suggestions. They aren't particularly “useful”, and I don't think the Scratch Team would reopen them.

OK, I edited out the “rejected” bit.

Bump

Not my topic about this being a dupe

Support because the clog up Indexers and make it harder to find original topics for dupes