Here's the cloud data for project #0 and project #undefined:

https://cloud.lindsey.studio/project/0/logs

https://cloud.lindsey.studio/project/undefined/logs

You can see they both have cloud data, which is really weird
Direct from the scratch servers:
https://clouddata.scratch.mit.edu/logs?projectid=0&offset=0&limit=100000

https://clouddata.scratch.mit.edu/logs?projectid=undefined&offset=0&limit=100000

Does anyone have any idea why?

You can probably just set the cloud data on those projects with a Python library.

Edit: yup (I used my alt account):

Anybody can set cloud variables to any project; whether private or not. This should be fixed

anybody can do that, with python

9gr wrote:

Anybody can set cloud variables to any project; whether private or not. This should be fixed

scratch team being scratch team hasn't fixed this even though its been more than a year that people have known about this bug

Chiroyce wrote:

9gr wrote:

Anybody can set cloud variables to any project; whether private or not. This should be fixed

scratch team being scratch team hasn't fixed this even though its been more than a year that people have known about this bug

I thought you were the one who said that it would be really hard (even impossible) to fix the cloud variable “bug”?

NFlex23 wrote:

I thought you were the one saying that it would be really hard (even impossible) to fix the cloud variable “bug”?

Yeah, for the ST it is nearly impossible, since they cannot afford to have projects run on their server and be streamed to the user, so the only other way is to delete cloud vars entirely.

It's also weird that it doesn't check if the project exists, like project undefined

Funny how all the logs are from “well-known” Scratchers doing testing

NFlex23 wrote:

(#6)

Chiroyce wrote:

9gr wrote:

Anybody can set cloud variables to any project; whether private or not. This should be fixed

scratch team being scratch team hasn't fixed this even though its been more than a year that people have known about this bug

I thought you were the one who said that it would be really hard (even impossible) to fix the cloud variable “bug”?

That's a different bug, probably. That is cloud variables being externally settable, this is cloud variables being settable on unshared and even NONEXISTENT projects.

Chiroyce wrote:

9gr wrote:

Anybody can set cloud variables to any project; whether private or not. This should be fixed

scratch team being scratch team hasn't fixed this even though its been more than a year that people have known about this bug

Even with people abusing it for denial-of-service attacks, it still hasn't been fixed!!! Think they're busy improving https://filter.scratch.mit.edu/ or something…

this still exists btw