(Redirected from Censor Outage on 2022-04-12)
|This article has links to websites or programs not trusted by Scratch or hosted by Wikipedia. Remember to stay safe while using the internet, as we cannot guarantee the safety of other websites.|
On April 12, 2022, the filterbot temporarily stopped working. As a result, users could post any inappropriate comments without being muted, and accounts with prohibited usernames were created. Users could also comment large numbers, which is normally prevented by the phone number filter.
A number of Scratchers received inappropriate comments and spam on their profiles, primarily users who were active on the forums. Additionally, the censor for account creation was also not working, so a number of accounts with inappropriate usernames were created.
Many forum topics were created asking questions related to the outage.
Scratch Team Response
In order to limit the effects, the Scratch Team disabled comments on projects, profiles, and studios as well as the forums. The Scratch Team also released a statement via Twitter, stating that the commenting had been temporarily disabled due to "a technical issue". The Scratch Team officially announced that comments were re-enabled at 3:37pm Scratch Time, at which time the filter was working normally again. Additionally, Scratch Team member Paddle2See later confirmed that there were issues with the filtering system and that they were not the result of an attack.
On the Twitter post about the technical issues, the Scratch Team hid replies saying that the filterbot was broken. They also deleted some forum posts about the issue. This caused some users to criticize how the Scratch Team handled the situation. Paddle2See explained that the posts were deleted to prevent the issue from being exploited.
- kccuber. (12/04/2022). "the filterbot crashed? I'm not really sure what happened but people can now write blocked words without issues" post:6205310
- Super_Scratch_Bros20. (12/04/2022). "they also made accounts with inappropriate usernames, since the usernames weren’t censored" post:6206596
- Za-Chary. (24/5/2019). "The phone number sensor [sic] will only censor numbers that are 10 or 11 digits long (I just checked on my profile). As a result, not too many numbers are affected by the filter." post:3559108
- scratchykit5743. (12/04/2022). "They've been targeting [The Forum Helpers] members left and right." post:6205256
- discordusername. (12/04/2022). "Title: "temporarily disable new users joining", Contents: "i shouldn't be able to have this username, and people can make much worse"" topic:595997[dead link]
- wolfbomb. (12/04/2022). "I've noticed that studio, project, and profile comments are turned off across scratch. Why? Did something happen?" topic:596033
- Time gap of 24 minutes between post:6205919 (3:16pm Scratch Time) and the next ID post:6205920 (3:40 Scratch Time)
- @scratch. (12/4/2022). "Commenting is temporarily disabled on http://scratch.mit.edu due to a technical issue." https://twitter.com/scratch/status/1513957027000709127
- @scratch. (12/4/2022). "Comments are back online!" https://twitter.com/scratch/status/1513964550827126784
- Paddle2See. (12/4/2022). "There were some issues with the filtering system but they weren't related to any kind of DOS." post:6206238
- Jeffalo. (13/4/2022). "the scratch team hid replies to their tweet about disabling comments." post:6208250
- HailStateDawgs. (13/4/2022). "Scratch has been dustbinning posts that discuss the comment shutdown yesterday, why is that?" topic:596303
- Scratchfangs. (13/4/2022). "How they are addressing the situation is disappointing. There is so much confusion going on, and more stress is getting pushed on the Scratch Team by trying to hide everyone from saying what happened." post:6208273
- Paddle2See. (13/4/2022). "As for why topics were removed - posting a security issue on a public forum is not a good idea as it encourages others to take advantage of it. Please use Contact Us or another private channel to let the Scratch Team know in the future." post:6208355