YAS SOMEONE FINALLY DONE DID IT

MathlyCat wrote:

YAS SOMEONE FINALLY DONE DID IT

ayyyyyy

alexphan wrote:

redgreenandblue wrote:

Nice new guide! I hope people will follow it!

Thanks! I hope the suggestions forum will greatly improve, too.

Make the suggestions forum great again

Sigton

Can we add “Keep Ideas as Simple as Possible”? I feel that this may be a problem in the future.

Scratch isn't designed for a super complex set of features. Like @Lightnin said in this post…

Lightnin wrote:

It should be easy to climb in and get started with Scratch - even for Scratchers who have no experience programming.

In other words, the website needs to be easy to understand and work with. If a feature sounds like it is too complicated for a 10 year old, it might be best to simplify the suggestion as much as possible so it is not super complicated.

Ziggy741 wrote:

Some users use stuff instead of support/no support/semi-support, like for example +1/-1/+0.5 or Approved/Rejected. (I don't know if all users who use the “Counting thing” do +0.5 for semi-support, I'm using that example because I once saw it. Also, for the “Approved thing”, I don't think I saw one for semi-support.) I think that those stuff instead of support/no support/semi-support seem really unconstructive, so I think you should add that to the list of what kind of replies you shouldn't do.

You might also want to add the Approved and Rejected ones. Saying “Approved” or “Rejected” might be one of the worst things to say. If you say “Approved”, someone might think that the suggestion is going to be added. Saying “Rejected” might make users think that there is no chance of the suggestion being added.

Does Sarcasm count as against the sticky? I've seen this being used for criticizing someone when they're being unconstructive, and that's being rude to their post. Sarcasm isn't actually funny! It's more of an insult!
Sorry about the sarcasm rant post.

DownsGameClub wrote:

Can we add “Keep Ideas as Simple as Possible”? I feel that this may be a problem in the future.

Scratch isn't designed for a super complex set of features. Like @Lightnin said in this post…

Lightnin wrote:

It should be easy to climb in and get started with Scratch - even for Scratchers who have no experience programming.

In other words, the website needs to be easy to understand and work with. If a feature sounds like it is too complicated for a 10 year old, it might be best to simplify the suggestion as much as possible so it is not super complicated.

That is a good point. I might add that later.

Ziggy741 wrote:

Ziggy741 wrote:

Some users use stuff instead of support/no support/semi-support, like for example +1/-1/+0.5 or Approved/Rejected. (I don't know if all users who use the “Counting thing” do +0.5 for semi-support, I'm using that example because I once saw it. Also, for the “Approved thing”, I don't think I saw one for semi-support.) I think that those stuff instead of support/no support/semi-support seem really unconstructive, so I think you should add that to the list of what kind of replies you shouldn't do.

You might also want to add the Approved and Rejected ones. Saying “Approved” or “Rejected” might be one of the worst things to say. If you say “Approved”, someone might think that the suggestion is going to be added. Saying “Rejected” might make users think that there is no chance of the suggestion being added.

That is also a good point. I will add it to the “support/no support” part of the unconstructive arguments.

1MatsuLover wrote:

Does Sarcasm count as against the sticky? I've seen this being used for criticizing someone when they're being unconstructive, and that's being rude to their post. Sarcasm isn't actually funny! It's more of an insult!
Sorry about the sarcasm rant post.

Well, you're being unconstructive when you're being sarcastic, because you are “talking” in a tone that makes the OP feel uncomfortable. So yes, it is against this sticky.

alexphan wrote:

Ziggy741 wrote:

Ziggy741 wrote:

Some users use stuff instead of support/no support/semi-support, like for example +1/-1/+0.5 or Approved/Rejected. (I don't know if all users who use the “Counting thing” do +0.5 for semi-support, I'm using that example because I once saw it. Also, for the “Approved thing”, I don't think I saw one for semi-support.) I think that those stuff instead of support/no support/semi-support seem really unconstructive, so I think you should add that to the list of what kind of replies you shouldn't do.

You might also want to add the Approved and Rejected ones. Saying “Approved” or “Rejected” might be one of the worst things to say. If you say “Approved”, someone might think that the suggestion is going to be added. Saying “Rejected” might make users think that there is no chance of the suggestion being added.

That is also a good point. I will add it to the “support/no support” part of the unconstructive arguments.

Okay. You might want to have a part for it not with the normal support/semi-support/no support without a reasoning because I think that approved/rejected might be even worse than support/semi-support/no support without a reason because it might confuse users and users might think that their idea is going to get added or there is no chance of it getting added.

DownsGameClub wrote:

Can we add “Keep Ideas as Simple as Possible”? I feel that this may be a problem in the future.

Scratch isn't designed for a super complex set of features. Like @Lightnin said in this post…

Lightnin wrote:

It should be easy to climb in and get started with Scratch - even for Scratchers who have no experience programming.

In other words, the website needs to be easy to understand and work with. If a feature sounds like it is too complicated for a 10 year old, it might be best to simplify the suggestion as much as possible so it is not super complicated.

That's not what Scratch wants, it wants ideas that are simple but can be made complex.

So obscure suggestions is not what we want, but nor uber complex.

Ziggy741 wrote:

alexphan wrote:

Ziggy741 wrote:

Ziggy741 wrote:

Some users use stuff instead of support/no support/semi-support, like for example +1/-1/+0.5 or Approved/Rejected. (I don't know if all users who use the “Counting thing” do +0.5 for semi-support, I'm using that example because I once saw it. Also, for the “Approved thing”, I don't think I saw one for semi-support.) I think that those stuff instead of support/no support/semi-support seem really unconstructive, so I think you should add that to the list of what kind of replies you shouldn't do.

You might also want to add the Approved and Rejected ones. Saying “Approved” or “Rejected” might be one of the worst things to say. If you say “Approved”, someone might think that the suggestion is going to be added. Saying “Rejected” might make users think that there is no chance of the suggestion being added.

That is also a good point. I will add it to the “support/no support” part of the unconstructive arguments.

Okay. You might want to have a part for it not with the normal support/semi-support/no support without a reasoning because I think that approved/rejected might be even worse than support/semi-support/no support without a reason because it might confuse users and users might think that their idea is going to get added or there is no chance of it getting added.

That's based off of your own mindset. Not everyone thinks the same.

Hence why we don't add things based on 100% opinion. The only way we're going to change the way people respond is if we all respond reasonably, with fair argument, and not the spammy stupidity of “support teehee pointless text”

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

Ziggy741 wrote:

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

I want to prevent it from coming up again.

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

I want to prevent it from coming up again.

What coming up again?

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

This ties in a bit with “Scratch isn't social media”. I might add it as a part of that argument, though.

For the “Don't bash on ideas” you should also say stuff about what you should say if you find a duplicate topic.

Ziggy741 wrote:

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

I want to prevent it from coming up again.

What coming up again?

The argument “no support scratch is not about popularity”.

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

I want to prevent it from coming up again.

What coming up again?

The argument “no support scratch is not about popularity”.

Okay thank you. Well I can stop using that to no support (I'm not really doing the support thing anymore.) and I changed my mind so I think that it should be added. But I think it should be the rows on the Front Page instead of the Explore and Search, because the Explore and Search can be used to find projects faster.

Ziggy741 wrote:

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

I want to prevent it from coming up again.

What coming up again?

The argument “no support scratch is not about popularity”.

Okay thank you. Well I can stop using that to no support (I'm not really doing the support thing anymore.) and I changed my mind so I think that it should be added. But I think it should be the rows on the Front Page instead of the Explore and Search, because the Explore and Search can be used to find projects faster.

ok

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

Ziggy741 wrote:

pvz_pro wrote:

• No support, scratch is not about popularity. - We all know that scratch is not about popularity, but that is like saying “We should not have explore/search because scratch is not about popularity.” Don't ever say this unless the idea is encouraging to trying to be super popular.
  

Could you please add this?

I don't agree. The search and Explore are not about fame. They are for finding stuff faster. We also can't have every single reason to not support.

I want to prevent it from coming up again.

What coming up again?

The argument “no support scratch is not about popularity”.

Okay thank you. Well I can stop using that to no support (I'm not really doing the support thing anymore.) and I changed my mind so I think that it should be added. But I think it should be the rows on the Front Page instead of the Explore and Search, because the Explore and Search can be used to find projects faster.

ok

Okay.