LegoManiac04 wrote:

I thought I'd like it, but my god, it's absolutely horrible. Like, why even be a manager anymore? It's useless. You can't edit descriptions, titles, or thumbnails- I get this helps solve the issue of users promoting people they don't trust, but this is not the answer-

Jeffalo wrote:

they nuked my whole post.

Chiroyce wrote:

Jeffalo wrote:

they nuked my whole post.

they did that because more people would agree with you since it was the first post.

Jeffalo wrote:

yes some parts of my post were a little “unconstructive”, but they nuked my whole post.

Jeffalo wrote:

yes some parts of my post were a little “unconstructive”, but they nuked my whole post.

Jeffalo wrote:

Chiroyce wrote:

Jeffalo wrote:

they nuked my whole post.

they did that because more people would agree with you since it was the first post.

litteraly 1984

CST1229 wrote:

ScratchCatHELLO wrote:

Maximouse wrote:

The only thing studios will still be able to be used for without problems are collections of projects. Any studio that currently has a different purpose will need to find an alternative.

but what alternatives are there?

1. Project
2. User

…that's it (unless they are willing to use the forums, and even then there's few collaboration).

Jeffalo wrote:

While I almost understand some of the reasoning for the changes, I'm very disappointed on how these changes were communicated beforehand… why was there no way for the community to influcence the decision before it was made?

ScratchCat wrote:

Limiting comment threads helps enhance site performance, and prevents long but still active threads from being buried where few people will see new activity. As Scratch continues to grow, it is important to us to continue exploring ways in which we can help keep Scratch running smoothly, safely, and quickly for everyone who uses it. It is our hope that these changes will help do just that! Once a comment thread has reached its limit, you are welcome to start a new thread to continue the conversation.

Now we can view "buried' comment threads by using a comment link, that's one of the actually good features of the new studio page.. But forcing people to create new comment threads will just cause the original comments to get buried even more, and then the comment link isn't useful because the thread continues elsewhere. I am very confused, this update is sending so many mixed signals.

Not to mention that the reply limit was heavily criticized prior to the release, but it seems like all of that discussion was completely ignored.

ScratchCat wrote:

One new feature we are particularly excited about is the “Browse projects” option for when you add projects to your studio. Through this feature, you can add projects you’ve created, projects you have favorited, as well as projects you have recently viewed. You can also still add projects by the project URL.

(view this post)

i'm just going to assume you've never seen this before…



Regarding the suggestion to create a new studio when the owner is inactive, I'm wondering how you expect us to let everyone in the studio know, especially if we can't edit the description, title, or even disable comments.

edit: I thought that the purpose of this topic was for the scratch team to actually respond to peoples questions.. seems like that's not the case.

ScratchCatHELLO wrote:

Maximouse wrote:

The only thing studios will still be able to be used for without problems are collections of projects. Any studio that currently has a different purpose will need to find an alternative.

but what alternatives are there?

Jeffalo wrote:

(note that for scratch legal reasons i no longer agree with any of the statements in this post and i'm just sharing for historic purposes)

dhuls wrote:

Jeffalo wrote:

(note that for scratch legal reasons i no longer agree with any of the statements in this post and i'm just sharing for historic purposes)

What Scratch legal issues? Censorship?

ScratchCatHELLO wrote:

I feel bad for the scratch team at this point, even if the community doesn’t like it, they did work hard on the update and it would suck if something I had been working on for months was hated like this.

ScratchCatHELLO wrote:

I feel bad for the scratch team at this point, even if the community doesn’t like it, they did work hard on the update and it would suck if something I had been working on for months was hated like this.

Maximouse wrote:

ScratchCatHELLO wrote:

I feel bad for the scratch team at this point, even if the community doesn’t like it, they did work hard on the update and it would suck if something I had been working on for months was hated like this.

I don't think there is a reason to feel bad for them. They clearly don't (want to) listen to the community at all, which is very bad for a website with such a large community.

Maximouse wrote:

ScratchCatHELLO wrote:

I feel bad for the scratch team at this point, even if the community doesn’t like it, they did work hard on the update and it would suck if something I had been working on for months was hated like this.

I don't think there is a reason to feel bad for them. They clearly don't (want to) listen to the community at all, which is very bad for a website with such a large community.

Edit: and they aren't following their own CGs either. One of them is “Be honest”, which advertising the Browse projects modal as a new feature isn't. There are no new features and they should admit that.

Jeffalo wrote:

i personally think the backend changes are awesome, i am just not a fan of how they informed us of the new limits.

Jeffalo wrote:

i personally think the backend changes are awesome

            string response;
            try
            {
                response = await client.GetStringAsync($"https://scratch.mit.edu/site-api/comments/user/{username}?page={page}");
            }
            catch
            {
                return NotFound();
            }
            HtmlDocument html = new HtmlDocument();
            html.LoadHtml(response);
            HtmlNodeCollection commentNodes = html.DocumentNode.SelectNodes("//div[@class=\"comment \"]");
            List<Comment> comments = new List<Comment>();
            if (commentNodes == null)
            {
                return Ok(JsonConvert.SerializeObject(new List<Comment>()));
            }
            foreach (HtmlNode node in commentNodes)
            {
                HtmlNode info = node.SelectSingleNode(".//div[@class=\"info\"]");
                HtmlNode user = node.SelectSingleNode(".//a[@id=\"comment-user\"]");
                ScratchCommentAuthor author = new ScratchCommentAuthor(info.SelectSingleNode(".//div[@class=\"name\"]").InnerText.Trim(), user.SelectSingleNode(".//img[@class=\"avatar\"]").Attributes["src"].Value);
                ScratchComment scratchComment = new ScratchComment(int.Parse(node.Attributes["data-comment-id"].Value), info.SelectSingleNode(".//div[@class=\"content\"]").InnerText.Trim().Replace("\n      ", ""), author, DateTime.Parse(info.SelectSingleNode(".//span[@class=\"time\"]").Attributes["title"].Value));
                List<Comment> replies = new List<Comment>();
                if (!node.ParentNode.HasClass("reply"))
                {
                    foreach (HtmlNode replyContainer in node.ParentNode.SelectSingleNode(".//ul[@class=\"replies\"]").ChildNodes)
                    {
                        if (replyContainer.SelectSingleNode(".//div[@class=\"comment \"]") != null)
                        {
                            HtmlNode replyContainerInfo = replyContainer.SelectSingleNode(".//div[@class=\"info\"]");
                            HtmlNode replyContainerUser = replyContainer.SelectSingleNode(".//a[@id=\"comment-user\"]");
                            ScratchCommentAuthor replyContainerUserAuthor = new ScratchCommentAuthor(replyContainerInfo.SelectSingleNode(".//div[@class=\"name\"]").InnerText.Trim(), replyContainerUser.SelectSingleNode(".//img[@class=\"avatar\"]").Attributes["src"].Value);
                            ScratchComment replyContainerUserScratchComment /* :) */ = new ScratchComment(int.Parse(replyContainer.SelectSingleNode(".//div[@class=\"comment \"]").Attributes["data-comment-id"].Value), replyContainerInfo.SelectSingleNode(".//div[@class=\"content\"]").InnerText.Trim().Replace("\n      ", ""), replyContainerUserAuthor, DateTime.Parse(replyContainerInfo.SelectSingleNode(".//span[@class=\"time\"]").Attributes["title"].Value));
                            Comment r = new Comment(replyContainerUserScratchComment.id, replyContainerUserScratchComment, Residence.User, username, true, new List<Comment>());
                            replies.Add(r);
                            comments.Add(r);
                        }
                    }
                    Comment c = new Comment(scratchComment.id, scratchComment, Residence.User, username, false, replies);
                    comments.Add(c);
                }
            }

            var response = await client.GetAsync($"https://api.scratch.mit.edu/studios/{studioId}/comments?offset={(page - 1) * 20}");
            var data = await response.Content.ReadAsStringAsync();
            List<ScratchComment> responseComments = JsonConvert.DeserializeObject<List<ScratchComment>>(data);

Maximouse wrote:

Edit: and they aren't following their own CGs either. One of them is “Be honest”, which advertising the Browse projects modal as a new feature isn't. There are no new features and they should admit that.