Codingfairy07 wrote:

dhuls wrote:

Codingfairy07 wrote:

This falls through a category of a rejected suggestion:

9.6 Polls in the forums
Some Scratchers have suggested optional polls that could be implemented into forum threads so users can vote on a particular suggestion, state that they experience the same glitch as someone else, or for other reasons. However, the Scratch Team is less interested in polling results and more interested in constructive posts on the forums. Although polls could theoretically reduce the number of unconstructive posts, they likely would not help Scratchers think constructively and write constructive posts. This suggestion includes polls that Scratchers can create themselves, as well as pre-made polls.

This isn't about forum polls, so it isn't rejected.

But it still is about polls.

forums polls ≠ polls

This is good, because the ST needs to ask the users more often. Especially the studio update.

bump

pavcato wrote:

A lot of people left because of 3.0 because it wasn't what the expected so suggest allowing Scratchers vote for the updates they want. It will only let Scratchers vote because there could be account spamming problems. It should feature similar features together to vote like “Do you want this placement of this or this placement of this?”. I think it could be a solution to unwanted changes caused by major updates. The poll should be placed on the front page to maximize responses

Even though 4.0 isn't coming soon, I still think we should vote so we won't have a terrible 3.0 profile update.

pavcato wrote:

A lot of people left because of 3.0 because it wasn't what the expected so suggest allowing Scratchers vote for the updates they want. It will only let Scratchers vote because there could be account spamming problems. It should feature similar features together to vote like “Do you want this placement of this or this placement of this?”. I think it could be a solution to unwanted changes caused by major updates. The poll should be placed on the front page to maximize responses

bumpity bumpity bump

Support! I don't really like the studio update, and we could've voted it down if this was already implemented. I can see this being useful in the future as well for the profile/my stuff update.

full/strong support to this

sihan666666 wrote:

full/strong support to this

Please give a reason

I think their should be scratch coins people can pay for. and people can make it cost scratch coins to play their game. and make things in their scratch games cost scratch coins to get.

pavcato wrote:

imabanana22 wrote:

4.0 wont come out for the next decade… Semi-support

I know… that's why I made it now. And it's actually coming out in 4 years.

No. Source?

Anyway, support. I think the Scratch Team should publicly say what they're gonna do, get our feedback, tweak things from there, release a beta, tweak things from there, and release.
Also, why are people saying “scratch 4 isnt coming out”? That has nothing to do with this. For example, the studio update release, but it has nothing to do with Scratch 4.0.

djfjaaaa wrote:

I think their should be scratch coins people can pay for. and people can make it cost scratch coins to play their game. and make things in their scratch games cost scratch coins to get.

A) Please don't derail this topic.
B) If you want to, you can make a new suggestion here.
And:
C) That is rejected:

The Official List of Rejected Suggestions wrote:

8.7 Digital currency or Scratch achievements
Some form of digital currency which allows you to “buy” Scratch features (with real or fake money) would not really benefit the educational value of Scratch; after all, there is not really anything that you can buy. While there could be features that are only unlockable via digital currency, this does not really contribute to Scratch's purpose of being a programming language available for everyone. However, you can make digital currency in your own projects, if you like. A very good detailed analysis for why digital currency should not be on Scratch can be found on this post.

The Scratch team do not implement suggestions here due to the number of supports, so they should not implement suggestions using a voting system either - it is always the reasoning behind the pros and the cons, and whilst many may support and vote on a suggestion, they are completely oblivious to the larger cons, but since tonnes of people voted, the Scratch Team now have to implement the feature that is worse. So I think the Scratch Team should just carry out there own research and make a verdict on what feature is better to add. instead of letting the communtiy decide, as harsh as it may sound.

i agree, ive seen a ton of complaints about the studio update lately, which are all valid complaints. and i think this is a good way to make sure everyone (or at least most people) are happy with new updates. i'm pretty sure if we had the option to vote, the studio update would not exist. and instead of reducing spam of people you follow inviting you to their studios, it just causes people you don't follow to invite you, which i think is worse honestly. because, if i don't want any future invites from a certain person, i could just unfollow them, but now i can't do anything about all these invites from strangers.

(sorry i kinda bashed the studio update, was just using it as an example as i wasn't here for scratch 2.0)

Note: I am not making a new suggestion. I am merely edifying this pre-existing one.

I think it would be better if the Scratch Team allowed other users’ constructive input while considering to implement something, instead of them giving all users the ability to vote outright. I provide the following objections for that line of reasoning in the OP:

1. First of all, it’s more constructive than just adding a vote. It’s similar to the Suggestions forum, actually. The Scratch Team should look into others’ input, yet ultimately make the decision themselves.
   
   
2. This would not necessarily prevent users from creating alternate accounts to manipulate the number of users that vote on an idea. This would be an entirely new form of spam never seen before on Scratch: voter fraud.
   
   
3. What if the users come to a decision the Scratch Team didn’t like? The Scratch Team gets no say in it; the Scratchers do.
   

If we made it so that users could give input in an update, they’d still understand the general consensus, but also why or why not, and how they can improve on the idea. Agree?

What updates specifically? Updates as in 2.0-3.0, or other minor updates as well? Would only the scratchers votes count? How would this page be issued? And besides, 4.0 isn’t coming o until JavaScript and (insert coding language I forgot here) are both dead. That will not happen in decades, so this feature would be kind of useless until then. And besides, I feel like this kind of would feel spammh and rapid if they were for minor updates. I lack any support given.

dertermenter wrote:

.. So I think the Scratch Team should just carry out there own research and make a verdict on what feature is better to add….

Ideally their research should include some involvement from us, their stakeholders.

The studio update could have been smoother if they had asked the community if the current studio owners all wanted to become solely responsibly for certain abilities that at the time were shared with all managers. The capacity change around reducing the quality of the studio and user pictures could have been smoother if they had announced this as a necessary change and asked us to submit some example pictures to help them with their research of this change. Some of the suggestions in this forum date back to 2013 with no direction provided or even interest shown by any of the developers.

For example, are they thinking that custom reporters are “low-floor enough” to be added someday? Do they want to know what kind of search options people would use the most if they could implement something but not everything? Would they consider adding an extension that contained example workarounds, and which ones? (Which could make it easier for beginners to find and use small script examples. Jetpack girl, for example, used to be a sprite in the sprite library that had an example movement script).

And I would even take the voting idea as a way to send feedback to the ivory tower if that was the only option.

pavcato wrote:

imabanana22 wrote:

4.0 wont come out for the next decade… Semi-support

I know… that's why I made it now. And it's actually coming out in 4 years.

No, it is not coming out in 4 years. Even though scratch team released 1 to 2 and 2 to 3 every 5 years, there are no definite plans for a further update

Bump

bump

B U M P I T Y B U M P B U M P