So in order to fix the problem with the Cloud Variables and Cloud lists, we need to understand the problem. The problem is that with these things, it will be hard to moderate and keep the site safe and friendly.

My suggestion? Make ordinary Scratchers moderators. When a Cloud data piece gets reported, the Scratch Team looks it over and judges whether or not it's malicious. If it is, the Scratcher gets a cool point. If it's fine, the Scratcher gets a strike.

For 5-10(or so, these are my suggested ranges for numbers) cool points, a Scratcher has the option of becoming a Cloud Moderator. Cloud Moderators would check other's projects for bad Cloud use, and have the power to shut it down. Random checks(let's just say in terms of reporter blocks, “pick random 1 to 5) would go to the Scratch team in case of a Scrather turning evil or a hacker.

Strikes: Three-to-five strikes, and you're out. Strikes would occur whether or not you're a moderator. Once you have too many strikes, you lose reporting power for bad use. I realize that they could just create new accounts just for the purpose of trolling(for lack of a better term) but reporting should require Scratcher status, just as use of Cloud data. What new Scratchers could do is add a comment about it in the notes.

I also support an active data swear-word bleeper so Scratchers don't have to build your own. Data would just be sorted through and replace cussing that occurs in the data or notes to be replaced with, ”BLEEP.“ You would still need to report cussing through Paint Editor, though. Text placement in Editor should also have active bleeping, but that would still be easy to work around.

*Problems I have thought of with my ideas:
-Scratch Team still has to sift through a bunch of stuff to elect moderators.
-Workarounds in active bleeper.
-Chat rooms still require a lot of moderators, so this idea still doesn't help their case.
-Moderators won't always catch this stuff and may quit or decline, putting more strain on the ST.

Some pros, however, is that users can be the ”army of moderators" that the Scratch Team doesn't have, and it reduces the workload on everybody in the ST. It also works by supply and demand, when the demand for moderators goes up, we get more.

When I say 3-5 in earlier sentances, I still am only suggesting the range. The lower the numbers are, the easier it is to become a moderator and less work for the ST. The higher they are, the more work for the ST but the better moderators may be.

i agree with most of what you say, but the scratch team should offer someone to be a cloud moderator and they must accept
+
in order for someone to be a cloud moderator they must be a full scratcher beforehand
also cloud moderators should have the power to change a cloud variable but the log gets submitted to the ST so one cant just change a score or something.

The ST said that they are looking suggestions that don't involve large armies of mods, and that is what you are suggesting to create. Even if this were implemented, that would mean that only the Scratchers who visit less kid-friendly projects that are more likely to get inappropriate data would become moderators.
Do not support.

Yeah, I know. I just felt this had a slight possiblity of working. The ST needs all the suggestions they can get.

Once thing I do like about your suggestion is a level between Scratcher and CM. I know this has been suggested before, but it seems like a good idea to bring up. Instead of New Scratcher, we could try to be a bit cooler:

Scratch Kittens => New Scratchers
Scratch Cats => Scratchers
Scratch Leopards => Experienced Scratchers
Scratch Tigers => CMs
Scratch Lions => STs

(Yes, the Mac reference is intentional).

i used to have tiger
on the old ppc architecture