There need to be better ways of reporting people for hacking cloud variables. Unless they commented about the fact they are hacking variables, there is no easy way to report them. Maybe something like this?



Also another thing, if a project has a cloud leaderboard for example, and it gets hacked to be inappropriate, instead of taking it down scratch team should just reset the cloud variables or disable them temporarily.

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

Maybe on the “report” button on a project, instead of the profile. There could be a check saying “cloud variables have been hacked” and then you could type the username.

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

Agreed

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

Maybe this is what you're talking about (sorry I don't know what you mean), but I think it should be the thing that comes up when you click the “see data” button, or go here: https://scratch.mit.edu/cloudmonitor/[PROJECT ID]/

bump

Elijah999999 wrote:

Maybe on the “report” button on a project, instead of the profile. There could be a check saying “cloud variables have been hacked” and then you could type the username.

No support for this post. The project will taken down if it is mass reported. All problems to the creater of the project, not the hacker.

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

I agree with you. Which is why I do not support.

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

Even for this, would the Scratch Team actually decode it? If they just saw 876654456783133213879008876374865900383629007464848124958351, would they actually go inside the project and figure out what it means?

k7e wrote:

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

Maybe this is what you're talking about (sorry I don't know what you mean), but I think it should be the thing that comes up when you click the “see data” button, or go here: https://scratch.mit.edu/cloudmonitor/[PROJECT ID]/

Right, that's what I'm referring to.

k7e wrote:

Even for this, would the Scratch Team actually decode it? If they just saw 876654456783133213879008876374865900383629007464848124958351, would they actually go inside the project and figure out what it means?

No, unless maybe it was immediately clear by looking at the project what was changed. But I was under the impression that sometimes hackers can update the cloud variables so that the cloud log itself says bad words (maybe I'm misremembering).

Crispydogs101 wrote:

I agree with you. Which is why I do not support.

Or you could just… list other ways how to improve the suggestion so it could work, rather than flat-out withdrawing any support.

-TwentyFour- wrote:

Elijah999999 wrote:

Maybe on the “report” button on a project, instead of the profile. There could be a check saying “cloud variables have been hacked” and then you could type the username.

No support for this post. The project will taken down if it is mass reported. All problems to the creater of the project, not the hacker.

I never said the project would be taken down. It would just get the ST's attention quicker. Besides, it's already possible, I was just suggesting a more convenient method.

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise, the Scratch Team has no way of knowing what project the user hacked cloud variables on.

If you click the cloud variables area, you can see everyone who has made a change to the cloud variables, scratch should allow you to select one or multiple changes, and then report those changes

There was a dupe, so…


EDIT: Also I cannot think of any point to say currently so I won't say anything else for now

I mean, couldn't the reporter tell ST what the decoded version is (or tell them where the code for the decoder is)?

no support for 2 reasons:
somebody could make a project with some code buried far down that checks if your username is somebody the creator doesn't like, and sets the leaderboard to have something inappropriate from them, with it still being in their name on the logs. then, once the user gets banned, they could edit the project to remove the code.

also if you're connecting via python you can just create a new account and use that without even verifying the email.

Za-Chary wrote:

I feel like it would be better to have a Report button on the cloud variable log itself, rather than the user's profile. Otherwise the Scratch Team has no way of knowing what project the user hacked cloud variables on.

I agree it just seems strange to report it this way

So to get around all of these issues


Just make the page 3.0 styled so people can do “other” then type out details and what the variable does so they can understand why it’s not a normal value to reach

I had a comunity going until a scratch team member decided to get rid of it.

we worked hard and we got canceled. this is a ghost town

29bbean11 wrote:

we worked hard and we got canceled. this is a ghost town

Just tell everyone to come here now instead, Maybe copy and paste a summary of the old discussion to here.