Allow managers to MANAGE STUDIOS

KN1Rises

SavetheAtlantic wrote:
I think it's fine the way it is and if this suggestion is implemented, it will cause the opposite effect because the Scratch community hates change.

Correction: The Scratch community hates bad changes. Good changes they like.

12 | male | Christian

join the cor

SavetheAtlantic

KN1Rises wrote:
SavetheAtlantic wrote:
I think it's fine the way it is and if this suggestion is implemented, it will cause the opposite effect because the Scratch community hates change.
Correction: The Scratch community hates bad changes. Good changes they like.

The community hated both 3.0 and 2.0 when they came out ¯\_(ツ)_/¯

ContagiousAnimations

I'm not sure what the point was of changing the studios so drastically, it only hurt the studios. I don't think we've even had so much as an explanation as to why??? Scratch, please repair the studios!

when I receive [ContagiousAnimations]
set [Motivation] to [Low]
if <[Followed?] = [Yes]> then
say [Thank you] for (2) secs
end

jackson49

ContagiousAnimations wrote:
I'm not sure what the point was of changing the studios so drastically, it only hurt the studios. I don't think we've even had so much as an explanation as to why???

I disagree with the manager change, but they gave an explanation for many of the changes:

cheddargirl wrote:
The way studios were operating was pretty much starting to get unsustainable for the website.

Source

cheddargirl wrote:
This big decision was made due to internal and budget issues, and that kind of stuff can override wishes of a majority and even the ST, at times.

Source

cheddargirl wrote:
The previous system with having unlimited comments was contributing to lag, especially for studios that were constantly refreshed and had long comment chains. It's not an easy decision to make, but we have to put in place to prevent things from lagging further.

Source

Last edited by jackson49 (June 9, 2022 03:38:12)

Be moist

PC LOAD LETTER

;

sushicat11129

Support! I've been thinking the same. And if the managers are abusing the power, they could make the owner a toggle on and off button not for projects or comments but for if the managers can access the desc or not

bentshaggyoil

come on people this is too old to still be talking about

Don’t comment ladder on my profile.

https://scratch.mit.edu/projects/711602448/

sushicat11129

bentshaggyoil wrote:
come on people this is too old to still be talking about

No it's not. It happened quite recently

bentshaggyoil

sushicat11129 wrote:
bentshaggyoil wrote:
come on people this is too old to still be talking about
No it's not. It happened quite recently

Alright fair enough but almost a year ago doesn’t seem very recent

Don’t comment ladder on my profile.

https://scratch.mit.edu/projects/711602448/

NecroAnvil

bentshaggyoil wrote:
sushicat11129 wrote:
bentshaggyoil wrote:
come on people this is too old to still be talking about
No it's not. It happened quite recently
Alright fair enough but almost a year ago doesn’t seem very recent

So? People can still discuss about this suggestion because it is still relevant, though I'd agree that people have moved on, and if the ST reimplements this, it would be very controversial.

foruming terminology is complex

popjam12

Half support. There should be an option for the owner to toggle this, in my opinion.

Highlight + ctrl + shift + down to see the rest of my signature
*BEST VIDEO EVERRRR!!!!!*
150 FOLLOWERS :D :D :D

I will voice act.

sushicat11129

popjam12 wrote:
Half support. There should be an option for the owner to toggle this, in my opinion.

That's what I said. We should have a toggle for the owner only so if a manager is abusing the desc, they can turn it off using the toggle.

Thethree13

Yeah I agree there are now arguments about it and it totally sucks

bump

KangaCoder

This suggestion to revert manager restrictions back to 2.0 studios is rejected and is listed in TOLORS

Za-Chary wrote:
5.4 Revert back to older versions of the studio pages
The Scratch website has to update sometimes to accommodate certain changes. In particular, the Scratch 3.0 studio pages were created to improve website performance and the studio experience. Changing the studio pages back to these older versions would not only undo months of hard work by the Scratch Team, but they also may not be sustainable in the long run anymore. More information on why these changes were made are stated in this topic, and frequently asked questions are listed in this topic.

@cheddargirl stated in the topic linked in TOLORS:

cheddargirl wrote:
We won't be changing it back since the way studios were operating was pretty much starting to get unsustainable for the website. We're open to suggestions that build on top of the one we have put in place, but conversion to old stuff is going to have to be a no-go.

This includes reverting back the less restrictive manager limits, so, this suggestion is therefore rejected.

(Note that this 5.4 only applies to changing studios back to their old versions, not adding new features, like the toggle idea mentioned above)

don't feed the trolls. feed yourself pizza cupcakez

.[1] [2] [3] [4]

KangaCoder • [he/him] • kæŋɡəˈ koʊdər

• Random Fun Facts: Male, Christian, US resident, EST time zone, Ravenclaw, likes Math and Science, learning German, knows HTML, Python and Java, loves chocolate, favorite color, possibly a kangaroo
• On the Main Site: Experienced Wikian, Camp Counselor, SWC Reviewer, SDS Helper, Forum Helper
• On the Forums: 2.65K+ forum posts
•

Project Ideas Directory 6.0 - need a project idea? Check it out!
• Check out some weird and cool Scratch pages!

Discuss Scratch