(Different from Report featured project on profile )

Intro
Projects on the front page and explore page can be unshared, but still appear on that page (citation needed).
This means the project author can set the title or thumbnail to be something inappropriate or scary and it can’t be reported because the project is unshared.

Suggestion
Add a button in the lower right-hand corner of each thumbnail which opens a menu that allows you to report the project for either an inappropriate thumbnail or title.

Details
The button looks similar to the “edit profile picture” button.
The menu is basically the same as the “report profile” menu, except with the 2 following options:

1. I don’t like it (This option is here to prevent 5 year olds from reporting everything)
   
2. Inappropriate title
   
3. Inappropriate thumbnail
   
4. Doesn’t let me report it (opens a second menu which asks the user to explain what exactly happens when they try to report)
   

Finally, the menu would have a smaller version of the name and thumbnail of the project so the user a make sure they are reporting the right project.

Q&A
Q: But what about shared projects?
A: It would still be there so users don’t have to load the project in order to report it.

Q: Can’t users use “Contact Us” instead?
A: Yes, but the response time can be anywhere from a few days to months so it’s unreliable. Plus, the project author could change the thumbnail to hide the evidence, making it impossible to prove the project author actually used an inappropriate thumbnail.

Q: Would this confuse scratchers: having 2 report buttons for the same project in different places?
A: Possibly, but they could be used interchangeably.

Q: Could this be abused for sending tons of false reports?
A: Yes, but so can the current method. It doesn’t seem to cause issues currently so I don’t see issues arising with this change.

Q: What would the ST do to handle reports? (By han614698)
A: Remove that project from the front page / explore page and then reset the thumbnail to a pure color (white or smth) or reset it to the empty project thumbnail.
Same with title: Reset to “Removed by moderator” or some variation of that.

Mock-up (by Rosics):



Q: Can the ST actually modify titles or thumbnails?
A: Yes to both.
(For thumbnails) proof: https://scratch.mit.edu/discuss/post/8260017/

Notes
If you can/want to, I’d like some concept art for this since I can’t make some myself rn.

What do you expect the ST to do? Unshare the project?

han614698 wrote:

What do you expect the ST to do? Unshare the project?

Reset the title or thumbnail to their defaults:

“Untitled Project” and a blank thumbnail.

SpyCoderX wrote:

( #3 )

han614698 wrote:

What do you expect the ST to do? Unshare the project?

Reset the title or thumbnail to their defaults:

“Untitled Project” and a blank thumbnail.

As far as I know, the ST cannot edit projects.

They can change the title. And they can delete projects. But at least with what I heard through YAB (when we left our projects unshared and the ST shares them for us when they're ready), the ST cannot edit projects.

han614698 wrote:

( #4 )
As far as I know, the ST cannot edit projects.

They can change the title. And they can delete projects. But at least with what I heard through YAB (when we left our projects unshared and the ST shares them for us when they're ready), the ST cannot edit projects.

https://scratch.mit.edu/discuss/post/8260017/

cheddargirl wrote:

We do have the ability to wipe thumbnails, we're currently looking into why it wasn't working this time around.

han614698 wrote:

SpyCoderX wrote:

( #3 )

han614698 wrote:

What do you expect the ST to do? Unshare the project?

Reset the title or thumbnail to their defaults:

“Untitled Project” and a blank thumbnail.

As far as I know, the ST cannot edit projects.

They can change the title. And they can delete projects. But at least with what I heard through YAB (when we left our projects unshared and the ST shares them for us when they're ready), the ST cannot edit projects.

1. The thumbnail isn’t a project in the same way the title isn’t a project. I would guess they have a way of resetting / modifying both.
2. What would limit them? They definitely have the tools for it, since they run the site. The only thing I see is perhaps some sort of contract in the TOS?

Voxalice wrote:

( #5 )

han614698 wrote:

( #4 )
As far as I know, the ST cannot edit projects.

They can change the title. And they can delete projects. But at least with what I heard through YAB (when we left our projects unshared and the ST shares them for us when they're ready), the ST cannot edit projects.

https://scratch.mit.edu/discuss/post/8260017/

cheddargirl wrote:

We do have the ability to wipe thumbnails, we're currently looking into why it wasn't working this time around.

Ah ok, so they can wipe thumbnails, but not edit projects. I'm going to guess it's probably just overshadowing the actual thumbnail with the default as I still don't think they have editing access.

I'm still not sure of the importance here. This sounds like a lot of work to implement and will likely just be misused as it's in a very very public place.

SpyCoderX wrote:

han614698 wrote:

What do you expect the ST to do? Unshare the project?

Reset the title or thumbnail to their defaults:

“Untitled Project” and a blank thumbnail.

Mockup:

Rosics wrote:

SpyCoderX wrote:

han614698 wrote:

What do you expect the ST to do? Unshare the project?

Reset the title or thumbnail to their defaults:

“Untitled Project” and a blank thumbnail.

Mockup:

I like that! Mind if I use it in the main post?

Support. I also know some projects that run code to stop you from reporting. While you can just refresh and not press the flag, could there be an option to report for this?

han614698 wrote:

Ah ok, so they can wipe thumbnails, but not edit projects. I'm going to guess it's probably just overshadowing the actual thumbnail with the default as I still don't think they have editing access.

I'm still not sure of the importance here. This sounds like a lot of work to implement and will likely just be misused as it's in a very very public place.

If I recall, they actually are able - They can also share the project.
They just don't really have the time to be editing someone's project; at best that would be something Contact-Us would have the time for.

Coughfe wrote:

( #11 )

han614698 wrote:

Ah ok, so they can wipe thumbnails, but not edit projects. I'm going to guess it's probably just overshadowing the actual thumbnail with the default as I still don't think they have editing access.

I'm still not sure of the importance here. This sounds like a lot of work to implement and will likely just be misused as it's in a very very public place.

If I recall, they actually are able - They can also share the project.
They just don't really have the time to be editing someone's project; at best that would be something Contact-Us would have the time for.

Well, I know they have the ability to share projects - it's happened to me twice.
I don't believe they are able to edit projects, still, but I do know that they have a button to “clear thumbnail”.

I imagine it wouldn't be too much work to hit a button, alert the user, and move on.

Although I'm not so sure if they can clear the thumbnail of an unshared project, due to how the mechanics likely work.

han614698 wrote:

Coughfe wrote:

( #11 )

han614698 wrote:

Ah ok, so they can wipe thumbnails, but not edit projects. I'm going to guess it's probably just overshadowing the actual thumbnail with the default as I still don't think they have editing access.

I'm still not sure of the importance here. This sounds like a lot of work to implement and will likely just be misused as it's in a very very public place.

If I recall, they actually are able - They can also share the project.
They just don't really have the time to be editing someone's project; at best that would be something Contact-Us would have the time for.

Well, I know they have the ability to share projects - it's happened to me twice.
I don't believe they are able to edit projects, still, but I do know that they have a button to “clear thumbnail”.

I imagine it wouldn't be too much work to hit a button, alert the user, and move on.

Although I'm not so sure if they can clear the thumbnail of an unshared project, due to how the mechanics likely work.

I don't see what's limiting them from modifying unshared projects in the same way they can modify shared projects.

I'm fairly certain they can edit project data (e.g. description, title, instruction…) - I've not had it happen myself, but I've seen screenshots of warning messages of the ST doing this, though it's not common.

AHypnoman wrote:

( #13 )

han614698 wrote:

Coughfe wrote:

( #11 )

han614698 wrote:

Ah ok, so they can wipe thumbnails, but not edit projects. I'm going to guess it's probably just overshadowing the actual thumbnail with the default as I still don't think they have editing access.

I'm still not sure of the importance here. This sounds like a lot of work to implement and will likely just be misused as it's in a very very public place.

If I recall, they actually are able - They can also share the project.
They just don't really have the time to be editing someone's project; at best that would be something Contact-Us would have the time for.

Well, I know they have the ability to share projects - it's happened to me twice.
I don't believe they are able to edit projects, still, but I do know that they have a button to “clear thumbnail”.

I imagine it wouldn't be too much work to hit a button, alert the user, and move on.

Although I'm not so sure if they can clear the thumbnail of an unshared project, due to how the mechanics likely work.

I don't see what's limiting them from modifying unshared projects in the same way they can modify shared projects.

I'm fairly certain they can edit project data (e.g. description, title, instruction…) - I've not had it happen myself, but I've seen screenshots of warning messages of the ST doing this, though it's not common.

And I do not argue with that. I doubt that the ST can edit project data such as code/costumes/sounds etc. I am sure they can edit description, title, and instructions even if the project is unshared.

I don't know how their clear thumbnail feature works.

My guess is that it just covers the other thumbnail with something - doesn't actually edit the project. While that usually works, projects are not meant to appear on explore when they're unshared. So theoretically, there would never be a reason for the ST to clear thumbnails on unshared projects so I'm not sure it would work.

TheAutocorrectingCat wrote:

Support. I also know some projects that run code to stop you from reporting. While you can just refresh and not press the flag, could there be an option to report for this?

I think that would make sense.

han614698 wrote:

AHypnoman wrote:

-snip-

I don't know how their clear thumbnail feature works.

My guess is that it just covers the other thumbnail with something - doesn't actually edit the project. While that usually works, projects are not meant to appear on explore when they're unshared. So theoretically, there would never be a reason for the ST to clear thumbnails on unshared projects so I'm not sure it would work.

I can see your logic. If the thumbnail is reset, the user can just change it back to being inappropriate.

But to your second point, it still happens. I’ve seen unshared projects on explore myself, since it takes so long for projects on explore to be indexed again. (Assuming that’s what removed unshared projects)

Bump (2nd page; 7 hrs since last post)

Is there a reason the QuickReport™ feature should be implemented as opposed to just ensuring that unsharing a project removes it from the Explore page?

Za-Chary wrote:

Is there a reason the QuickReport™ feature should be implemented as opposed to just ensuring that unsharing a project removes it from the Explore page?

a) If the project crashes users who try to load it, it will be unreportable, so it makes sense to have a way to report that project that doesn’t require you to load it.
b) The project could also try to crash the user if they try to report it, which also makes the project unreportable.
c) Just as a backup in case something occurs where normal reporting projects breaks or becomes unusable.

Support, this would be good. I've never seen it myself, but I imagine this could be a problem. Also, the feature to bypass report detectors is excellent. Especially as someone whose internet sometimes cuts out randomly (probably my phone) it'd be nice to save a click.

Bump (from 2nd page)