eikh2 wrote:

This would only make sense if it's a part of live commenting, which is a rejected suggestion:

Za-Chary wrote:

6.4 Live commenting or streaming
This refers to some system where you would not need to refresh the webpage to see new comments that are posted. Some Scratchers think this would be convenient if you are engaged in a conversation with someone so that the conversation moves more quickly (somewhat like how texting works). However, aside from the technological barriers this would bring, it would also put a greater emphasis on the social media aspect of Scratch, moving the focus away from the project-creating aspect. Indeed, project creating is intended to be the primary focus of Scratch.

Streaming is similarly rejected, as is video chat, as they are forms of live commenting. With streams, it is easy to share personal information without anyone being able to report it, which the Scratch Team does not want to risk. Although one solution would be to have the Scratch Team moderate the streams, they do not have the resources to do that effectively.

5C1AdrianAu wrote:

eikh2 wrote:

This would only make sense if it's a part of live commenting, which is a rejected suggestion:

Za-Chary wrote:

6.4 Live commenting or streaming
This refers to some system where you would not need to refresh the webpage to see new comments that are posted. Some Scratchers think this would be convenient if you are engaged in a conversation with someone so that the conversation moves more quickly (somewhat like how texting works). However, aside from the technological barriers this would bring, it would also put a greater emphasis on the social media aspect of Scratch, moving the focus away from the project-creating aspect. Indeed, project creating is intended to be the primary focus of Scratch.

Streaming is similarly rejected, as is video chat, as they are forms of live commenting. With streams, it is easy to share personal information without anyone being able to report it, which the Scratch Team does not want to risk. Although one solution would be to have the Scratch Team moderate the streams, they do not have the resources to do that effectively.

This is technically NOT rejected

IloveRoblox003 wrote:

The problem is that Scratch API is slow. And I mean slow, it can take minutes for a comment to be sent out server-wide after it was locally sent.

Also, think about hatman, hatman would just be able to clog up comment sections even more with this feature.

FreshTheCat wrote:

This would bring the same technological barriers as live commenting, and might consume at least a bit more server space, since the servers would have to store the usernames of each user typing on the comment.
So i'd say it would fall under the live commenting rejection

spiningCat_gamez wrote:

It could be better if in mail (which is live) and have it say “typing…” from whoever’s typing then show message in mail

TLoRS wrote:

6.4 Live commenting or streaming
This refers to some system where you would not need to refresh the webpage to see new comments that are posted. Some Scratchers think this would be convenient if you are engaged in a conversation with someone so that the conversation moves more quickly (somewhat like how texting works). However, aside from the technological barriers this would bring, it would also put a greater emphasis on the social media aspect of Scratch, moving the focus away from the project-creating aspect. Indeed, project creating is intended to be the primary focus of Scratch.

Streaming is similarly rejected, as is video chat, as they are forms of live commenting. With streams, it is easy to share personal information without anyone being able to report it, which the Scratch Team does not want to risk. Although one solution would be to have the Scratch Team moderate the streams, they do not have the resources to do that effectively.