Topic Join request button for studios:
Category: studios
Description: There should be a request to join button for studios
Keywords: studio, request to join

overview/basis
My suggestion is that scratch should add a feature, or more specifically, a button on studio pages where users can request to join. When they click the button, they should also be able to add a note (message) as some studios require users to fill out a form before joining. Obviously, these messages/notes should follow community guidelines and so, the same restrictions (as normal commenting) should be placed on them (like limit of characters etc). These requests + messages should be then sent to the host and all managers of the studio. When the host/managers receive the notification (in their inbox), they should be able to view the user who sent the request + the studio they requested to join + their message + an option to decline/accept with a short message (to apologize to/welcome the user). Then, the user who requested is sent a notification accepting/declining their request. If they are accepted, they are sent a curator invite so that they can decide if they still want to join that studio.

The suggestion (in detail): https://scratch.mit.edu/projects/1032213131
(i unshared the project as it didn't seem to be getting views, if you still want the longer version and see this suggestion in detail, let me know and i'll reshare the project.

Note: I spent way too long on it and it wouldn't let me post as it ‘appeared to include unsuitable language’. So, I put it on a comment/sticky note inside a project, sorry, I hope it's not too much trouble!

– Snowynight

I think this is a pretty good suggestion that could be useful. I did find some issues that I felt were worth pointing out, though:

-SnowyNight- wrote:

they should also be able to add a note (message) as some studios require users to fill out a form before joining

That could be used for private messaging, so I don't think this part should be added if the suggestion becomes accepted. The scratch team is very, VERY strict about preventing private messaging which means they would not add such a feature in the first place if it allowed for private messages. This also includes the other message part:

-SnowyNight- wrote:

an option to decline/accept with a short message (to apologize to/welcome the user)

Solution: scratch team just doesn't add this part of the suggestion
The next part I had an issue with was the benefit of this suggestion. It's easy to ask in the comment section of the studio or on a manager's profile, and any manager who cares about their studio will be active enough to add users. Sure, I agree that it would make it easier, but it wouldn't be a huge difference. This isn't a very big problem and can be ignored.
The final issue I had isn't very important, it's mostly just a small opinion:

-SnowyNight- wrote:

If they are accepted, they are sent a curator invite so that they can decide if they still want to join that studio.

I feel that the curator being sent an invite would be unnecessary as they specifically requested to be in the studio. You did provide a reason that makes sense, which is why this isn't an important issue, but I just thought it was worth pointing out.
Overall, I think your suggestion is pretty good and these issues aren't super important. You did a good job on describing it in detail, which is pretty cool since not a lot of people do that.

Thank you for your input, I appreciate it Though one comment on something you said:

Xzillox wrote:

That could be used for private messaging, so I don't think this part should be added if the suggestion becomes accepted. The scratch team is very, VERY strict about preventing private messaging which means they would not add such a feature in the first place if it allowed for private messages. This also includes the other message part:

I expanded more on this feature in the project (the link to which i shared). This wouldn't be considered ‘private messaging’ and the host as well as all the managers would receive this message. And, this is why I mentioned in the extended version that the requester would only be allowed to send 1 message (with the request) and the manager/host would only be able to send 1 message (anonymously as well). However, I can see where you're coming from, and if this appears to be an issue for the ST as well, removing it would be a good idea.