Currently, featured projects are difficult to moderate because when they're unshared, there's no option to report them. And Contact Us is very inconvenient, so I suggest a very easy solution. The servers would be always detecting if a user's featured project is unshared and if the project is unshared, it'll automatically be hiden. This should be very easy to code. Have a detector script and if it detects that it's unshared, it hides the project.

What do you think?

why not just add a report button on the user's page? that seems much more convenient and won't remove banners

subjectnamehere wrote:

why not just add a report button on the user's page? that seems much more convenient and won't remove banners

One reason is that having an unshared featured project is not an intentional feature, so it shouldn't be possible in the first place.

subjectnamehere wrote:

why not just add a report button on the user's page? that seems much more convenient and won't remove banners

Plus, that would scale much better than a script that continually checks every single Scratch user in existence

A better method would be to:

- check if a user has unshared a project that is currently featured
- if the above is true, replace their featured project with their latest project

bump

ajskateboarder wrote:

subjectnamehere wrote:

why not just add a report button on the user's page? that seems much more convenient and won't remove banners

Plus, that would scale much better than a script that continually checks every single Scratch user in existence

A better method would be to:

- check if a user has unshared a project that is currently featured
- if the above is true, replace their featured project with their latest project

Problem there. They could unshare their featured project and upload a new innapropriate project, which could lead to thousands of users being exposed to innapropriate content.

cookiethescratchlynx wrote:

Problem there. They could unshare their featured project and upload a new innapropriate project, which could lead to thousands of users being exposed to innapropriate content.

I mean, it is already possible to share inappropriate projects on the Scratch website, featured on a profile or not. So the described solution doesn't really impact much on that front.

Za-Chary wrote:

cookiethescratchlynx wrote:

Problem there. They could unshare their featured project and upload a new innapropriate project, which could lead to thousands of users being exposed to innapropriate content.

I mean, it is already possible to share inappropriate projects on the Scratch website, featured on a profile or not. So the described solution doesn't really impact much on that front.

Far more people are likely to see it if it's on the * FRONT PAGE rather then on a user profile. This doesn't apply to everyone, but it does to the average user.

cookiethescratchlynx wrote:

Far more people are likely to see it if it's on the * FRONT PAGE rather then on a user profile. This doesn't apply to everyone, but it does to the average user.

By “featured project”, the original poster was referring to the “Featured Project” section of a user's profile, not featured on the the Front Page. It's impossible for unshared projects to be featured on the Front Page.

bring up my post

Better idea is to add a report button for this, as follows:


I've honestly never seen one that's inappropriate - have you?

For example, the one on my profile is unshared - that doesn't mean it's inappropriate…

han614698 wrote:

Better idea is to add a report button for this, as follows:
(snip)

I've honestly never seen one that's inappropriate - have you?

For example, the one on my profile is unshared - that doesn't mean it's inappropriate…

1.

Za-Chary wrote:

#3

subjectnamehere wrote:

why not just add a report button on the user's page? that seems much more convenient and won't remove banners

One reason is that having an unshared featured project is not an intentional feature, so it shouldn't be possible in the first place.

2. Inappropriate unshared featured projects do sometimes appear and I've seen it before.

It's honestly more efficient for them to add a report feature than create a blocking system for unshared projects. Especially since due to the way it works, someone will just get around it again.

han614698 wrote:

It's honestly more efficient for them to add a report feature than create a blocking system for unshared projects.

I disagree with this statement — in order for such a report feature to be effective, it would take quite a bit of work — more work than just adding an option in the reporting box and calling it a day. There are reasons for my doubt, but unfortunately I can't go into much more detail since those reasons involve what the report queue looks like to a moderator.

Even aside from that, I still believe that it doesn't make sense to provide a workaround for something that isn't supposed to be a feature in the first place.

han614698 wrote:

Especially since due to the way it works, someone will just get around it again.

This is speculation on your part. If the Scratch Team were to fix the unshared featured project bug, then naturally nobody can get around it anymore.

ajskateboarder wrote:

- check if a user has unshared a project that is currently featured
- if the above is true, replace their featured project with their latest project

this already happens.

Za-Chary wrote:

han614698 wrote:

It's honestly more efficient for them to add a report feature than create a blocking system for unshared projects.

I disagree with this statement — in order for such a report feature to be effective, it would take quite a bit of work — more work than just adding an option in the reporting box and calling it a day. There are reasons for my doubt, but unfortunately I can't go into much more detail since those reasons involve what the report queue looks like to a moderator.

Even aside from that, I still believe that it doesn't make sense to provide a workaround for something that isn't supposed to be a feature in the first place.

han614698 wrote:

Especially since due to the way it works, someone will just get around it again.

This is speculation on your part. If the Scratch Team were to fix the unshared featured project bug, then naturally nobody can get around it anymore.

It is speculation, but I would be willing to guess that people in the ATs would figure it out. Currently the only information needed for the featured project is the ID and it verifies it is owned by you (if I remember correctly).

On the first thing, I assume you're not allowed to go into more detail about exactly what the report queue looks like and how this would be implementable.

no support, i use a banner and it wouldn't make sense for it to be shared.

ajskateboarder wrote:

A better method would be to:

- check if a user has unshared a project that is currently featured
- if the above is true, replace their featured project with their latest project

what if they have no shared projects?

there goes my purple space image
anyway, just use contact us lol

Banana

han614698 wrote:

It is speculation, but I would be willing to guess that people in the ATs would figure it out. Currently the only information needed for the featured project is the ID and it verifies it is owned by you (if I remember correctly).

A couple of years ago, the Scratch Team made a change with the website that had a consequence of Scratchers not being able to use TurboWarp to view unshared projects. Have people in the Advanced Topics figured out a workaround for that? If they have, do they share such a method? I would assume that wouldn't be allowed.

That being said, the Scratch Team could try both making a system to prevent unshared featured projects and adding a report option for it. Neither would be easy for the reason I said earlier, but I see them as good things to potentially add.

han614698 wrote:

On the first thing, I assume you're not allowed to go into more detail about exactly what the report queue looks like and how this would be implementable.

Exactly.

bring up my post