IndianRuby718 wrote:

So, about suggestion 9.2, notifications when you get quoted. at the end it says “If you want to stay updated on a certain topic, you can always follow the topic and get notified on new posts that are made.” But this isn't the main reason this suggestion should be implemented.

IndianRuby718 wrote:

If for example someone posts “support” on a topic and leaves, then someone else quotes them and says “please say why you support”, the first person is never going to see that, because they aren't following the discussion.

The person being quoted probably has no reason to follow the topic if they came over for a simple “support” and leaves.

IndianRuby718 wrote:

[M]y example above [snip] is a very good reason for adding it that hasn't been mentioned. Also, [if it only counts direct quoting, and] if you only get one message no matter how many times someone quotes you up until you view the message, like for normal forum posts, then it can't be abused any more than the regular forums can, right? All the extra quoting would take up that whitespace, but there's no use from it, so the spammers would just stop…

But you could still be spammed if someone has quoted you each time you look at your messages. So I'm not asking to remove this from the rejected list, because I see the problems. I just want to see the above addressed in the reasons why it was rejected. [I also have two ideas to replace this suggestion, and I will make two topics about them, but I want to see what happens with this post first.]
If you want to know where I posted this, it's on here… but my post there was very long XD
Post 102…

p-p-p-p-p-p-p-p-p-p- wrote:

Would being able to enable being notified from your username with an @ be rejected?

p-p-p-p-p-p-p-p-p-p- wrote:

Would being able to enable being notified from your username with an @ be rejected?

p-p-p-p-p-p-p-p-p-p- wrote:

Would being able to enable being notified from your username with an @ be rejected?

Za-Chary wrote:

RobotChickens wrote:

Are these blocks rejected?

<@greenFlag clicked?::sensing>
When @greenFlag clicked? = [false v]::events hat

When @greenFlag clicked? = [true v]::events hat

I'm just going to stop the discussion here and confirm that yes, although the definitions are somewhat ambiguous, they are not explicitly rejected. Feel free to make your own topic suggesting them.

p-p-p-p-p-p-p-p-p-p- wrote:

Would being able to enable being notified from your username with an @ be rejected?

Super_Scratch_Bros20 wrote:

Hold on there. The OP asked if the suggestion was rejected. You said “yes”, then turned around and said that it's not rejected.

p-p-p-p-p-p-p-p-p-p- wrote:

Would being able to enable being notified from your username with an @ be rejected?

Za-Chary wrote:

bruh chill i was building off of what others said

Super_Scratch_Bros20 wrote:

Za-Chary wrote:

bruh chill i was building off of what others said

So, is it rejected, or not? Basically, you answered the “Is this rejected” question with “yes”, and then said it's not rejected? What?

Super_Scratch_Bros20 wrote:

Za-Chary wrote:

bruh chill i was building off of what others said

So, is it rejected, or not? Basically, you answered the “Is this rejected” question with “yes”, and then said it's not rejected? What?

EZ-Games wrote:

He's saying it's not rejected.

BlahBlahBoy22 wrote:

I wish there was a website for scratch. But for like 13+ so we could have some features we can't on here.

Za-Chary wrote:

4.1 Disable “See Inside” or restrict sharing
Some users want an option to prevent Scratchers from looking inside their project and using their artwork, scripts, or sounds. However, the core ideas of Scratch are "Imagine, Program, Share.“ By sharing a project on the Scratch website, you are allowing others to see the code and potentially remix or reuse the data inside, as long as they give credit. That being said, please use the Report any project that uses content from another Scratcher without giving credit to them. If you do not want other users to see inside your project, then do not share your project on the Scratch website.

Restricting sharing so that only certain users can view the project is also not going to be implemented. It is important for projects to be publicly shared for everyone to see so people can report them if they are inappropriate. Only allowing certain users to view projects could increase the chances of inappropriate projects being shared on the website. ”Unlisted projects," similar to a YouTube feature, will also not be implemented for the same reason. It could also be used for private messaging; for more information, see #7.1 on this list.

p-p-p-p-p-p-p-p-p-p- wrote:

Za-Chary wrote:

4.1 Disable “See Inside” or restrict sharing
Some users want an option to prevent Scratchers from looking inside their project and using their artwork, scripts, or sounds. However, the core ideas of Scratch are "Imagine, Program, Share.“ By sharing a project on the Scratch website, you are allowing others to see the code and potentially remix or reuse the data inside, as long as they give credit. That being said, please use the Report any project that uses content from another Scratcher without giving credit to them. If you do not want other users to see inside your project, then do not share your project on the Scratch website.

Restricting sharing so that only certain users can view the project is also not going to be implemented. It is important for projects to be publicly shared for everyone to see so people can report them if they are inappropriate. Only allowing certain users to view projects could increase the chances of inappropriate projects being shared on the website. ”Unlisted projects," similar to a YouTube feature, will also not be implemented for the same reason. It could also be used for private messaging; for more information, see #7.1 on this list.

I have something that falls in this category, but doesn't align with the reasoning, so here:
Would restricting sharing for a class count? For example, if I create a school project, but I'm on my school account, and I want to send it to my teacher, but I don't want anybody else to see (It might be something personal, like an apology letter for talking out in class) then I could privately share with my teacher AND ONLY MY TEACHER so that they can see it?

Ihatr wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

Za-Chary wrote:

4.1 Disable “See Inside” or restrict sharing
Some users want an option to prevent Scratchers from looking inside their project and using their artwork, scripts, or sounds. However, the core ideas of Scratch are "Imagine, Program, Share.“ By sharing a project on the Scratch website, you are allowing others to see the code and potentially remix or reuse the data inside, as long as they give credit. That being said, please use the Report any project that uses content from another Scratcher without giving credit to them. If you do not want other users to see inside your project, then do not share your project on the Scratch website.

Restricting sharing so that only certain users can view the project is also not going to be implemented. It is important for projects to be publicly shared for everyone to see so people can report them if they are inappropriate. Only allowing certain users to view projects could increase the chances of inappropriate projects being shared on the website. ”Unlisted projects," similar to a YouTube feature, will also not be implemented for the same reason. It could also be used for private messaging; for more information, see #7.1 on this list.

I have something that falls in this category, but doesn't align with the reasoning, so here:
Would restricting sharing for a class count? For example, if I create a school project, but I'm on my school account, and I want to send it to my teacher, but I don't want anybody else to see (It might be something personal, like an apology letter for talking out in class) then I could privately share with my teacher AND ONLY MY TEACHER so that they can see it?

I think that probably falls under the rejected line, but I may be wrong.

However, you could also simply download the .sb3 file, and email that to your teacher. Then, your teacher can import it to see what you have created.

when green flag clicked
say [i still didnt understand what this forum is for...] for (until they make me understand) secs

iltersinav2b wrote:

when green flag clicked
say [i still didnt understand what this forum is for...] for (until they make me understand) secs

p-p-p-p-p-p-p-p-p-p- wrote:

iltersinav2b wrote:

when green flag clicked
say [i still didnt understand what this forum is for...] for (until they make me understand) secs

It's so that users don't suggest things that won't be implemented, along with detailed explanations why.