A couple of thoughts about the project token stuff:
who in the world thinks it’s a good idea to require a token for shared, public scratch projects?!? it’s just unnecessary work!
what about project embedding? what will happen to that? I doubt the scratch team wants to remove embedding since it promotes coding and sharing your projects
What if you’re not logged in and want to use a scratch project? Will you have to be logged in or else not be able to load any projects?
The big fear I have is this will turn into something like when the studios were transferred, a massive public outrage aimed at the scratch team. We’re talking 9 pages of forum topics just complaining about the studios. This is even worse than the studios though because it’s not just a design change, it actually removes functionality of being able to view and edit projects on turbowarp, which is much faster in some cases than normal scratch. So I fear people are going to complain A LOT. They are going to be outraged.
comments
2 and 3 will still work. For shared projects, the API with the token would become public.
luckily the changes have been temporarily put on hold due to some bugs it created
Scratch was supposed to be an open-source platform where people can learn to code and share their work. But, bit by bit the Scratch Team is ruining it, by slowly making everything closed-source. First the new API, then studios, and now they are restricting access to all projects all together. It’s only going to get worse…
The studios are open source I think (llk/scratch-www) but I can see what you mean. It’s really sad
Yeah, it's ok for unshared projects but doing it for shared projects is crossing a line
Honestly, I should look into whether or not this even agrees with the way Scratch projects are licensed.
I already looked and there’s nothing really in the terms of service about it