This article or section may not have content matching Scratch Wiki editing standards. Please improve it according to Scratch Wiki:Guidelines and Scratch Wiki:Editing Conventions. (December 2020) |
The Review Status of a Project is a status given by the Scratch Team, and only visible to the Scratch Team. This status determines the visibility of the project, and if the project can appear on the Front Page, the remix tab of another project and if it can appear in search results.
Statuses
There are four statuses a project can be in. The first is for a project has not been reviewed yet, and the other three of them are for projects that have been reviewed.
Unreviewed
When a project is uploaded, it is automatically placed in the "unreviewed" category. A project is in this category until it is reviewed by a member of the Scratch Team. Projects in this category have no restrictions placed on them. The majority of projects are unreviewed due to the immense amount of projects constantly being uploaded to the site.[1]
For Everyone
If a project has been reviewed and deemed appropriate for the Scratch community, it is marked For Everyone (FE). Like unreviewed projects, projects in the For Everyone category have no restrictions placed on them.
Not For Everyone
If a project is deemed inappropriate for the community, but not inappropriate enough to be censored or removed, it is marked Not For Everyone (NFE). These projects cannot get onto the Front Page, will never appear in the search results, and will not appear under the remixes tab in the Project Page if it is a remix project. Some reasons that projects get marked as NFE include:
- A certain amount of blood (the exact amount is hard to tell)[2]
- Intense cartoon violence
- Mildly inappropriate language or content
- Minor violations to the Community Guidelines
However, inappropriate content is not the only reason a project can get marked NFE. Projects using animated thumbnails may also get marked NFE because they may lag the front page;[3] although some users may not notice the lag, this could be very annoying to some users. If someone uses other accounts to love or remix a project, created by themselves or another person, multiple times to get it Front Paged, it will be marked as Not for Everyone,[citation needed] and that user may receive an alert on their messages page.
Removed
Sometimes, the Scratch Team will unshare a project if it breaks the Community Guidelines. If a user other than the creator or a Scratch Team member tries to access the project afterwards, the user will be shown a 404 error page.
If a project was unshared, the creator of the project can usually reshare it after taking the inappropriate content out. However, in some cases, the ability to share the project was permanently disabled.[4] If the user wishes to reshare a project that was permanently unshared, they may contact the Scratch Team.
Reporting
- Main article: Report
To report a project, one can click the "Report" button below the project. The user will be asked to select a reason from a drop-down menu. After that, they will be asked to give the Scratch Team more information on why the project breaks the Community Guidelines. Once this is done, the project appears on a page visible to the Scratch Team that lists reported projects. They will review it, and mark its review status.
The same process is used to feature a project, but instead of taking the project down, they click on a feature button on the admin panel for projects.[normal report or?]
Community Censor
If a project is reported multiple times by multiple people, it is automatically censored until reviewed by a Scratch Team member. In Scratch 1.4, when one visited the project, they used to be shown Gobo giving a message about reporting,[citation needed] but in 2.0 and 3.0, it has been replaced with a 404 page.
See Also
Links
References
- ↑ scratch:statistics#projects
- ↑ post:4763522
- ↑ cheddargirl. (24/03/2015). "...using an animated thumbnail can result in your project being marked as NFE because animated project thumbnails can make the front page laggy." post:876154
- ↑ topic:202769