-
-
Notifications
You must be signed in to change notification settings - Fork 169
Unshared Projects
You've probably noticed that TurboWarp can load unshared projects, and you might be concerned about that.
To be clear: This is a problem with the Scratch API that's been around for years. It's not a bug in TurboWarp.
Even the official development version of Scratch GUI can view unshared projects: https://llk.github.io/scratch-gui/develop/#1
As TurboWarp uses the exact same project loading code as Scratch, it's also able to load unshared projects the same way.
If you want your projects to remain private, don't share the project ID (the numbers in the project URL) with anyone you don't trust. That means you shouldn't share links to your project or screenshots/videos of your project that include your browser's URL bar.
If the project ID has already been leaked and you don't want people to see the project, save a copy of the project (File > Save as a copy) and delete everything from the original project. Deleting a project through the My Stuff page (even emptying the trash) is not enough. You must manually clear everything from the project. Keep in mind that if the project ID is already public, it's possible that someone has already downloaded it to their computer.
This would be a good opportunity to download a backup of the project to your computer for safekeeping so that you don't have to learn the importance of backups the hard way.
Another alternative to keep your project secure would be to use the offline editor. We could recommended TurboWarp Desktop :)
It would be possible to make TurboWarp not load unshared projects, but it wouldn't fix the root cause and people would still view them just as easily as before by using the official Scratch GUI development build or any other tool.
Curious people have visited https://turbowarp.org/1 and found a strange project. That's just what the Scratch API returns when you ask for the project with ID 1. Some story applies to all the other low project IDs. We don't know why those projects are the way that they are.
This is normal if the project was shared very recently. Let me know on Scratch and I can fix it if it doesn't resolve itself within a few hours.