This suggestion is a solution (maybe?) for the 2.1 rejected suggestion:

List of rejected suggestions

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations but also because it could lead to private messaging; for more information, see #7.1 on this list. This suggestion includes live editing (similar to Google Docs) and other forms of private collaboration. If you would like to work on a project with another Scratcher, you can remix each other's projects.

Note: I will talk about chat and comments note that these are two different things.

Main idea
The idea is that instead of having a closed project that only you can see you have an open project that anyone can see. Not everyone can edit but they can see all code, comments, and chat messages. Basically, the project would be “shared” (meaning people can do things like remixing and commenting.)

Appearance
Collaborations would be in a section just under shared projects called “My Collaborations”. In the project editor, there is a chat that people can use to send messages. Everyone (even non-editors) in the project will see a message icon called the chat (maybe on the top right) showing how many new messages there are. These are separate from comments. Comments will not be posted in the chat and you must have permission to use the chat (however anyone can view it.)

Reporting
If something bad happens like someone saying a bad word in chat, comments, or code blocks people can report it (to report a code block just right-click and an option to do so will appear.) People can also report others in the project for reasons like deleting (lots of) code in an attempt to harm. There will be a curators tab (like in studios), and a button where the owner of the collaboration can restore a version.

Is this rejected?
The answer to this is: I don't know. 2.1 says:

List of rejected suggestions

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations

So it's possible this means that private chat isn't the only problem? However, it could be this is referring to a lack of moderation or something else.

Extra features!
1. A short term “re-wind” (see #22, #24, and #25)
2. Background and user name tag around blocks that are being dragged by a user!
3. the ability to kick someone from a collab (this would remove a person's editing clearance.)

Thanks to B123code for “Extra features!” 2 and 3 (see #26)

Can someone make some mock-ups for this?

List of (maybe) duplicates:
This might be a dupe?

The only issue is that you could have unmoderated chat, and making it public would make it even worse. However, you could apply this to any project so I don't think it's really much of a valid argument.

historical_supa wrote:

The only issue is that you could have unmoderated chat, and making it public would make it even worse. However, you could apply this to any project so I don't think it's really much of a valid argument.

The point of making it public is to not have unmoderated chat so I don't think this makes it worse.

Thanks for the feedback!

This would put a lot of stress on the servers, since they already struggle with cloud variables, and this would transfer WAY more information than cloud variables.

some troll wrote:

ScolderCreations wrote:

This would put a lot of stress on the servers, since they already struggle with cloud variables, and this would transfer WAY more information than cloud variables.

this is another diobolical post from you! I hate you

Not the first time I’ve heard that. Don’t troll, kids

JT_Production wrote:

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations

So it possible this means that private chat isn't the only problem? However, it could be this is referring to lack of moderation or something else.

Yeah, lack of moderation means people could easily share personal information quickly and delete it and nobody would be able to report it.

2nd page BUMP

JT_Production wrote:

historical_supa wrote:

The only issue is that you could have unmoderated chat, and making it public would make it even worse. However, you could apply this to any project so I don't think it's really much of a valid argument.

The point of making it public to not have unmoderated chat so I don't think this makes it worse, and you can't really do this as the current system of collaboration is turn base while this is live.

Thanks for the feedback!

Yes, but some people would be able to have unmoderated conversations in public anyway, which would expose more people to potentially unsafe content.

4th page BUMP

bUMP

Bump

bump (again…)

Due to Scratch limited moderation and technological limitations, communication will have to be removed completely through scratch to remove the problem, but since this is a children coding block app that doesn't allow you to share links with services that allow private chating* it will be impossible to communicate efficiently and safely.

Be safe: keep personal and contact information private. For safety reasons, Scratchers are discouraged from giving out any information that could be used for private communication, in person or online. This includes sharing names or usernames, phone numbers, addresses, hometowns, or links to websites with private chat functionality.

coderwe2 wrote:

Due to Scratch limited moderation and technological limitations, communication will have to be removed completely through scratch to remove the problem, but since this is a children coding block app that doesn't allow you to share links with services that allow private chating* it will be impossible to communicate efficiently and safely.

Be safe: keep personal and contact information private. For safety reasons, Scratchers are discouraged from giving out any information that could be used for private communication, in person or online. This includes sharing names or usernames, phone numbers, addresses, hometowns, or links to websites with private chat functionality.

But it wouldn't be private chatting since anyone could see the project. It's basically a shared project that multiple people can work on at the same time.

Wouldn’t this go against the TOU?

4.3 All user-generated content you submit to Scratch is licensed to and through Scratch under the Creative Commons Attribution-ShareAlike 2.0 license. This allows others to view and remix your content. This license also allows the Scratch Team to display, distribute, and reproduce your content on the Scratch website, through social media channels, and elsewhere. If you do not want to license your content under this license, then do not share it on Scratch.

musicROCKS013 wrote:

Wouldn’t this go against the TOU?

4.3 All user-generated content you submit to Scratch is licensed to and through Scratch under the Creative Commons Attribution-ShareAlike 2.0 license. This allows others to view and remix your content. This license also allows the Scratch Team to display, distribute, and reproduce your content on the Scratch website, through social media channels, and elsewhere. If you do not want to license your content under this license, then do not share it on Scratch.

How would it go against the TOU?

JT_Production wrote:

musicROCKS013 wrote:

Wouldn’t this go against the TOU?

4.3 All user-generated content you submit to Scratch is licensed to and through Scratch under the Creative Commons Attribution-ShareAlike 2.0 license. This allows others to view and remix your content. This license also allows the Scratch Team to display, distribute, and reproduce your content on the Scratch website, through social media channels, and elsewhere. If you do not want to license your content under this license, then do not share it on Scratch.

How would it go against the TOU?

Because everything publically shared one scratch can be used by everyone (as long as credit is given), not just by certain users.

JT_Production wrote:

coderwe2 wrote:

Due to Scratch limited moderation and technological limitations, communication will have to be removed completely through scratch to remove the problem, but since this is a children coding block app that doesn't allow you to share links with services that allow private chating* it will be impossible to communicate efficiently and safely.

Be safe: keep personal and contact information private. For safety reasons, Scratchers are discouraged from giving out any information that could be used for private communication, in person or online. This includes sharing names or usernames, phone numbers, addresses, hometowns, or links to websites with private chat functionality.

But it wouldn't be private chatting since anyone could see the project. It's basically a shared project that multiple people can work on at the same time.

Scratch has a limited moderation and a similar suggestion is already rejected.

JT_Production wrote:

This suggestion is a solution (maybe?) for 2.1 rejected suggestion:

List of rejected suggestions

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations but also because it could lead to private messaging; for more information, see #7.1 on this list. This suggestion includes live editing (similar to Google Docs) and other forms of private collaboration. If you would like to work on a project with another Scratcher, you can remix each others' projects.

Note, I will talk about chat and comments note that these are two different things.

Main idea
The idea is that instead of have a closed project you have an open project that anyone can see. Not every one can edit but they can see all code and comments. The project would be “shared” so people could remix and comment.

Appearance
Collaborations would in a section just under shared projects. In the project editor there is a chat that people can use to send messages. Everyone in the project will see a message icon called the chat (maybe on the button right) showing how many new messages there are. These will also be posted in the comments. Comments will not be posted in the chat and you must have permission to use the chat (however anyone can view it.)

Reporting
If something bad happens like someone say something bad in chat, comments or code block people can report it (to report a code block just right click and a option to do so will appear.) People can also report others in the project for reasons like deleting (lots of) code in an attempt to harm. There will also be a curators tab (like in studios), and a button where the owner of the collaboration can restore a version.

Is this rejected?
The answer to this is: I don't know. 2.1 says:

List of rejected suggestions

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations

So it possible this means that private chat isn't the only problem? However, it could be this is referring to lack of moderation or something else.


Can some one make some mock-ups for this?

List of (maybe) duplicates:
This this might be a dupe?

There was a similar suggestion named share zones I cannot find it rn but it used to exist

musicROCKS013 wrote:

JT_Production wrote:

musicROCKS013 wrote:

Wouldn’t this go against the TOU?

4.3 All user-generated content you submit to Scratch is licensed to and through Scratch under the Creative Commons Attribution-ShareAlike 2.0 license. This allows others to view and remix your content. This license also allows the Scratch Team to display, distribute, and reproduce your content on the Scratch website, through social media channels, and elsewhere. If you do not want to license your content under this license, then do not share it on Scratch.

How would it go against the TOU?

Because everything publically shared one scratch can be used by everyone (as long as credit is given), not just by certain users.

It could be used by anyone by remixing the people of the collab do not necessarily need to remix

The problem is that if there is chat going on, it's non-reportable as the user could just delete the chat before it's seen, so it's pretty much just as bad as private chat.