DaSpudLord wrote:

monstermash3 wrote:

DaSpudLord wrote:

You could provide a link, you know, instead of just telling me to find it myself.

How do you provide a link to a specific post (without it being the last post)?

The post timestamp that appears above the username of the user that made the post also functions as a link to that post. Just right click on it and select copy link address.

monstermash3 wrote:

DaSpudLord wrote:

monstermash3 wrote:

DaSpudLord wrote:

You could provide a link, you know, instead of just telling me to find it myself.

How do you provide a link to a specific post (without it being the last post)?

The post timestamp that appears above the username of the user that made the post also functions as a link to that post. Just right click on it and select copy link address.

Ok, here is the link.

monstermash3 wrote:

21. Sharing projects privately
It is important that everyone can view a project, so inappropriate content can be reported.

22. Charging real money/in-project micropayments
If someone could charge real money to run a script, it would limit the access of some people to Scratch. Also, this would be a very complicated aspect of Scratch, but it would not teach learning Scratchers/New Scratchers any more.

23. Less scary alerts
It has been decided that alerts are okay the way they are.

24. Stopping banning impersonating joke accounts
Impersonation is not permitted on Scratch. Scratch does not allow any joke accounts. Impersonation jokes go too far for jokes within Scratch.

25. Setting a limit to how many times the same comment can be reported
This isn't a big problem. It is rare for several people to report the same comment, and it's never hard to deal with.

26. Increasing limits of FPC actions

Paddle2see wrote:

We intentionally give control of the the Curated Projects row to the Curator with very little restriction so that they can put up projects that express what they like about Scratch. Of course, it is important that Curators do this while abiding by the Community Guidelines - which ask that everyone be honest and help keep the site friendly. If you think that a Curator's actions are working against those principles, please use the Contact Us button to let the Scratch Team know.

scratchmaster755 wrote:

I think there should be a name block

when stop sign clicked

Username [ Delete]

MathlyCat wrote:

I think you should add this:

21. Multiplayer/Servers in a Single Block
Scratch is about creativity and learning. You don't learn anything from a single block that allows for this function. There is also the problem of this being a very vague block, what would it exactly do? Does it create a lobby, how does it accept players? Instead you can use Cloud Variables to make your very own servers, maybe ask a few people in the Help With Scripts forum? Remember, Imagine - Program - Share!

monstermash3 wrote:

monstermash3 wrote:

21. Sharing projects privately
It is important that everyone can view a project, so inappropriate content can be reported.

22. Charging real money/in-project micropayments
If someone could charge real money to run a script, it would limit the access of some people to Scratch. Also, this would be a very complicated aspect of Scratch, but it would not teach learning Scratchers/New Scratchers any more.

23. Less scary alerts
It has been decided that alerts are okay the way they are.

24. Stopping banning impersonating joke accounts
Impersonation is not permitted on Scratch. Scratch does not allow any joke accounts. Impersonation jokes go too far for jokes within Scratch.

25. Setting a limit to how many times the same comment can be reported
This isn't a big problem. It is rare for several people to report the same comment, and it's never hard to deal with.

Also

26. Increasing limits of FPC actions

Paddle2see wrote:

We intentionally give control of the the Curated Projects row to the Curator with very little restriction so that they can put up projects that express what they like about Scratch. Of course, it is important that Curators do this while abiding by the Community Guidelines - which ask that everyone be honest and help keep the site friendly. If you think that a Curator's actions are working against those principles, please use the Contact Us button to let the Scratch Team know.

This may not have been suggested multiple times, but I just wanted to point this out.

27. Facepalm emoji
A facepalm emoji has only bad uses. Self-deprecation is basically the only thing this would be used for besides misusing it for bad comments.

monstermash3 wrote:

monstermash3 wrote:

21. Sharing projects privately
It is important that everyone can view a project, so inappropriate content can be reported.

22. Charging real money/in-project micropayments
If someone could charge real money to run a script, it would limit the access of some people to Scratch. Also, this would be a very complicated aspect of Scratch, but it would not teach learning Scratchers/New Scratchers any more.

23. Less scary alerts
It has been decided that alerts are okay the way they are.

24. Stopping banning impersonating joke accounts
Impersonation is not permitted on Scratch. Scratch does not allow any joke accounts. Impersonation jokes go too far for jokes within Scratch.

25. Setting a limit to how many times the same comment can be reported
This isn't a big problem. It is rare for several people to report the same comment, and it's never hard to deal with.

Also

26. Increasing limits of FPC actions

Paddle2see wrote:

We intentionally give control of the the Curated Projects row to the Curator with very little restriction so that they can put up projects that express what they like about Scratch. Of course, it is important that Curators do this while abiding by the Community Guidelines - which ask that everyone be honest and help keep the site friendly. If you think that a Curator's actions are working against those principles, please use the Contact Us button to let the Scratch Team know.

This may not have been suggested multiple times, but I just wanted to point this out.

monstermash3 wrote:

monstermash3 wrote:

monstermash3 wrote:

21. Sharing projects privately
It is important that everyone can view a project, so inappropriate content can be reported.

22. Charging real money/in-project micropayments
If someone could charge real money to run a script, it would limit the access of some people to Scratch. Also, this would be a very complicated aspect of Scratch, but it would not teach learning Scratchers/New Scratchers any more.

23. Less scary alerts
It has been decided that alerts are okay the way they are.

24. Stopping banning impersonating joke accounts
Impersonation is not permitted on Scratch. Scratch does not allow any joke accounts. Impersonation jokes go too far for jokes within Scratch.

25. Setting a limit to how many times the same comment can be reported
This isn't a big problem. It is rare for several people to report the same comment, and it's never hard to deal with.

Also

26. Increasing limits of FPC actions

Paddle2see wrote:

We intentionally give control of the the Curated Projects row to the Curator with very little restriction so that they can put up projects that express what they like about Scratch. Of course, it is important that Curators do this while abiding by the Community Guidelines - which ask that everyone be honest and help keep the site friendly. If you think that a Curator's actions are working against those principles, please use the Contact Us button to let the Scratch Team know.

This may not have been suggested multiple times, but I just wanted to point this out.

This may end up getting rejected (sorry if this is unneccesary).

27. Facepalm emoji
A facepalm emoji has only bad uses. Self-deprecation is basically the only thing this would be used for besides misusing it for bad comments.

Paddle2See wrote:

I'd rather not try to handle every single rejected suggestion that comes up - let's just address the common ones that appear repeatedly. Sometimes it's good to revisit your thinking on a suggestion, even if it's been made and rejected previously.

DaSpudLord wrote:

monstermash3 wrote:

monstermash3 wrote:

monstermash3 wrote:

21. Sharing projects privately
It is important that everyone can view a project, so inappropriate content can be reported.

22. Charging real money/in-project micropayments
If someone could charge real money to run a script, it would limit the access of some people to Scratch. Also, this would be a very complicated aspect of Scratch, but it would not teach learning Scratchers/New Scratchers any more.

23. Less scary alerts
It has been decided that alerts are okay the way they are.

24. Stopping banning impersonating joke accounts
Impersonation is not permitted on Scratch. Scratch does not allow any joke accounts. Impersonation jokes go too far for jokes within Scratch.

25. Setting a limit to how many times the same comment can be reported
This isn't a big problem. It is rare for several people to report the same comment, and it's never hard to deal with.

Also

26. Increasing limits of FPC actions

Paddle2see wrote:

We intentionally give control of the the Curated Projects row to the Curator with very little restriction so that they can put up projects that express what they like about Scratch. Of course, it is important that Curators do this while abiding by the Community Guidelines - which ask that everyone be honest and help keep the site friendly. If you think that a Curator's actions are working against those principles, please use the Contact Us button to let the Scratch Team know.

This may not have been suggested multiple times, but I just wanted to point this out.

This may end up getting rejected (sorry if this is unneccesary).

27. Facepalm emoji
A facepalm emoji has only bad uses. Self-deprecation is basically the only thing this would be used for besides misusing it for bad comments.

Paddle2See wrote:

I'd rather not try to handle every single rejected suggestion that comes up - let's just address the common ones that appear repeatedly. Sometimes it's good to revisit your thinking on a suggestion, even if it's been made and rejected previously.

Failord wrote:

I don't see “2 people on the same project editing it at the same time like in Google Docs” on the list. That's been suggested a bajillion times.

Failord wrote:

I don't see “2 people on the same project editing it at the same time like in Google Docs” on the list. That's been suggested a bajillion times.

Failord wrote:

I don't see “2 people on the same project editing it at the same time like in Google Docs” on the list. That's been suggested a bajillion times.

SimplyUnliked wrote:

-snip-

banana439monkey wrote:

Just so you know, the scratch team haven't implemented Cloud lists at all and they said they would!

CraZGuy wrote:

I'd like to suggest a code that 100% kills a sound. The and script doesn't always work. I suggest this:

[play sound until < >]

There in the < > could be <until done>, <key v pressed>, <(variable) = (blah)> or something.

That would make it work when placed inside a or script.



BTW….
LOL I m done! Banning FNAF?? I like the fact that an animatronic game actually has its own category in the rejected suggestion. What goes on in people's minds?