This has been bugging me to extremes, so I'm going to put in a really in-depth solution.

To be honest, cloud variables have been one of the worst implemented features in Scratch. They're not pointless, just almost unusable. I hate to say that, but it's unfortunately true. It is almost impossible to create really cool things when you're limited to ten number-only variables. This isn't even talking about numerous glitches, this is talking about lack of features.

This has so long been debated with chatrooms and such that I thought in addition to my complaint I might actually try to suggest a bit of a solution.

My solution involves two kinds of cloud variables: Normal Cloud Variables and Chat Cloud Variables.

Normal cloud variables and lists can do everything the same as chat lists. They're displayed in the same old log, etc. Same rules apply - no passwords, no chat, etc. “But wait, no chat?” Wait…

Chat cloud LISTS are different. They are stored in the log as well, BUT they are also conveniently displayed below the project, constantly updating. AND, these are view-able whether the project is showing you it or not (it doesn't make noise, and it could be hidden as an option. But it's just an idea). It also tags users with their usernames.

If someone misuses cloud data variables (normal ones) and uses it for inappropriate use including chat, the project is blocked and the account is dealt with as normal. The log will have some sort of report button. But with chat lists, it gets interesting.

At the bottom, with the feed of chats, if someone sends out something horrible the user can easily report them. There is a report button next to the chat that will bump those chats so as to show them to users. If more users report them, eventually a moderator will look at it and deal with it as necessary.

Here's what gets you into trouble:

Normal variables/lists:
-Inappropriate Links
-Sharing of usernames and passwords of others.
-CHAT
-Swearing and cussing.
-Basically, if it violates the community guidelines…

Chat lists:
-Being rude
-Swearing
-Community Guidelines again…

IF someone misuses data or chat cloud stuff, they can have their access blocked for all projects. This prevents them from continuing what they're doing.

Please, people, add onto this. I'd like to get the Scratch Team cooking up some solutions so we can have our beloved cloud lists back, and our dreams of chatrooms. This can't be impossible, it just needs work! Please support this. And thank you.

BTW Scratch Team, removing community moderators doesn't make moderation easier, FYI

I really don't see what the problem would be with just making it so you can't make a free chat.

Another thing is that this wouldn't fix any of the glitches, so I really don't know how helpful this would be. And, it seems like it would be a bit annoying to have a list of cloud data that I couldn't hide under every project. (Would it be in full screen mode?)

Also, I really don't like the sound of variables that have the word “chat” in their title. That's just my opinion.

The problem with cloud variables at the moment, is actually the servers - especially since the influx of users from Hour of code.

ssss wrote:

The problem with cloud variables at the moment, is actually the servers - especially since the influx of users from Hour of code.

No… if you are talking about why chat lists aren't being used, it's because the scratch team hasn't been able to effectively monitor them yet.

FireNinjaGAME wrote:

This has been bugging me to extremes, so I'm going to put in a really in-depth solution.

To be honest, cloud variables have been one of the worst implemented features in Scratch. They're not pointless, just almost unusable. I hate to say that, but it's unfortunately true. It is almost impossible to create really cool things when you're limited to ten number-only variables. This isn't even talking about numerous glitches, this is talking about lack of features.

This has so long been debated with chatrooms and such that I thought in addition to my complaint I might actually try to suggest a bit of a solution.

My solution involves two kinds of cloud variables: Normal Cloud Variables and Chat Cloud Variables.

Normal cloud variables and lists can do everything the same as chat lists. They're displayed in the same old log, etc. Same rules apply - no passwords, no chat, etc. “But wait, no chat?” Wait…

Chat cloud LISTS are different. They are stored in the log as well, BUT they are also conveniently displayed below the project, constantly updating. AND, these are view-able whether the project is showing you it or not (it doesn't make noise, and it could be hidden as an option. But it's just an idea). It also tags users with their usernames.

If someone misuses cloud data variables (normal ones) and uses it for inappropriate use including chat, the project is blocked and the account is dealt with as normal. The log will have some sort of report button. But with chat lists, it gets interesting.

At the bottom, with the feed of chats, if someone sends out something horrible the user can easily report them. There is a report button next to the chat that will bump those chats so as to show them to users. If more users report them, eventually a moderator will look at it and deal with it as necessary.

Here's what gets you into trouble:

Normal variables/lists:
-Inappropriate Links
-Sharing of usernames and passwords of others.
-CHAT
-Swearing and cussing.
-Basically, if it violates the community guidelines…

Chat lists:
-Being rude
-Swearing
-Community Guidelines again…

IF someone misuses data or chat cloud stuff, they can have their access blocked for all projects. This prevents them from continuing what they're doing.

Please, people, add onto this. I'd like to get the Scratch Team cooking up some solutions so we can have our beloved cloud lists back, and our dreams of chatrooms. This can't be impossible, it just needs work! Please support this. And thank you.

BTW Scratch Team, removing community moderators doesn't make moderation easier, FYI

From what I know, the current problem with chat lists isn't so much that the Scratch Team can't track what user says what; scratch coding can store usernames. However the Scratch Team just can't currently look through every project on scratch that would use cloud chat; it's just too tedious.

pigletdiglet wrote:

ssss wrote:

The problem with cloud variables at the moment, is actually the servers - especially since the influx of users from Hour of code.

No… if you are talking about why chat lists aren't being used, it's because the scratch team hasn't been able to effectively monitor them yet.

READ THIS BEFORE SUGGESTING ANYTHING

Stuff that is still in progress but will be here later
Let me know when they are implemented!
1. Cloud lists and strings
The server still needs to be set up.

I do know what I'm talking about.

How about a chat room that only invited people can use it? if you only add people you trust, and they add people they trust, it should work, no?