Bump.

Support!

Support!

No support, sorry.
If a project isn't for everyone, simply report it. Voilà

I think it's an interesting idea, but Scratch was created for all ages so all projects should be able to be viewed by all ages, and many people will look at projects even if it's rated ‘NFE’ just for the excitement of it. Plus, the scratch team would be overloaded with having to review EVERY shared project. So I'm sorry, but no support.

Support 1000%!

LeoBernard wrote:

No support, sorry.
If a project isn't for everyone, simply report it. Voilà

That's not the suggestion…

No support. There's a workaround, but I only know the windows version. What you have to do is go to the project, then press ctrl+shift+J. I don't know What the equivalent for Apple computers is, but once I find it out, I'll edit this and tell you.

wWSunPandaWw wrote:

No support. There's a workaround, but I only know the windows version. What you have to do is go to the project, then press ctrl+shift+J. I don't know What the equivalent for Apple computers is, but once I find it out, I'll edit this and tell you.

Rightclick and select inspect element on any device, then look for ‘no index’ using ctrl or cmd F.

wWSunPandaWw wrote:

No support. There's a workaround, but I only know the windows version. What you have to do is go to the project, then press ctrl+shift+J. I don't know What the equivalent for Apple computers is, but once I find it out, I'll edit this and tell you.

It would be better to have users see if the project is NFE or FE without having to go to Inspect Element. Most don't even know what Inspect Element, we don't need to do everything by using Inspect Element, it is just not worth it! Also, determining what script can detect us a project is NFE or FE can be difficult since not everyone is an expert at JavaScript. They are probably experts in other languages.

Besides, if you only know the Windows Version but not the others versions remember that not all users have Microsoft Windows.

wWSunPandaWw wrote:

No support. There's a workaround, but I only know the windows version. What you have to do is go to the project, then press ctrl+shift+J. I don't know What the equivalent for Apple computers is, but once I find it out, I'll edit this and tell you.

This is like handing someone a car without car keys.

Now they have to hotwire it to get it started. Think about that in the context of younger kids trying to find out why their project isn't viewable in the search results?

Just because there's a specific and technical way to do something, doesn't mean there shouldn't be (especially an indicator of some sort) a useful tool to help start it.

Would you like doctors to perform surgery in the most basic of ways? No. So why the same with a Scratch Project?

Yeah, I support. I know that there is a workaround, but I don't think younger kids will go into Console and use the code just to find out why their project isn't showing up.

girlsruless wrote:

Support 1000%!

lord have mercy on the necroposters

Did I support this yet? If not, you know what comes next :-)

Semi-Support - It might segregate the community.

myeducate wrote:

Semi-Support - It might segregate the community.

Well it'd certainly be nice to know if the project you're about to view might contain something a 4-year-old wouldn't want to see, you never know. NFE projects already exist, so at least a warning would probably be helpful if you're about to view one. I don't see how a simple warning will split the community.

Support! Most people wouldn't want to have to go into the console just to see if their project is NFE.

██       ██  ██            ██  ██       ██
██       ██  ██            ██  ██       ██
██       ██  ██     ██     ██  ██       ██
██       ██  ██     ██     ██  ██       ██
███     ███   ██   ████   ██   ███     ███
 █████████     █████  █████     █████████

Support

st19_galla wrote:

The Suggestion:
I think we should be able to see if a project has been marked NFE, FE, or Unreviewed.

For those who don't know: When a Scratch Team member reviews a project, they will either mark it as ‘FE’ (For Everyone, meaning the project has no restrictions placed on it) or ‘NFE’. (Not For Everyone, meaning the project cannot appear on the front page) For more information, see here: http://wiki.scratch.mit.edu/wiki/NFE#Not_For_Everyone

Reasons:
This would be good because:

1. If you're waiting for your project to be placed on the front page (top-loved, top-remixed, etc.) you will know ahead of time if your project is aloud. By the time Scratchers figure out it was marked NFE, fix why it was marked NFE, get a ST member to remove the NFE status, the time it should've been on the Front Page will most likely be gone.
   
2. I have seen loads of comments from FPC's on ST's profiles saying “Why wont this project go on the front page?” It's normally because its marked NFE. They now have to explain to the project creator that even though they said they would curate it, they can't because its marked NFE. A ‘Project Status Bar’ would let them know ahead of time if it is NFE.
   
3. You don't have to leave a comment on an ST's profile asking if your project is NFE or FE anymore.
   

Demonstration:
Here's what a project marked NFE would look like:

Obviously, this is a rough drawing and would look loads better than this. Also, when you hover your mouse over the ‘Status’, a small bar will pop up saying "This project was marked Not For Everyone. (NFE) This means it can not appear on the Front Page. For more information, please see here: http://wiki.scratch.mit.edu/wiki/NFE#Not_For_Everyone. If you think this project was wrongly marked, please send a message to https://scratch.mit.edu/contact-us/."

Supporters:
The following people support this suggestion:

1. St19_Galla
   
2. DaSpudLord
   
3. scrooge200
   
4. TheHockeyist
   
5. Cream_E_Cookie
   
6. Deerleg
   
7. Vyuss
   
8. Rollercoasterfan
   
9. -SuperScratch-
   
10. Hamish753
    
11. applesauceepicness
    
12. crimson19
    
13. Co49
    
14. fmtfmtfmt2
    
15. coolgem923
    
16. shaymin88
    
17. skelepound
    
18. Nether_before
    
19. letsgopitt
    
20. Samanyolu
    
21. Medley7
    
22. Znapi
    
23. IronBit_Studios
    

Conclusion:
If you have any questions, please ask! Also, if you do not support, please say why :D

If there is a topic similar to this, please let me know and I will have this closed! I looked, but I could not find any.

They should also say the reason why it's marked NFE.

megaman100 wrote:

They should also say the reason why it's marked NFE.

Definitely. Otherwise, you wouldn't know what's wrong. I think it'd be good to have this so you have better control over how your projects are seen by the ST.

No support - it could cause problems like:

• People treating projects/creators of NFE projects differently, like not loving or favouriting
  

• Comments about the fact it is NFE
  

• Causing people to keep reporting the project
  

• A consideration of NFE projects to be more “mature” than other projects