So basically you can share your project in “private viewing mode” which makes a project only accessible by certain people

In viewing mode, nobody but whitelisted people can view the project. To prevent private messaging, comments are disabled in viewing mode and only a max of 5 people can have access to a project at a time. Projects in viewing mode can ONLY be accessed by finding them on the creators profile, if a viewing project is linked it simply brings up a 404 page when the link is clicked. A project on the creators profile that is in viewing mode can only be seen by people with access. Projects in viewing mode cannot be remixed, however you can see inside them.

Uses:

Allows for feedback on a project
Allows private playtesting


Edit: Cloud variables are disabled in viewing mode. Thank ajskateboarder for that.

What if someone made a project which did this:

forever
ask [Enter message here] and wait
set [☁ answers v] to (join (join (☁ answers) [ ]) (answer)) 
end

(private messaging btw)

Support if cloud variables are disabled in private viewing mode

ajskateboarder wrote:

What if someone made a project which did this:

forever
ask [Enter message here] and wait
set [☁ answers v] to (join (join (☁ answers) [ ]) (answer)) 
end

(private messaging btw)

Support if cloud variables are disabled in private viewing mode

Yes good idea. Cloud variables disabled.

support, always wanted this.

<:|>

Your suggestion appears to be rejected.

TOLORS 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 button on 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; for more information, see this post. It could also be used for private messaging; for more information, see #7.1 on this list.

deleteifscratcher wrote:

Your suggestion appears to be rejected.

TOLORS 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 button on 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; for more information, see this post. It could also be used for private messaging; for more information, see #7.1 on this list.

Technically speaking, exclusive access to certain projects IS rejected, but this suggestion seems to have some solutions aside from the main topic as well, and the fixes to those problems listed on TOLORS 7.1 seem somewhat viable too.

Doesn't fix the fact that people could still make guideline-breaking projects and only share them with people who won't report them.

Also, private messaging is still possible:

person A creates a private project with a text saying a message and makes it so that only person B can see it.
person B creates a private project with a text replying to the aforementioned message and makes it only so that person A can see it.
Process repeats.

While this method takes longer, it's still certainly a viable and easy way to private message, so this suggestion is still rejected.

Even if comments are disabled - this feature would still be allowing private communication through the project. Which is very much not be okay - sorry.