Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it very clear that we are not the Scratch Team on the feedback page #500

Conversation

CST1229
Copy link
Member

@CST1229 CST1229 commented Nov 4, 2024

i am going insane. everyone keeps addressing us as "scratch team", or filling in the username field with the placeholder "ScratchCat", asking us to ban users or unban them or themselves (ok i wrote this in a sliiiiight fit of rage)
image

i am going insane. everyone keeps addressing us as "scratch team", or filling in the username field with the placeholder "ScratchCat", asking us to ban users or unban them
@Samq64
Copy link
Member

Samq64 commented Nov 4, 2024

I suggested this in #439 a while ago and Hans disagreed.

Edit: #500!

@Hans5958
Copy link
Member

Hans5958 commented Nov 5, 2024

My point still stands on #439 (comment). Take a time to read it again.

Perhaps, if I had time, I would convert this into a modal that would really put focus on the message instead. I will open this for the time being.

@WorldLanguages
Copy link
Member

It's unfortunate that our feedback page has quite good SEO

@WorldLanguages
Copy link
Member

@CST1229 This probably won't be very effective. Most likely, we rank quite high for "Scratch feedback" on Google, or similar. Meanwhile, most of our users probably go through the "Send Feedback" button on the settings page, instead of search engines.

A better solution is to tell Google not to index /feedback. For those people actually searching for a way to send "Scratch Addons feedback", we can allow Google to index a different page/doc that itself provides a link to /feedback. A disclaimer like this could fit there.

@CST1229
Copy link
Member Author

CST1229 commented Nov 23, 2024

superseded by #506

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants