nickeljorn wrote:

What if a user fakes been an adult?
Well, what if the option only came after you viewed a certain number of NFE projects? This would show that you are mature even though you are not an adult.

maturity isn't viewing more adult content, it's being able to handle more adult content. and even if a certain kid out of every few users is mature enough to handle the more mature side of scratch, it's scratch's responsibility to make sure no kid sees that content at all, because you really can't make many exceptions when you're trying to make a platform universally family-friendly.

Hmm, semi-support. It should be an automatic only FE projects, and then maybe under Account Settings an option to allow NFE. Sometimes it's really difficult to find NFE projects and studios. If it's something kids absolutely can't see, it shouldn't be on Scratch. A lot of NFE things are just controversal, have gif thumbnails, etc., so yeah. It shouldn't be that easy to turn off the filter, it should have a warning and stuff, and probably say “Ask your parents”, but other than that turning off the filter could be beneficial.

Edit: Should only be for Scratchers, not New Scratchers. Also, the reason I'm only semi is because of all the cons people have listed.

I don't think this would work. Children could somehow get past the whole process of being allowed to search NFE projects, and end up disobeying their parents more easily.

Wasn't the whole point of creating the NFE rating to allow projects that were borderline in terms of content to stay on the website but to hide them by not letting them be viewable in search or on the front page so that people who have just started Scratch or are searching around don't end up gaining an expectation that making NFE content is the norm? This suggestion would undo quite a bit of that work.

What about only full scratchers can turn it on, and it is not obvious?

Support, This feels like something that everyone should have acess to
and if anyone is worried that they will find something bad
1. This a kids site, it's not like they will come across anything inaporperate
2. just make it so u have to be a Scratcher to turn it off

bump

Seems like too much work to view a project…

littleMAHER1 wrote:

2. just make it so u have to be a Scratcher to turn it off

Why would a user need to be a scratcher to turn it off.

I feel like this falls under the “+13” alternative site thing rejected suggestion.

I don't see why they decide to filter FNAF. From what I see the comments above, I can easily summarize a fact that “if someone wants to see something, they will stop at nothing to obtain it”. I just don't see anyway to prevent kids from wanting to play those games.

The easiest solution will be to have a system that detacts if a project that is too scary for kids and give a warning before the kid can press the green button. If the kid still doesn't stop there, than I think the kid clearly knows what he/she is up to.

People shouldn't be making those projects anyway. Just keeping it NFE works perfectly, and I don't see the need to change it.

a lot of kids will use their own emails for their scratch accounts

WolfCat67 wrote:

DownsGameClub wrote:

Mmmm… I'm not sure if that's a good idea. Some kids may be tempted to see material that is questionable, or sometimes not allowed by parents.

Here's an idea to counteract that:
You are NOT allowed to search for NFE projects at first.
You can, however, send a request to your parent's email to ask whether or not you're allowed to view this material. If you're not allowed, then you can't use it and the search bar works the same as normal. If you are allowed, then instead of having the filter, NFE projects will now be able to appear in search results.

What if you are older than 13?

What if your an adult lol

No support, makes them more find-able but defeats the purpose of NFE.

nickeljorn wrote:

So certain words and phrases are blocked from the Search and Explore. Same with NFE projects. But what if you could press a button to toggle seeing projects like those in Search?

FAQ:

• What if users see questionable material?
  (Thanks WolfCat67 for answer) Here's an idea to counteract that:
  You are NOT allowed to search for NFE projects at first.
  You can, however, send a request to your parent's email to ask whether or not you're allowed to view this material. If you're not allowed, then you can't use it and the search bar works the same as normal. If you are allowed, then instead of having the filter, NFE projects will now be able to appear in search results.
  
  
• What if a user fakes been an adult?
  Well, what if the option only came after you viewed a certain number of NFE projects? This would show that you are mature even though you are not an adult.
  

Can't you just bypass it by putting a - after your search?
Such as FNAF-

WolfCat67 wrote:

DownsGameClub wrote:

Mmmm… I'm not sure if that's a good idea. Some kids may be tempted to see material that is questionable, or sometimes not allowed by parents.

Here's an idea to counteract that:
You are NOT allowed to search for NFE projects at first.
You can, however, send a request to your parent's email to ask whether or not you're allowed to view this material. If you're not allowed, then you can't use it and the search bar works the same as normal. If you are allowed, then instead of having the filter, NFE projects will now be able to appear in search results.

Another way is adding a verify age option.

CatsUnited wrote:

Wasn't the whole point of creating the NFE rating to allow projects that were borderline in terms of content to stay on the website but to hide them by not letting them be viewable in search or on the front page so that people who have just started Scratch or are searching around don't end up gaining an expectation that making NFE content is the norm? This suggestion would undo quite a bit of that work.

exactly

the point of nfe is that its unsearchable to the public eye without having the link
this has too many holes to be enforcable and could potentially cause some coppa law issues.
i mean really this is probably impossible to enforce no matter what you do without prying into privacy

edit: i miss-spelled the [wp][/wp] tag on accident but thats fixed