Maximouse wrote:

Super_Scratch_Bros20 wrote:

Maximouse wrote:

BearSlothCoding wrote:

it looks like nobody likes the idea.

There would be a support count.

But the Scratch Team looks into the usefulness of a topic, not the support count (proof). They need other people's perspectives, which can persuade the Scratch Team to implement or not to implement it.

People who would have more to tell than just if they support would still post.

@Za-Chary explained it well:

Za-Chary wrote:

Of course, we should all be aware that this suggestion wouldn't actually do much with the chances of a suggestion being implemented. As we've seen many times before, the number of people who say “support” or “no support” has no influence on whether the suggestion gets implemented. Hopefully you are intending this suggestion to be a sort of “placebo” for people. Whether or not they understand that supporting or no supporting actually does nothing in that case, I suppose it doesn't matter as long as they don't write posts which contain only “support.”

But, shouldn't everyone be explaining why they support a suggestion?

(The following will likely not happen, but this is an example from the top of my head.)
Imagine a user creates a post that allows users to edit comments. The Scratch Team is beginning to lean on no support because of the reason it's rejected right now! Meanwhile, @Scratcher thinks it is useful and has valid reasons on why it should be implemented. However, the user is new to the forums, and thinks that pressing “Support” will change the Scratch Team's minds.

R E J E C T E D

(Again, that's an example. I couldn't think of an example that isn't rejected, so I used that. Imagine that topic was created many years ago, I guess.)

All I'm asking is to have to state a reason why you support. I don't necessarily think this will encourage constructive posts. Although you can state why you support, that's what you're supposed to do in the first place.

Super_Scratch_Bros20 wrote:

But, shouldn't everyone be explaining why they support a suggestion?

(The following will likely not happen, but this is an example from the top of my head.)
Imagine a user creates a post that allows users to edit comments. The Scratch Team is beginning to lean on no support because of the reason it's rejected right now! Meanwhile, @Scratcher thinks it is useful and has valid reasons on why it should be implemented. However, the user is new to the forums, and thinks that pressing “Support” will change the Scratch Team's minds.

R E J E C T E D

(Again, that's an example. I couldn't think of an example that isn't rejected, so I used that. Imagine that topic was created many years ago, I guess.)

All I'm asking is to have to state a reason why you support. I don't necessarily think this will encourage constructive posts. Although you can state why you support, that's what you're supposed to do in the first place.

A possible solution is to show something like this after you press “Support”:

Thank you for feedback! You can tell what you like about this suggestion and how it could be improved by leaving a reply.

Making the reason required, though, would make this suggestion pointless, because people would still post unconstructive replies.

Bump.

Maximouse wrote:

Making the reason required, though, would make this suggestion pointless, because people would still post unconstructive replies.

That's a good point, actually. You know how when you report a project for “This project could be improved on”, it will ask you to be constructive to go step-by-step on how to give a helpful and constructive response? Perhaps we could do the same there.

I don't want to start a flame war, so I'm trying to give a polite and respectful response. I only think it should be a requirement to be constructive, and show you how to be constructive.

Bump.

Bump.

Bump.

Support. This would keep it much simpler and help keep the forums more cleaner and easier. and reduce spam.

The votes in the Snap! feature requests forum don't change whether the suggestion gets added, by the way. It's just part of the forum thing they used.

Also, a lot of people would just press the button then leave without saying anything constructive. There would be a lot less posts in general.

Support.
I always wanted to support comments in profiles and project and blah blah blah. So a majority would like it!

Bump.

I don't think this is a good idea; Suggestions is about more than just counting upvotes.

snap forums doesn't have the vote thing anymore

But when you post, you can say why you like or dislike the suggestion. The Scratch Team decides weather to add the feature by looking at why other people support. It has almost nothing to do with numbers.

Mr_PenguinAlex wrote:

Also, a lot of people would just press the button then leave without saying anything constructive. There would be a lot less posts in general.

Yes? Isn't that the point? I think this just acts as a placebo, and it will reduce the amount of unnecessary posts while hopefully retaining the constructive ones.

gosoccerboy5 wrote:

Mr_PenguinAlex wrote:

Also, a lot of people would just press the button then leave without saying anything constructive. There would be a lot less posts in general.

Yes? Isn't that the point? I think this just acts as a placebo, and it will reduce the amount of unnecessary posts while hopefully retaining the constructive ones.

Yes, that's the point. It might reduce the number of all posts a bit (maybe there could be a popup when you press it telling you to leave a constructive reply?), but it would probably reduce the number of posts that just say “it's a good idea”, “it would be helpful” or “support for the reasons above” quite a lot.

Bump.

No support, I don't see any use for this. You said you only have to be constructive for no support. But what about support? Youmustbeconstructivewhenalsosayingsupport (TM) What's the point of this when you could just simply make a post on why you support or no support? Again, no support.

It's not that hard to reply to a topic saying you don't support, and then giving your reason why you don't support. Not having a “vote support / no support” option encourages users to be constructive while explaining why they don't support / do support.

Scratchperson1000000 wrote:

No support, I don't see any use for this. You said you only have to be constructive for no support. But what about support? Youmustbeconstructivewhenalsosayingsupport (TM) What's the point of this when you could just simply make a post on why you support or no support? Again, no support.

Must you read the post