Oop I just realised @LegoManiac04 had the same idea on the 5th page of ‘Pronouns in comments but less vague’, I have a feeling I subconsciously stole it from them lol, credit to them as well

Edit 3: Please do not discuss whether this is necessary because it ‘only saves one click’ or similar. We have already wasted 200 posts on this topic, and we are considering it unresolved for now. Please do not waste more posts on this.

Edit 2 : Oof I'm sorry I meant to edit this but I ran out of time and then completely forgot…Can do a big edit tomorrow when I get off this stupid device…

Epik mockup by @musicROCKS013:

– Please read the ENTIRE post before responding! –

So.

I've been seeing a lot of topics about implementing pronouns in comments, but the associated controversy seems to be about neopronouns and whether they should be included. Including all the neopronouns would be nigh on impossible, but not including any could be seen as homophobic, and only including some would be unfair to the others.

The solution: What if we don't just include pronouns - what if we include the whole About Me? PLEASE PLEASE THIS SOUNDS CRAZY BUT HEAR ME OUT

Next to a person's username in their comment would be a little grey information symbol or question mark. Hovering over or tapping/clicking this question mark would open a miniature popup - tooltip-style but bigger and with a scrollbar - displaying the user's About Me. Users usually put their pronouns in the top of their About Me, making them visible at a glance - and then Scratch doesn't have to worry about making a list of ‘valid’ neopronouns!

There are other advantages too - users could put other things they might want users to know in there, like if they need trigger warnings or feel disrespected by or dislike certain topics. And we don't have to worry about reporting, because the exact same text would be displayed on the user's profile and is already fully reportable.

This is a simple and efficient way to display information about a user, and eliminates the need to click off the page. So what do you think? Did I miss any cons? If not, I hope this can be implemented soon!

Really nice idea! I guess the grey info symbol will become light grey when hovered and display information when clicked so that it can also be helpful for mobile users. Support

about me's are huge, how do you expect them to get put in every single comment? what would be the point of the about me then?
no support.

-Valtren- wrote:

about me's are huge, how do you expect them to get put in every single comment? what would be the point of the about me then?
no support.

try reading.

I really like this idea. It won't only benefit people who want their pronouns known, it will benefit everyone! It also keeps the site looking simple.

Just a few concerns: What happens if your about me has countless “return” spaces, such as mine? Making the mockup, I simply had to snip it. Maybe it could do something similar?

Mockups:

I'm just going to play devil's advocate but the convenience of saving one click does not outweigh the development time to do this

SavetheAtlantic wrote:

I'm just going to play devil's advocate but the convenience of saving one click does not outweigh the development time to do this

You know it's a good suggestion when the only con is, “could take time to implement.”

This wouldn't be impossibly hard, because the About Me is already stored in a user's API. This would also make the about me more useful impactful, and make users be more engaged when typing in it.

musicROCKS013 wrote:

SavetheAtlantic wrote:

I'm just going to play devil's advocate but the convenience of saving one click does not outweigh the development time to do this

You know it's a good suggestion when the only con is, “could take time to implement.”

That doesn't mean anything. The con outweighs the pro of "I don't want to click a link :("

And just a reminder for the people saying “it takes 2 seconds” it also takes 2 seconds to make the workarounds for at least a dozen blocks. Some of these include if else, all of the change ___ by () blocks, the arithmetic operations, and ‘or’ and ‘and’ booleans.

This could help! Support.
It would be easier then complaining at someone and getting into drama because somebody got your pronouns wrong.

SavetheAtlantic wrote:

I'm just going to play devil's advocate but the convenience of saving one click does not outweigh the development time to do this

Sir, Ma'am, Mx, whatever you are.
Yeah uhh things take time. How is that a con?

DashaTheAroace wrote:

Yeah uhh things take time. How is that a con?

It takes away time from other things that could be getting done on the site, such as bug fixes and such. This isn't the most serious con. It isn't really a problem with the suggestion, or something that the OP can fix, it's really a problem with Scratch Team and how they never have time to implement suggestions like this.

musicROCKS013 wrote:

DashaTheAroace wrote:

Yeah uhh things take time. How is that a con?

It takes away time from other things that could be getting done on the site, such as bug fixes and such. This isn't the most serious con. It isn't really a problem with the suggestion, or something that the OP can fix, it's really a problem with Scratch Team and how they never have time to implement suggestions like this.

Oh right

(removed)

VioletCalico wrote:

(removed)

???????

musicROCKS013 wrote:

I really like this idea. It won't only benefit people who want their pronouns known, it will benefit everyone! It also keeps the site looking simple.

Just a few concerns: What happens if your about me has countless “return” spaces, such as mine? Making the mockup, I simply had to snip it. Maybe it could do something similar?

Mockups:

Thanks! I was thinking there could be a scrollbar on the side of the popup to deal with that.
—-
Will respond to other stuff later

Eagle138 wrote:

Thanks! I was thinking there could be a scrollbar on the side of the popup to deal with that.

Good idea!

Updated mockup:

musicROCKS013 wrote:

Eagle138 wrote:

Thanks! I was thinking there could be a scrollbar on the side of the popup to deal with that.

Good idea!

Updated mockup:

Perfect! I will put it in the OP as soon as I get a chance.

This is a really great solution to a common suggestion. Not only does it save the ST the concern of what pronouns to exclude or include, and what should be the option for “prefer not to say” it also allows for things like a bit more context when talking to people (e.g., whether someone does f4f or not).

portalpower wrote:

And just a reminder for the people saying “it takes 2 seconds” it also takes 2 seconds to make the workarounds for at least a dozen blocks. Some of these include if else, all of the change ___ by () blocks, the arithmetic operations, and ‘or’ and ‘and’ booleans.

Ok, and? This isn't about those blocks, this is about this suggestion.