Banning users from projects via Scratch directly for example if you think someone is behaving inapropiate in ur online game

I bet it is ok.
But they could unban themselves in “see inside”.
It’s not that secure.

If someone is behaving inappropriately, just prevent them from doing so. No need to ban them for something they cannot do, right?

what if someone makes an inappropriate project and bans everyone from seeing it so it can't be reported?
also this(and it's workarounds) would be against the community guidelines since it's not really respectful to entire ban someone from your projects

-Valtren- wrote:

what if someone makes an inappropriate project and bans everyone from seeing it so it can't be reported?

if no one can see the inappropriate project then why would you report it LOL

poomuk wrote:

I bet it is ok.
But they could unban themselves in “see inside”.
It’s not that secure.

the online game doesn't work if you see inside and edit it, it only works if you're the creator

Br3ndon- wrote:

-Valtren- wrote:

what if someone makes an inappropriate project and bans everyone from seeing it so it can't be reported?

if no one can see the inappropriate project then why would you report it LOL

I meant that some people can but not the people who would report it

How about instead of banning the user from the project, you ban them from using cloud variables on your project?

That would be quite easy, just use the username block to check if a user is on a banned people list before allowing them to access the game. If they go inside the project and remove themselves from the list, the cloud variables will not work anymore.

YetAnotherRandomGuy wrote:

That would be quite easy, just use the username block to check if a user is on a banned people list before allowing them to access the game. If they go inside the project and remove themselves from the list, the cloud variables will not work anymore.

Can't you already do something like that though? For example, if “username” is on list “name here”, change something to something, which will prevent them from using cloud.

zomboss1_1 wrote:

YetAnotherRandomGuy wrote:

That would be quite easy, just use the username block to check if a user is on a banned people list before allowing them to access the game. If they go inside the project and remove themselves from the list, the cloud variables will not work anymore.

Can't you already do something like that though? For example, if “username” is on list “name here”, change something to something, which will prevent them from using cloud.

I did that in a project years ago (using the username block to only allow certain users to use the project) and it ended up getting taken down by the ST. Not sure if this sort of thing would fly.

oxiti8 wrote:

zomboss1_1 wrote:

YetAnotherRandomGuy wrote:

That would be quite easy, just use the username block to check if a user is on a banned people list before allowing them to access the game. If they go inside the project and remove themselves from the list, the cloud variables will not work anymore.

Can't you already do something like that though? For example, if “username” is on list “name here”, change something to something, which will prevent them from using cloud.

I did that in a project years ago (using the username block to only allow certain users to use the project) and it ended up getting taken down by the ST. Not sure if this sort of thing would fly.

That makes no sense. Why would they take it down? They essentially do the same thing, on a larger scale. We are just banning them from a project for good reasons.

zomboss1_1 wrote:

oxiti8 wrote:

zomboss1_1 wrote:

YetAnotherRandomGuy wrote:

That would be quite easy, just use the username block to check if a user is on a banned people list before allowing them to access the game. If they go inside the project and remove themselves from the list, the cloud variables will not work anymore.

Can't you already do something like that though? For example, if “username” is on list “name here”, change something to something, which will prevent them from using cloud.

I did that in a project years ago (using the username block to only allow certain users to use the project) and it ended up getting taken down by the ST. Not sure if this sort of thing would fly.

That makes no sense. Why would they take it down? They essentially do the same thing, on a larger scale. We are just banning them from a project for good reasons.

They're moderators who get paid to moderate correctly. You're not. Many people here would just ban people with very poor reasoning

We can see a feature like this being abused. Scratchers might block other Scratchers from using their projects just because they don't like them - or to try and negotiate a favor from them. This goes against the idea that Scratch projects are shared to the entire community.

I understand what might be driving this suggestion - there isn't really a good way to report inappropriate behavior that happens within a cloud project. For now, I suggest using the Contact Us link at the bottom of every page to let the Scratch Team know directly if you are seeing abuse of the Community Guidelines inside a cloud project.