Getting straight to the point here, a few months ago it was stated that API changes will be made that will make it so TurboWarp can no longer view unshared projects. I believe the changes have finally been made.

This has got to be one of the worst changes ever done to the website. Now it’s very difficult to send test builds to friends so they can playtest it, or even playtest it yourself in the browser. The entire point of the change was to “stop projects from leaking,” but the change ends up becoming extremely counter-productive since you now have to SHARE the project for people to test it, and you may not want the average viewer seeing the project yet.

The “just download the project and upload it to TurboWarp” or “send the .sb3 file instead of a TurboWarp link to your friends” workarounds aren’t entirely full-proof either. I’m pretty sure after downloading a project there’s a chance for the cloud variables to completely break, and also it’s just extremely tedious.

I hope other people feel the same way about the changes as I do. SO MANY people previously shared TurboWarp links in order for others to test their games. In fact, I only found out about the API change because I was about to send a TurboWarp link of a WIP game to a friend! I really hope Scratch Team considers reverting the API changes.

support because of the reasons stated in the op

This isn't just about the occasional Scratch game that one may not want to release early. Every single project on Scratch was vulnerable and public for everyone to see, including deleted ones. I'm pretty sure you or really anyone would like to have every project they ever made shared, ones that may have personal information or other things that the user definitely does not want to share.

Major support. My idea to rectify this, make a way to delete projects permanently, but keep unshared projects visible in turbo warp. It's secure because one would still need the link to the project to access it.

the reason they updated it s to prevent mean comments and to protect unshared projects. reverting it would make it harder to report inappropriate content.

IndexErrorException wrote:

Major support. My idea to rectify this, make a way to delete projects permanently, but keep unshared projects visible in turbo warp. It's secure because one would still need the link to the project to access it.

It's not secure because Scratch doesn't use random strings for links like Youtube. You can just iterate through every number from say, 729,000,000 to 730,000,000, and you'll know every single link would be a project.

Uhh, no? The reason it was removed was because of inappropriate projects were being shared, I actually had a run-in on this. This falls under unlisted projects and Paddle made a post on this.

Paddle2See wrote:

Sorry - I'm going to have to reject this idea. We depend heavily on the community to view projects and let us know when something in the project goes against the Community Guidelines. Restricting the viewing audience to a very small number decreases the likelihood that we would get a report if the project were not okay. It would also make it easier to do some forms of private communication, since we don't have the resources to view every project.

This would lead to private messaging, the whole foundation of the reason to add this. The workarounds are fine, and if you don't want the average viewer to see it, but still let your followers see it it's pretty hard. You have to put it on your profile. What I see in this post to add this is

Now it’s very difficult to send test builds to friends so they can playtest it

you may not want the average viewer seeing the project yet.

I was about to send a TurboWarp link of a WIP game to a friend!

All of these highlight private messaging, which is rejected. It's not that hard. Share your projects, and let the average viewer see it. It won't hurt the project hype if you release it at specific intervals, and copies.

Unfortunately, there was enough abuse of the ability to see unshared content that I do not see any interest from the Scratch Team in reverting the change.