scratchfoundation / scratch-www

Standalone web client for Scratch
https://scratch.mit.edu
BSD 3-Clause "New" or "Revised" License
1.58k stars 834 forks source link

Consider adding Leave Studio button #5400

Open apple502j opened 3 years ago

apple502j commented 3 years ago

With the current migration of studios, it's a good time to implement new features.

Why add new feature, now?

Users expect that big changes come with some good things (for them; not like "finally free from Django stuff") - and given that Scratch Team rarely adds new features once released, this is a good opportunity to implement this.

Why studio leave button?

First, user's convenience - in big studios, it's very hard to see the username in crowded area. It is also possible that the server/the user's computer cannot handle items such deep in the list. This makes it impossible to leave studios once joined.

Second, user's security - some users do want to leave studios, so they usually run userscripts or browser extensions which include such features (that are advertised against the guidelines, or outside the Scratch Team's moderation). This obviously has negative impact to the overall security of the system, because an important feature is implemented by the community in ways that, when they go wrong, can lead to account compromise.

Third, the reputation - implementing long-requested feature is a good way to increase the reputation of the Scratch Team.

Designs

Studio leave buttons should be placed at the top of the curator page (not the curator section, since that doesn't help when there are many curators.) The button should have confirmation dialog just to make sure people do not click by accident.

The button should not be shown for non-curator/managers. It may or may not be shown for owners; however, if shown, it should be disabled and have the tooltip like "Owners cannot leave studios."

Alternatives

One alternative method I considered is to bump the curator list item so that the user themselves show at the top. However, this does not help when there are many managers and you are the curator. This may also involve excessive API calls due to pagination.

Simple "studio leave" button does not have this problem if placed correctly, and should not require additional API calls, as all it needs is "whether the user is curator/manager" and "whether the user owns the studio", both available on Redux.

Suggestion topic on Leave Studio button: https://scratch.mit.edu/discuss/post/908994/ Note that because this suggestion has been suggested so many times, it might not be the original one.

WorldLanguages commented 3 years ago

Apparently, my "how to leave a studio without finding yourself" tutorial is one of the 2500 most loved projects on Scratch, with over 3,000 loves and 35,000 views. I've been waiting for years for the moment where I can finally unshare my own tutorial for being unnecessary 👌

jemunm378 commented 3 years ago

I think it’s a great idea. It also could be below the "delete" button in "my stuff”.

apple502j commented 3 years ago

(please be respectful, the rules apply here too!)

return-misaPuding commented 3 years ago

I agree. Using userscripts and such to leave crowded studio is unsecure, inconvenient and may be inaccesible for some users who don´t know the tutorial project or the extension. Now that studios are being migrated to scratch-www, it´s the right time to finally implement this

locness3 commented 2 years ago

No update on this?

turtle846 commented 8 months ago

i really want this

devashish2024 commented 5 months ago

I might look onto it.