(Redirected from Frequently Rejected Suggestions)
|
This article has links to websites or programs outside of Scratch and Wikipedia. Remember to stay safe while using the internet as we cannot guarantee the safety of other websites. |
This is a list of frequently suggested and rejected suggestions on the Scratch Suggestions forum.
Scratch Blocks
“broadcast received” boolean block
( v) received?::events boolean
It is too ambiguous what would cause the value to be true; it could be whether the broadcast has ever been received since the project was created, since the green flag was clicked, since any other broadcast was sent, or whether the "when I receive X" blocks are still executing/have finished, or whether the broadcast was sent on that same frame.[1] As such, the workaround for the block depends on what the use case for the block is, and what it is meant to do. However, a "last broadcast received" reporter block has its own open suggestion, the blocks "repeat until () received" and "wait until () received" have their own suggestion as well.
"when stop sign clicked" hat block
when @stopSign clicked::events hat
The stop sign is intended to stop all scripts, not to start other scripts.[2] However, workarounds exist using the timer block.
"pointing towards sprite" boolean block
<pointing towards ( v)?:: sensing>
This block would allow a sprite to detect if it is pointing towards another sprite. However, it is ambiguous when it would trigger; whether it would return true if any part of the sprite facing towards any part of the other sprite, whether the center point of the sprite is facing the center point of the other sprite, or whether the center point of the sprite is facing an part of the other sprite.[3] The workaround depends on how the block is intended to work; it might be whether the direction is equal to what "point towards (other sprite)" would set the direction to, or it might be whether or not continuously moving in the sprite's direction would result in touching the other sprite before touching the edge. Alternatively, it could mean whether or not a ray extending from the source sprite's center would touch the target sprite.
Social action reporter blocks
(number of [loves v]::sensing)
This block could allow projects to know how many people have viewed/loved/favorited it. That would go against Scratch's focus on creating programs and focus too much on the social aspects of Scratch. This rejection extends to all social actions, including views, loves, favorites, remixes, comments, and followers.[4]
Cloud lists
(☁ list ::list)
Currently, cloud variables have several restrictions. Users can create no more than 10 in one project, each with a limit of 256 numeric digits (effectively a few more using the negative/positive and the decimal point).[5] All of these limits are in place to manage storage costs and to discourage the use of cloud variables for disallowed purposes (such as chat rooms). Even if only numbers were allowed in the lists, cloud lists would still too easily facilitate the creation of projects with disallowed uses of cloud variables. Ultimately, in addition to the variable limit and length limit, lack of lists is simply another limitation of cloud data.
2D lists
add () to (),() in [2d list v]::list
2D lists are a type of data structure that allows for the value of a list item to be another list; in other words, putting lists inside lists. These sorts of data structures are used widely in other programming languages, but the Scratch Team considers them too complicated for Scratch.[6]
The feature is available in Scratch modification Snap!.
3D Scratch
go to x: () y: () z: ()::motion
3D Scratch would allow projects to be three-dimensional. However, this would be complicated with many cameras settings and different types of 3D models. This could also lag browsers. Many existing blocks in Scratch may also not work.[7]
Snap!'s 3D Beetle extension, CreatiCode, Starlogo TNG and Alice contain 3D features.
Blocks that control the mouse pointer
hide mouse pointer::looks
Blocks that could be used to move, hide, or set the mouse-pointer to an arbitrary costume, would confuse users when their mouse-pointer disappears or gets stuck[8].[9]
However, changing the look of the mouse-pointer to one of the default mouse-pointers is not rejected and is currently being discused.
“Forever if” C block
forever if <> {
} @loopArrow :: control cap
This block was in the Scratch 1.4 editor, and worked the same as putting an "if block" inside a "forever” loop. It was removed in Scratch 2.0 because many beginning Scratchers were confused on how the block worked; [10] whether it was the same as an if-block inside a forever-loop, or whether it was the same as a forever-loop inside an if-block. Not having an ambiguous block and instead putting the two blocks together manually removes this ambiguity and gives users more control over how the project runs.
Comment block
comment []:: grey
The comment block, by design, does nothing. It would be used to put notes inside a script, instead of the current system of commenting code. While this block was present in a 1.2 beta, it was later removed, as it confused beginners, who expect every block in the block palette to do something. Additionally, there is a simple workaround:
define \/\/ [text] \/\/ [comment text here]
“Jump to code” block
A block similar to 'goto' statements in other programming languages would make programs less structured and harder to read and write.
The Coding Interface
Ability to add other users to edit the same project
Some users would like an option to work with other users, directly, by editing the same project in real-time. However, having multiple Scratchers able to edit the same project at the same time would make it unclear who made what parts of the project, which is important for attribution. In addition, editing projects in real-time would enable private messaging.[11] Users can still collaborate by remixing each others' projects, leaving a clear record of who made what.
At the moment, a turn-based collaboration system for shared projects is not rejected, and can be discussed on this topic.
Text-based Scratch
Some users wish to code Scratch not with blocks, but by typing code instead, similar to how more advanced programming languages work. Or want to convert Scratch code to other programming languages.[12] The feature, while potentially useful to those already familiar with Scratch and getting started with other programming languages, is considered outside the scope of Scratch's target demographic of beginning programmers. Tosh is a text-based version of Scratch similar to this feature.
An ability to make the editor look like older versions of Scratch
Some users prefer the layout of old versions of Scratch and want to be able to revert to them. However, this would require the Scratch Team to maintain multiple versions of the Scratch UI, and would make different users' Scratch editors look different, making it more difficult to follow tutorials or what other Scratchers are doing.[13] In addition, the UI changes were made for a reason, and the ability to undo them undermines this and potentially results in an experience where some users see things that other users do not.
Official Scratch to executable converter
Some users would like an option to convert Scratch projects to an executable. However, Scratch is designed to have everything be open source, so that users can see how projects work and tinker with them. If a project was converted to a black box executable, or even to an interpreted language like JavaScript, that would be lost.[14] While it is not against the Community Guidelines to use unofficial converters, the Scratch Team will not officially release one.
Removing or raising the clone limit
Some users would like to change the limit on the maximum number of clones. However, the clone limit is to stop problems on low-end devices.[15] Raising the limit only on higher-end devices would also result in inconsistency in how Scratch projects behave; they should work the same on every computer, and this means setting limits that ensure all sorts of different computers can run them equally well.
Scratch for video game consoles
The Scratch Foundation does not have the resources (money to buy devkits, time to program Scratch in a console compatible language, etc).[16] USB controller support is not rejected, and there is currently an open topic discussing it.
Allow text/symbols in cloud data
This would allow people to store usernames and other text in cloud variables. However, as described above, this feature would also be too easy to abuse to create chat rooms and other forms of disallowed content. [17]However, it is possible to simulate letters in cloud variables by encoding and decoding numbers.
AI image generator
The Scratch Team is concerned about ethical issues related to generative AI,[18] and the possibility to show biased and inappropriate content. However, generating images on external sites and adding them to Scratch projects is allowed.
Scratch Projects
Allowing cloud chats
Allowing cloud chats will not happen because of the potential of bullying. You can still have the user select from a predetermined list of phrases. You can also have it be "fill in the blanks"(for example, allowing users to send messages like "hi [user in the game]" or "i am at [place in platformer game]".[19] Cloud chats like this were not disallowed because someone could say a swear word, but out of non-swear words, or they could say things like "you suck" or "you are not good at making scratch projects".[clarify]
Ability to disable remixing a project
One of the most important features of Scratch is the share aspect; sharing a project is agreeing to it being remixed.[20][21]Scratchers should have the freeom to remix things they see on the Scratch website, so every project needs to be under the same license. If Scratchers do not want a project to be remixed, they can simply not share it to the Scratch website.
Disallow projects that do not have code
Scratch encourages creativity via means other than coding, such as art or music.[22]
Remove the automatic project unsharing of projects after multiple reports
The system is necessary in keeping the community safe, ensuring inappropriate projects will be removed immediately, limiting their impact. While there is occasional abuse of the future to remove legitimate projects, the potential for inappropriate projects to remain up without being readily removed if a moderator is not online at the moment is far greater.[23]
Dislike Button or Project Rating System
Newer Scratchers might get discouraged by low ratings, and disliking a project does not say what the user did not like about it, or could have been done better. A core component of Scratch and remixing culture is constructive criticism; for example, if a game is "bad" because it is too easy, anyone may remix it and make a harder version.[24][25]
Ability to see who viewed your project
There is a high potential for drama if other users can see that someone viewed a project, and did not love/favorite it.[26]
Studios
Remove studio activity messages
Many users are annoyed by studio messages, but many users find them helpful, so disabling them completely across the entire site does not make sense.[27] However, there is an open suggestion for individual users being able to opt out of receiving them.
"Invite all followers" button for studios
This could lead to a lot of unwanted traffic in inboxes by making it easy to generate hundreds or thousands of invites with the push f a single button. Following a user is not intended as a means of signing up for curator invitations.[28]
Revert the 2021 Studio Update
While many Scratchers hate the new design and features, the Scratch Team had good intentions and abandoning all of those changes would be a bad idea.[29][30]
Comments and text fields
Editing comments
This has the potential to lead to dishonest manipulation of comments. If editing comments is enabled, then moderators who are reviewing comments need to interpret replies not only in context of the current comment, but every previous revision as well, with multiple users' replies to a comment each potentially referencing a different version, and making moderating comments a much longer and more tedious task. Comments are not intended to be large boxes of text edited and refined over time; clarifying typos can be done via follow-up comments. [31]
Notification for being mentioned in comments
This would be easy to abuse to quickly and repeatedly spam users with unwanted notifications.[32]
Live commenting or live streaming
Real-time commenting is much harder to moderate than static commenting. It would also be a large use of Scratch's server resources, with the only benefit being making the Scratch website more akin to a social network.[33][34]
Scratch Community
Private messaging
Private messaging would be useful for collaborations, but goes against the idea of the public sharing aspect of the Scratch community. In addition, a private messaging feature on the website would have serious potential to be used for inappropriate activity that the heavily-moderated Scratch community is meant to keep users safe from. Even if private messages could be reported to the Scratch Team for view, the risk of only user being able to see them and not reporting it (or the user simply being persuaded not to report them) makes private messaging far too large of a liability and source of problems.[35]
A 13+ version of the site or age restricted content
The Scratch Community is intended to be a large space for users to create and share together. Splitting the community into "sub-communities" would run counter-intuitive to this. While users over 13 are welcome to participate in the Scratch community, .[36][37]
Allow Scratchers to moderate the website
Between 2011 and 2013, Scratchers were allowed to moderate the website. However, the Scratch Team closed this program as having a website moderated by minors creates legal issues. [38] Delegating moderation tasks to anyone outside of the Scratch Team creates organizational issues as well. [39]Any Scratcher who is 18+ and eligible to work in the United States may apply for the Community Moderator position via the Jobs page, if that position is currently hiring.
Disallow sharing political views
Anyone is allowed to express their political views on Scratch, as long as it is done in a respectful manner not used to attack others.[40]
Proposing own projects to be featured
If Scratchers could propose their own projects, there would be far too many projects proposed for the Scratch Team to be able to reasonably review them; many users might simply propose every project they make. Requiring someone other than the owner to propose a project has at least some form of oversight in that at least one other person believes the project should be featured.[41] However, users may ask others to propose their project to be featured, as long as it is done respectfully and not in a spam-like manner.
There is a risk of inappropriate projects appearing on that row. While there is theoretically a risk of inappropriate projects appearing anywhere on the site, rows of the front page should have some oversight-- either by the Scratch Team, the current curator, or the community as a whole.[42]
Featured Scratchers row
The front page is for showcasing projects, not users. The main purpose of the Scratch site is creating and sharing projects, and users would make Scratch too akin to a social network, without being an example of a creation and something users could make. [43] It is also unclear what being a featured user would mean, or how they would be chosen.
User Accounts
Changing usernames
If users could change their username (whether it was changed in the database or only changed the display name), cause confusion about who did what, and in old comments, who is referring to whom, both for moderators[44]and for the community as a whole. [45] However, the ability to have a nickname that always displays alongside the original username is not rejected, and currently has an open topic. The suggestion to change capitalization also has an open topic.
Remove the New Scratcher status
The New Scratcher rank is meant not only to stop spam/abuse, but also to disincentivize excessive use of alternate accounts and frequent moving of accounts[46].
A rank above Scratcher
A rank above Scratcher could cause division and conflict in the community.[47]
Show when users are online
The Scratch Team has decided that that would not benefit Scratch as an educational platform.[48]
Show when users are banned
It would cause unwanted attention to a user[49]. An option to make your ban public is not rejected, and has its own topic here.
Recycle Usernames
Even if a user is inactive, they may still want their account. If someone could use their name, all of their work would be deleted and they could be impersonated. The Scratch Team also wants to keep the account to refer back to.[50]
Ability to block users
Blocking users would just cover up the problem, not solve it.[51]
Money Blocks
ask for [$ v] [5] and wait::operators when [$ v] [5] paid::operators hat
This block would allow users to make certain Scratch project features cost money to access. Scratch, however, is an educational site, and is not intended as a way for users to make money.[52] The feature can also be defeated by editing a project and many users might not know a lot on spending money.
Official badges or achievements
Having a reward for getting loves or favorites, or other "achievements" or actions in games is rejected. That would make a community that judges by that arbitrary score or other rewards you got, and for in-game achievements, who would stop someone from making a project just to give them/others rewards?[53][54][55]
Notification when someone unfollows/unloves/unfavoritess a project/a user
This could cause some drama between the user and the unfollower, and the Scratch Team believes that users should be allowed to unfollow without feeling guilty.[56]
Change or remove the list of locations
Scratch's list is based on an international standard. It will not be added or removed.[57][58]
Discussion Forums
Bring back the discuss tab
The Scratch forums are easy to misuse, and New Scratchers might not know how to use the forums properly, and the button would cause many New Scratchers to use the forums.[citation needed] The forums also allow for more spam and misuse, especially for new forum users who are not aware of how the forums work.[59]
Notifications for being quoted in the forums
Due to the way the forums work, this would not be possible. There would also be the issue of spam. To stay up to date on a topic, follow it.[60]
Off topic section in the forums
There used to be the Miscellaneous forum, but it got shut down due to spam.[61]
A list of accepted suggestions
Every feature on Scratch would have been suggested at one point, whether by the Scratch Team or the community; the list would be a list of every feature in Scratch.
Allow users to upload files to Scratch
The issue is that it would cause a need for more moderation work and storage space.[62]
Polls on the forums
The Scratch Team is more interested in constructed replies and less in votes to suggestions.[63]
Tutorials section on the Forums
They are rejected because the forums are for discussion. Use a project or Wiki article instead.[64]
Report button for signatures
Users can press the Report button on a post with an inappropriate signature, explaining that the signature is inappropriate. There is no need to make a new button to report signatures.
Reallow April Fools forum posts
These were disallowed in 2024 onwards, due to them being too difficult to moderate and it causing lag to the Scratch Website. In previous years, they had been limited to the Suggestions forum and the temporary April Fools Day - Suggest-Show-Question-Bugs-Help-Glitch-Tell-Etc forum.
Forums Restriction
Removing 60/120 Second rule, New Scratcher status, etc.
While some Scratchers might perceive them as annoying, they are extremely effective shields against spam.[65]
Show exact post count
This would lead to increased competition of higher post count[66]; past 1000 posts, a user although a user's own count can be seen here.
Remove restricted image hosts or personal whitelisting
The Scratch Team does not want to have to spend time moderating tons of image sites. The Scratch Team only allows image hosts with certain rules.[67]
See Also
External Links
References
- ↑ Paddle2See. (18/12/2014). "but as we thought about it more, it became clear that it didn't really fit in with the idea of messages" post:634620
- ↑ Paddle2See. (28/6/2016). "When the stop sign is clicked, the project should stop - that's what people expect to happen." post:2070854
- ↑ Paddle2See. (24/6/2019). "Because of the fairly simple workaround - and the lack of definition of exactly how such a block would be used, I believe this suggestion is rejected at this time" post:3603084
- ↑ Paddle2See. (14/8/2019). "Yeah - interesting idea - but I can see where we might get a lot of problematic projects with these. Sorry, no. " post:3669210
- ↑ Paddle2See. (30/4/2019). "Cloud variables have proven to be expensive to maintain and subject to abuse. Cloud lists magnify these issues even more." post:3528653
- ↑ Paddle2See. (27/8/2019). "No, sorry - seems overly complicated for a first programming language." post:3684338
- ↑ Paddle2See. (11/4/2014). "Scratch is likely to stay 2D for quite a while." post:272115
- ↑ Paddle2See. (25/3/2020). "This particular suggestion would be helpful in improving a few types of projects - but wouldn't change very much the kinds of projects that could be made with Scratch" post:3889314
- ↑ Paddle2See. (2/7/2020). "The potential for confusion outweighs the anticipated benefits" post:4186455
- ↑ Paddle2See. (May 9 2020). "Actually, it wasn't removed because it had an easy workaround. It was removed because many beginning Scratchers found it overly confusing." post:4034761
- ↑ Paddle2See. (May 2, 2016). "it isn't something we can support right now, because of the moderation and technical issues" post:1958869
- ↑ Paddle2See. (March 14, 2019). "it's not a feature that would benefit beginning programmers" post:3471767
- ↑ Paddle2See. (Jan 21 2019). "this would require that we maintain twice the amount of code for the user interface portions of Scratch. I don't think that is something we can afford, given the resources we have. It would also make Scratch more complicated (more options)." post:3409849
- ↑ Paddle2See. (Nov. 5 2018). "Scratch is designed to be an educational language, with the “source code” always accessible for viewing and tinkering (remixing). Locking the code up in an EXE format runs counter to those goals." post:3303002
- ↑ Harakou. (July 12, 2014). "The clone limit we've added is a practical one to prevent projects from becoming unplayable. Otherwise, you could accidentally get sprites making infinite copies of themselves and such." post:375856
- ↑ Paddle2See. (May 4, 2020). "While it would be very cool if Scratch ran on the Switch, we don't have the resources to make that happen on our own." post:3983340
- ↑ Paddle2See. (June 5 2020). "Sorry - this feature was in the 2.0 Beta, but it immediately caused a bunch of moderation issues and was removed. I don't see it coming back at this time." post:4094599
- ↑ cheddargirl. (Aug. 6, 2024). "AI for image generation is currently a rejected suggestion due to ethical concerns." post:8078494
- ↑ dietbacon. (July 11, 2019). "Going forward, we will no longer allow projects that include cloud-based chat functionality on Scratch" post:3622655
- ↑ cheddargirl. (July 19,2015). "A lot of users think that additional permission is required to remix a project and that they can put up things in notes such as “no remixing/”no recolors"/etc. rules. The reality is that this that this practice goes against the remix policy" post:1222338
- ↑ Za-Chary. (June 2,2021). "By sharing your creations on Scratch, under this license, you are automatically giving permission to everyone to use your creations" post:5302901
- ↑ Paddle2See. (Unknown Date(original topic deleted) but before march 18,2017). "Scratch is about more than just programming" post:4541993post:2509816
- ↑ Za-Chary. (Nov.13 2020). "The automatic project removal and temporary account block system that is currently in place is extremely useful to ensure that the community stays safe. Without this system, users who make inappropriate projects would be able to keep making them, possibly without immediate consequence if a moderator is not online at the time." post:4600199
- ↑ Paddle2See. (May 2,2016). "Sorry - we aren't going to do this as it might be discouraging for beginning Scratchers." post:1958521
- ↑ Harakou. (July 29,2017). "Yeah, we're not interested in adding a rating system for projects." post:2749716
- ↑ Paddle2See. (Oct 1,2018). "it could lead to a lot of traffic on the inbox of some Scratchers - and it could lead to drama about who is or isn't viewing projects" post:3268569
- ↑ Paddle2See. (May 16, 2017). "No - I don't see the point of removing it entirely." post:2621530
- ↑ Paddle2See. (July 27, 2018). "We actually had this feature in the early days of Scratch 2. Unfortunately, we found that it led to a lot of unwanted traffic in inboxes." post:3190328
- ↑ cheddargirl. (July 8,2021). "We won't be changing it back since the way studios were operating was pretty much starting to get unsustainable for the website." post:5416219
- ↑ cheddargirl. (july 20,2021). "Maybe sometime we can bring this suggestion up again when website conditions are better to support a higher limit. But definitely not today, and not for a good very long while." post:5452511
- ↑ Harakou. (April 23,2016). "Comments simply aren't designed as longer thoughts that might need to be edited over time" post:1939992
- ↑ Lightnin. (Dec 17,2012). "We thought about making it also send them a notification / message, but decided it would be too easily abused for spamming." post:4221
- ↑ Paddle2See. (July 27, 2020). "There are two major concerns we have. First, would be the potential negative effects on the servers. It sounds like the suggestion would be asking more from them and increasing the load on them - something we cannot afford to do at this time. Second, while Scratch has a social media aspect, we want the primary focus to continue to be making and sharing Scratch projects." post:4264317
- ↑ Za-Chary. (Sept 24, 2020). "Sorry — livestreams on other websites have been proven to be troublesome" post:4445027
- ↑ andresmh. (Dec. 20, 2008). "No. Because keeping things open and public allow for things to be transparent. Inappropriate behavior is easily spotted and the benefits of having private communication do not outweigh its disadvantages." ar-post:83414
- ↑ Paddle2See. (Jan. 28 2014). " At this moment, we aren't convinced that splitting the community would be a good thing - and we don't have the resources to build another site (or portion of a site) if we did." post:242372
- ↑ Paddle2See. (March 11 2019). "Age verification is a tricky thing - people may not be truthful when they create their account. Also, in a group setting, you may have people of different ages sharing a computer (such as in a school classroom)." post:3468115
- ↑ Paddle2See. (Unknown). "there was some very ugly stuff showing up in the queue due to some trolling. We decided, for that reason and others, that we would stick to adults for forum moderation." post:3513044
- ↑ Paddle2See. (2021-09-24). "It's confusing enough with just the few moderators we have here. Imagine if we had many more! " post:5640772
- ↑ Paddle2See. (July 1,2017). "Please be aware that, while we value your constructive feedback, we are rejecting all suggestions to formalize what the Scratch Team can and cannot promote / construct / feature / etc. We have run the site successfully for 10 years with our current process and are satisfied with it. We recognize that no approach can appeal to everybody so we will continue to use our best judgement." post:2706108
- ↑ Paddle2See. (May 4,2020). "we made the rule that Scratchers could only propose projects made by other Scratchers for two reasons" post:3983330
- ↑ Paddle2See. (July 16,2020). "Yeah - we found that many new projects were quite rough and the creators of those projects (often people new to Scratch) would get mean comments. And some projects were not appropriate for all Scratchers. So I don't think we'll be trying that again." post:4229735
- ↑ Paddle2See. (Nov. 15, 2021). "we've thought about that in the past and decided to keep Scratch focused on projects, not Scratchers." post:5784390
- ↑ Paddle2See. (July 2, 2014). "Unfortunately, this would create too much confusion in the community - and our system isn't set up to handle it." post:367229
- ↑ Harakou. (Feb 18, 2017). "As described above, we're concerned with the confusion it could cause for other users, not just moderation. We don't intend on making namechanges possible, even if it's only to a display name." post:2456140
- ↑ Paddle2See. (2015-05-05). "In addition to being a barrier to spammers, there's one other reason for the New Scratcher restrictions that hasn't really been touched on - and that's to make it more difficult for people to spawn new accounts." post:993968
- ↑ Paddle2See. (March 24,2016). "more ranks would just divide the community unnecessarily." post:1870800
- ↑ Paddle2See. (Nov. 28,2018). "We (the Scratch Team) have talked it over a few times - but have never managed to convince ourselves that it is a feature that would benefit Scratch as a creative platform." post:3326952
- ↑ Harakou. (Nov. 27, 2015). "The status of a user's account is between us (the Scratch Team) and them." post:1631442
- ↑ LastContinue and Paddle2See. (Sept 16,2019). "The API is a way for the public to access the database, it would likely require expensive database purge operations to remove this data, and also modification to account deletion. ... We also think it would be confusing to the community" post:3704074
- ↑ Paddle2See. (Aug. 1,2016). "It tends to bury problems rather than bringing them into the light where they can be fixed" post:2128208
- ↑ Paddle2See. (20/8/2015). "Scratch is an educational site for learning and creating - not for making money" post:1333242
- ↑ Paddle2See. (March 26,2015). "However, badges / coins have been considered in the past ... but ultimately rejected as we don't feel it would be a good fit for our community. " post:884708
- ↑ jvvg. (May 10,2013). "This would harm Scratch's purpose, and people would determine their social worth on the site based on achievements in games, and some users would act as if they are more important than others merely because they have more game badges." topic:4789
- ↑ Paddle2See. (Sept. 29, 2014). "Thanks for the suggestion - but it doesn't really fit in with our philosophy for the site at this time." post:456374
- ↑ Paddle2See. (Aug. 12 2019). "We feel that it would potentially create a lot of drama with some Scratchers that are focused too much on the number of followers they have. Scratchers should always feel free to follow or unfollow Scratchers as their interests change, without feeling guilty about it. Remember that Scratch is for learning, sharing, and having fun - it's not about the number of followers."
- ↑ Paddle2See. (March 5, 2021). "They rejected it on the basis that they go by an international standard that determines these kinds of things" post:4965047
- ↑ Paddle2See. (Nov 28,2018). "it's still pretty cool to see all the different places that Scratch is used. We decided to keep it for now." post:3326935
- ↑ dietbacon. (July 5, 2017). "We have also removed the “Discuss” button from the navigation menu. We made this decision based on usage (how often it was clicked) and to give emphasis to the other menu options like “Create” and “Explore.”...These changes were made to help highlight project creation and get new users started on becoming full fledged Scratchers! " post:2711595
- ↑ Za-Chary. (June 6,2019). "Sorry, this has been rejected. As it has been mentioned early on in the thread, we cannot add this suggestion simply because of the way that the forums work. The large potential for spam could also be more trouble than this suggestion is worth." post:3579079
- ↑ Paddle2See. (Nov. 8,2016). "Sorry - we're still not interested. " post:2282480
- ↑ Paddle2See. (Nov. 2 2020). "We have to pay for storage - so we really don't want to be paying for storage beyond what we need to for projects and other Scratch stuff. It would also require more moderation work - an area that is already pretty stressed with the Covid-19 traffic." post:4564638
- ↑ Za-Chary. (April 8, 2021). "Unfortunately, polls are not something we believe would fit in the forums. We are more interested in seeing Scratchers create constructive and helpful posts, rather than believing that simply saying “support”" post:5109469
- ↑ Paddle2See. (March 5,2018). "However, my feeling is that guides and tutorials are better handled by the Wiki, which has a good organizational structure, working search features, and quality standards" post:3014753
- ↑ Paddle2See. (June 22, 2015). "Sorry - we still feel that it's a necessary security feature to throttle the post rate. Some commercial spammers and trolls have made it to full Scratcher status in the past." post:1134018
- ↑ Paddle2See. (Sept 17, 2018). "The reason that post counts were made “fuzzy” in the first place was to de-emphasize the importance attached to the post count - to prevent spamming for post count."
- ↑ Lightnin. (Dec. 18, 2012). "We can't take the time to add everyone who has a personal website to the whitelist. Sorry - you'll have to use one of the approved hosts." post:4569
