M1mikyu wrote:

An0therRand0mC0der wrote:

No support. Removing the 25 reply limit would cause lag. Plus, Scratch is for programming, not roleplaying. Roleplaying defeats the whole purpose of Scratch being a coding language.
Support for adding back manager rights though.

There never was lag with comment chains though, at least in my experience.
The text I bolded represents that I'm replying to that text.
They should at least increase the amount of replies, since it’s hard to have detailed discussions with only 25 replies. And there’s other situations where you’d need more replies than just roleplays. What if you’re making a Q&A project and you made a comment asking for people to send their questions in the replies? Or you have weekly questions and want people to respond to that specific comment so all the answers are in one place?

I agree

dhuls wrote:

xX_Unreal_Cool_Xx wrote:

dhuls wrote:

xX_Unreal_Cool_Xx wrote:

making a new comment chain takes up the same amount of space on the servers, if not more, so there is no point.

Cheddargirl once said (forgot where) that it's easier for the servers to load 2 comments with 25 replies each than 1 comment with 50 replies.

that is extremely confusing to me

To simplify this:

(length of [CommentA replies v] :: list) // 25
(length of [CommentB replies v] :: list) // 25
(length of [CommentC replies v] :: list) // 50

You would think it is as easy to load Comment C as it would be to load Comments A and B. But, that is wrong. So when the servers try this:

say (join (CommentA replies::list) (CommentB replies::list))

It would be easier than to try this:

say (CommentC replies::list)

I agree

support.some thing of that update are stu- so thia is why i support the suggestion

Unithlees3 wrote:

M1mikyu wrote:

An0therRand0mC0der wrote:

No support. Removing the 25 reply limit would cause lag. Plus, Scratch is for programming, not roleplaying. Roleplaying defeats the whole purpose of Scratch being a coding language.
Support for adding back manager rights though.

There never was lag with comment chains though, at least in my experience.
The text I bolded represents that I'm replying to that text.
They should at least increase the amount of replies, since it’s hard to have detailed discussions with only 25 replies. And there’s other situations where you’d need more replies than just roleplays. What if you’re making a Q&A project and you made a comment asking for people to send their questions in the replies? Or you have weekly questions and want people to respond to that specific comment so all the answers are in one place?

I agree

I agree too. That is why I support.

I’d say 50% support, remove the manager limits but keep the reply limit. Scratch isn’t really meant for role playing, anyway, it’s programming.

#changethenewstudios
Heavily support!
Heavily support!
Heavily support!
Heavily support!
Heavily support!
#changethenewstudios

Roleplaying isn't a valid argument against the list, this place wasn't meant to be a place to do some wings of fire play or something. But this does limit actual discussion, and none of the Scratch Team's arguments for it actually back it up except for loading times and server problems.

landofgreenandgold wrote:

Semi Support.

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.

If the ST is not going to completely revert it, at least remove most of the new limits and make the layout neurodivergent friendly.

Yeah

An0therRand0mC0der wrote:

No support. Removing the 25 reply limit would cause lag. Plus, Scratch is for programming, not roleplaying. Roleplaying defeats the whole purpose of Scratch being a coding language.
Support for adding back manager rights though.

But isn't there already likes ( social side ), followers ( social side ), and comments ( Can be used for RPing outside of a studio )?

I'd atleast make the reply limit 30, 50, or 100 and/or link the continue thread ( which will be a new comment )

About managers changing title and description, the change might need more thinking. They made the manager title absolutely just cosmetic, and what about studios with dead owners? I support for these reasons, but don't support keepiing the 3.0 layout, it can cause sensory overloads, and I'd think my mockup of a better 3.0 studio layout would help stop these incidents.

I support to remove a few limits, but not all.
I support to remove the 25 reply limit. I rarely saw a comment having 25+ replies. However, it is pointless to keep it a limit, because there is no difference. It obviously doesn't decrease spam, because they can make new comments instead of replying.
I support to have the “Invite Followers” button again. People can invite thousands of their followers, and now you have to type all of that up. Even before Scratchers were complaining to have the “Invite All Followers” button. We need the “Invite Followers” button.
I don't support to remove the manager limitation. That limit was useful, actually. Every time a studio hits a thousand managers, it crashes all the way to 0, because there are mean managers that eject everyone. Plus, it's useless to have over 40 managers. I like that rule.

GunesKing wrote:

I support to remove a few limits, but not all.
I support to remove the 25 reply limit. I rarely saw a comment having 25+ replies. However, it is pointless to keep it a limit, because there is no difference. It obviously doesn't decrease spam, because they can make new comments instead of replying.
I support to have the “Invite Followers” button again. People can invite thousands of their followers, and now you have to type all of that up. Even before Scratchers were complaining to have the “Invite All Followers” button. We need the “Invite Followers” button.
I don't support to remove the manager limitation. That limit was useful, actually. Every time a studio hits a thousand managers, it crashes all the way to 0, because there are mean managers that eject everyone. Plus, it's useless to have over 40 managers. I like that rule.

Ok nice job being respectful

Support as this breaks alot of studios.

No support. This would cause major lag. And you can't just say the load more button because it doesn't mean the thing isn't there.

An0therRand0mC0der wrote:

No support. Removing the 25 reply limit would cause lag. Plus, Scratch is for programming, not roleplaying. Roleplaying defeats the whole purpose of Scratch being a coding language.
Support for adding back manager rights though.

So why is Scratch a community then? Scratch is a place for people to share their work, that's why. Also, roleplaying is just another form of acts and storytelling, it is 100% allowed on Scratch.

-Scratchland- wrote:

An0therRand0mC0der wrote:

No support. Removing the 25 reply limit would cause lag. Plus, Scratch is for programming, not roleplaying. Roleplaying defeats the whole purpose of Scratch being a coding language.
Support for adding back manager rights though.

So why is Scratch a community then? Scratch is a place for people to share their work, that's why. Also, roleplaying is just another form of acts and storytelling, it is 100% allowed on Scratch.

yes, you are right. People need to recognize that Scratch isn't just a programming language, but also a community.

mrcreatorluigi wrote:

I’d say 50% support, remove the manager limits but keep the reply limit. Scratch isn’t really meant for role playing, anyway, it’s programming.

Okay, but you should recognize that

warriorcats2155 wrote:

Scratch isn't just a programming language, but also a community.

No support, many of these limits are apparently necessary, and the ST might not have the money to keep the servers running if the suggestion were implemented.

ScolderCreations wrote:

No support, many of these limits are apparently necessary, and the ST might not have the money to keep the servers running if the suggestion were implemented.

Dude this makes it so hard on the people USING the studios, just because St members don't get paid to use studios all day doesn't mean I don't use studios very often. Update is good, but hard to run that we can't stand it much longer.

hello_smile wrote:

-snip- Each reply or post puts equal load on the server.

That's correct, each individual reply puts an equal load on the server, however, when they are grouped together, the more replies there are, the larger the load.

dhuls wrote:

hello_smile wrote:

Stop lying, LLK. Each reply or post puts equal load on the server.

How would you know they're lying. You don't have back-end access, do you?

Might as well, scratch-www is open-source and the API loads all replies at once for each comment. In fact, new posts would create more load than replies.