so basically, my suggestion ISN'T a warning for inappropriate projects or projects that arent suitable for certain ages, my suggestion is that when you click on a certain project (lets say this project uses alot of flashing lights) a message would cover the project so you couldn't see it until you click the green flag again and it would say:

Are you sure you want to view this project? It contains ………………
Click the green flag to continue.

i understand that people could just put a warning in the desc but not everyone reads the description, especially when it has alot of tags and writing! i think this would be very helpful for alot of people example: people who have epilepsy!

thankyou for reading!

h3artsanri0 wrote:

so basically, my suggestion ISN'T a warning for inappropriate projects or projects that arent suitable for certain ages, my suggestion is that when you click on a certain project (lets say this project uses alot of flashing lights) a message would cover the project so you couldn't see it until you click the green flag again and it would say:

Are you sure you want to view this project? It contains ………………
Click the green flag to continue.

i understand that people could just put a warning in the desc but not everyone reads the description, especially when it has alot of tags and writing! i think this would be very helpful for alot of people example: people who have epilepsy!

thankyou for reading!

inappropriate projects should be reported to the scratch team, scratch is for all ages any way.

the_awsome_penguinja wrote:

inappropriate projects should be reported to the scratch team, scratch is for all ages any way.

In some cases, projects are appropriate for Scratch, but contain certain elements that might be harmful - like flashing lights.

Why can't such projects be NFE'd though?

Where would this warning pop-up on? The project page? Or the loading part of the page? And also, how would this stop scratchers from viewing a potential inappropriate project?

the_awsome_penguinja wrote:

h3artsanri0 wrote:

so basically, my suggestion ISN'T a warning for inappropriate projects or projects that arent suitable for certain ages, my suggestion is that when you click on a certain project (lets say this project uses alot of flashing lights) a message would cover the project so you couldn't see it until you click the green flag again and it would say:

Are you sure you want to view this project? It contains ………………
Click the green flag to continue.

i understand that people could just put a warning in the desc but not everyone reads the description, especially when it has alot of tags and writing! i think this would be very helpful for alot of people example: people who have epilepsy!

thankyou for reading!

inappropriate projects should be reported to the scratch team, scratch is for all ages any way.

i know, this post is about warnings for sensetive content/to help people with epilepsy and stopping them clicking on a dangerous project say with flashing lights

PaperMarioFan2022 wrote:

Where would this warning pop-up on? The project page? Or the loading part of the page? And also, how would this stop scratchers from viewing a potential inappropriate project?

loading part, and it would be used to stop people from seeing sensetive content, like repetetive flashing lights

How come the project owner can't just put TWs in the description or before the project?
The description is there to y'know, be read.

This might sound abit offtopic but it'll rail in even if it makes barely any sense.
I honestly just won't say anything, except — On my main account, my test animations infact could use this so I don't have to unshare them.
I just want to say this could be both bad or useful as ST would have to review your project, which would take ages as god knows how many projects are being shared a day. That is specifically why you can do things like this. Custom reasons would be annoying even with a filter because people might bypass, although if you can pick a warning reason via a dropdown, that still doesn't stop people from just not putting any in the first place.
That's why some people like I do just do this
(I actually did this also, due to bugs and just because of flashing lights.)
And the thing is, this is a good idea, yes. But it can easily be ignored and abused by people who simply don't care or are raiding the site, or overall causing problems.

Support, although this'd need ALOT of work to be enforcable.

Zydrolic wrote:

This might sound abit offtopic but it'll rail in even if it makes barely any sense.
I honestly just won't say anything, except — On my main account, my test animations infact could use this so I don't have to unshare them.
I just want to say this could be both bad or useful as ST would have to review your project, which would take ages as god knows how many projects are being shared a day. That is specifically why you can do things like this. Custom reasons would be annoying even with a filter because people might bypass, although if you can pick a warning reason via a dropdown, that still doesn't stop people from just not putting any in the first place.
That's why some people like I do just do this
-snip-
(I actually did this also, due to bugs and just because of flashing lights.)
And the thing is, this is a good idea, yes. But it can easily be ignored and abused by people who simply don't care or are raiding the site, or overall causing problems.

Support, although this'd need ALOT of work to be enforcable.

A lot of animators already do what you gave an example of or put a TW in the description.
This idea, while meant to be good for everyone and help make Scratch friendly, would take a bit of enforcement to implement. Even then, they still might provide warnings the same way we do currently.

Crazibot wrote:

(#10)
A lot of animators already do what you gave an example of or put a TW in the description.
This idea, while meant to be good for everyone and help make Scratch friendly, would take a bit of enforcement to implement. Even then, they still might provide warnings the same way we do currently.

Yup, I know. Infact I mentioned these:

Zydrolic wrote:

(#9)
-snip-
And the thing is, this is a good idea, yes. But it can easily be ignored and abused by people who simply don't care or are raiding the site, or overall causing problems.
-snip-
Support, although this'd need ALOT of work to be enforcable.

Zydrolic wrote:

Crazibot wrote:

(#10)
A lot of animators already do what you gave an example of or put a TW in the description.
This idea, while meant to be good for everyone and help make Scratch friendly, would take a bit of enforcement to implement. Even then, they still might provide warnings the same way we do currently.

Yup, I know. Infact I mentioned these:

Zydrolic wrote:

(#9)
-snip-
And the thing is, this is a good idea, yes. But it can easily be ignored and abused by people who simply don't care or are raiding the site, or overall causing problems.
-snip-
Support, although this'd need ALOT of work to be enforcable.

Was just restating the points since they're very notable in this case. Sorry, I didn't make that clear!
I probably should state my own stance.
Semi-Support. Comes from a light-hearted place but the feature may never be used or could be abused.

Crazibot wrote:

(#12)
Was just restating the points since they're very notable in this case. Sorry, I didn't make that clear!
-snip-

Nah, I just realized I misunderstood it, not your fault, dw. Apologies.

Anyways ST might need alot of donations to be able to implement this (They are nonprofit.), but hey this is a good suggestion.

Easy workaround: Just put a TW in the description or somewhere in the project, like the thumbnail.

Scratch--TheCat wrote:

Easy workaround: Just put a TW in the description or somewhere in the project, like the thumbnail.

But not just that. People also make inside sprite project warnings before a scratcher views that project or this project. But yes, those are some good workarounds.

Scratch Gift

If this was implemented, it should be set to only preset options. Letting people type whatever they want is not a good idea. If someone wants to set a warning for their project, they should be given a list of options. There should also be a list of warning options like "jumpscare" to where if you click it, it would say that isn't allowed.

Scratch--TheCat wrote:

Easy workaround: Just put a TW in the description or somewhere in the project, like the thumbnail.

Not everyone reads the description, especially if there are pretty symbols / tags / capitals that take attention anyway from the trigger warning.

Zydrolic wrote:

as ST would have to review your project, which would take ages as god knows how many projects are being shared a day.

Replying to Zydrolic: A user can add the message themselves

Other ways to improve this suggestion:

B) There could be pre-set warning options:
This contains flashing lights // This contains unpopular opinions // This contains spiders/bugs/tiny holes (only those ones because there's a phobia for pretty much everything but these are very common) // This project may trigger people with (example-medical-condition)
B1) And an option to customise one: “This project contains ______” but the blank is the only customisable part
C) New “Report this project” option: “Uses trigger Warnings incorrectly”