Conversation
|
I think the warning should also direct users to the places where they can actually suggest or report to the ST. |
@CST1229 This is the one I thinking to add, but I'm confused about directing to where specifically. Could you suggest what phrashes to add on that sentence? |
3e08605 to
eede01a
Compare
|
Alright, folks. I will expedite this PR to be merged. Expect this to be merged in few days or so. You may still give comments about it. The warnings can be expanded in the future, if we want to handle more cases in the future. As of the "reporting to where" side of things, I haven't got an idea. What I'm considering is that there are multiple ways to report something. Do we direct it to report on the project/user page? Or on the "contact us" page? Or send them an e-mail? Or a forum post? Any other ideas? |
I think it makes sense to link to Contact Us - it has links to the forums and an option to contact the ST directly. The message could also mention the ability to report content on the Scratch website, possibly linking to the wiki. |
|
Ah, I forgot there is the wiki. It explained quite well about the different methods. I think that's the best way, which is to just link it. |
f08a19c to
deac4c8
Compare
This reverts commit bef541e.
This reverts commit bef541e.


As it says, it adds a pre-send check and warning, which checks the message before sending and puts a warning if one or more keywords are detected on the feedback content.
The current form is quite preliminary, and may be improved on this PR based on necessity. Everyone that had access is welcome to edit it.