GvYoutube wrote:

(#3160)

sly_wolf_901 wrote:

is this what people are using to get round bans? because accounts don't get deleted, only banned.

No, this is a python API wrapper. If you're banned you cannot use the API with your login token

Some api endpoints are available for banned users. One example would be the cloud variable websockets.

MineTurte wrote:

MeLovesScratch123 wrote:

help, on my storage.add_database(db1) it keeps saying "name ‘db1’ is not identified

storage.add_database(“db1”)

OHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

ok @mineturte your here your connect team member, is there a way to edit cloud vars without credentials? shall i have to make a connect_ account?

webreserch wrote:

ok @mineturte your here your connect team member, is there a way to edit cloud vars without credentials? shall i have to make a connect_ account?

No, you need credentials.

MineTurte wrote:

webreserch wrote:

ok @mineturte your here your connect team member, is there a way to edit cloud vars without credentials? shall i have to make a connect_ account?

No, you need credentials.

ok, thanks! that was the bug (the bug was before scratch cloud servers were down)

Current rate limits when adding projects to studios via the Scratch API

Hello everyone,

I'm developing Scratch Studio Adder, an open-source tool that automates adding a project to multiple studios. It makes 2 requests per studio (connect + add) spaced 200ms apart (5 req/s, half the documented 10/s limit), yet I'm still getting 429 errors.

My questions:

1. Are there additional rate limits beyond the documented 10 requests/second? Per-minute or per-studio perhaps?
   
2. Do write operations (adding projects) have stricter limits than read operations?
   
3. What spacing would be safe for adding a project to 200+ studios in one session?
   

Any practical insights would help me make this tool reliable for the community. Thanks!

MyDigitalGarden wrote:

Current rate limits when adding projects to studios via the Scratch API

Hello everyone,

I'm developing Scratch Studio Adder, an open-source tool that automates adding a project to multiple studios. It makes 2 requests per studio (connect + add) spaced 200ms apart (5 req/s, half the documented 10/s limit), yet I'm still getting 429 errors.

My questions:

1. Are there additional rate limits beyond the documented 10 requests/second? Per-minute or per-studio perhaps?
   
2. Do write operations (adding projects) have stricter limits than read operations?
   
3. What spacing would be safe for adding a project to 200+ studios in one session?
   

Any practical insights would help me make this tool reliable for the community. Thanks!

For the rate limits, that's interesting. I'm able to download about 200 projects per minute using multi-threaded requests. That's 1 for the thumbnail, 1 for some comments, like 5 for each individual stat of the project, 1 for the .sb3 of the project, and multiple for the assets of the project. This happens as fast as possible (with small respect to the rate limit) and not once have I hit it. So either you made a ton of requests in a small period, maxing it out for a period; or requests to studios do indeed have higher and stricter rate limits. It might be both. Who knows. I'll probably do some testing and see what comes up. For now, try multi-threading (even though python is notoriously bad at it). It might not do anything but worth a shot. Also add a built-in limiter so that your program sleeps temporarily on a 429 error and retries after that delay (if you don't already have this).

MineTurte wrote:

MyDigitalGarden wrote:

Current rate limits when adding projects to studios via the Scratch API

Hello everyone,

I'm developing Scratch Studio Adder, an open-source tool that automates adding a project to multiple studios. It makes 2 requests per studio (connect + add) spaced 200ms apart (5 req/s, half the documented 10/s limit), yet I'm still getting 429 errors.

My questions:

1. Are there additional rate limits beyond the documented 10 requests/second? Per-minute or per-studio perhaps?
   
2. Do write operations (adding projects) have stricter limits than read operations?
   
3. What spacing would be safe for adding a project to 200+ studios in one session?
   

Any practical insights would help me make this tool reliable for the community. Thanks!

For the rate limits, that's interesting. I'm able to download about 200 projects per minute using multi-threaded requests. That's 1 for the thumbnail, 1 for some comments, like 5 for each individual stat of the project, 1 for the .sb3 of the project, and multiple for the assets of the project. This happens as fast as possible (with small respect to the rate limit) and not once have I hit it. So either you made a ton of requests in a small period, maxing it out for a period; or requests to studios do indeed have higher and stricter rate limits. It might be both. Who knows. I'll probably do some testing and see what comes up. For now, try multi-threading (even though python is notoriously bad at it). It might not do anything but worth a shot. Also add a built-in limiter so that your program sleeps temporarily on a 429 error and retries after that delay (if you don't already have this).

Thanks for your reply! Multithreading? I thought that would make things worse. I mean, it's more requests per second, and I try to keep it to a maximum of 5. My program cancels everything and exits immediately when I encounter these kinds of errors, which are serious for me, but beyond what it means for my account, my main goal is to be as kind and respectful as possible to the Scratch API.

UPDATE: I've updated the wait times. Here’s what I found:
The total execution time jumped from 3–5 minutes to nearly 30 minutes and the error occurred EXACTLY IN STUDY NUMBER 301. I wish I had saved my report to show it as evidence; in fact, it had happened before and I hadn’t noticed it. Maybe it’s just a coincidence, but personally, I’ll try to stay below that limit at all costs.
It’s worth noting that this isn’t the daily use I intend for it, but rather a test to fine-tune the script and ensure that both its users and the API are secure.

When I get my PC back I'm going to use this

It looks like Scratch is shadowbanning accounts from cloud variables. Many people using scratchattach are affected. However, some people who never used scratchattach before are affected as well, so this could also be a technical issue.

TimMcCool wrote:

it looks like scratchattach users are being shadowbanned from using cloud variables

what does shadowbanned mean?

webreserch wrote:

TimMcCool wrote:

…

what does shadowbanned mean?

blocking your whole account from setting cloud variables without telling you. see https://scratch.mit.edu/discuss/topic/838318/?page=43

we don't know if this is actually happening on purpose, there also could be a technical issue behind this.

TimMcCool wrote:

It looks like Scratch is shadowbanning accounts from cloud variables.

This might be related to the “hackers” (people spamming cloud variables using scratchattach to break games) that were breaking griffpatch's games. Griffpatch recently said @codubee fixed it, so this might be the fix in action.

TimMcCool wrote:

webreserch wrote:

TimMcCool wrote:

…

what does shadowbanned mean?

blocking your whole account from setting cloud variables without telling you. see https://scratch.mit.edu/discuss/topic/838318/?page=43

we don't know if this is actually happening on purpose, there also could be a technical issue behind this.

ah, thank you I have been developing a workaround.. or we could just migrate to turbowarp or a cloud server host independent from scratches cloud host while using a third party application like scratch auth to avoid impersonation the workaround (for scratch not turbowarp) has been in the work for a bit now, so due to its large scale nature may take a few years due to it should run on other software I created as a sort of scratch attach “layer”

webreserch wrote:

TimMcCool wrote:

webreserch wrote:

TimMcCool wrote:

…

what does shadowbanned mean?

blocking your whole account from setting cloud variables without telling you. see https://scratch.mit.edu/discuss/topic/838318/?page=43

we don't know if this is actually happening on purpose, there also could be a technical issue behind this.

ah, thank you I have been developing a workaround.. or we could just migrate to turbowarp or a cloud server host independent from scratches cloud host while using a third party application like scratch auth to avoid impersonation the workaround (for scratch not turbowarp) has been in the work for a bit now, so due to its large scale nature may take a few years due to it should run on other software I created as a sort of scratch attach “layer”

though I could probably setup a secondary server for scratchattach in maybe a few days emphasis on probably

Does it work on chromebook?

when I look at python:: cat events
ask [Is it for chromebook?] to [python v]:: sensing

Pawsai18 wrote:

Does it work on chromebook?

It only works if your chromebook lets you download python, since you need python to use it.

webreserch wrote:

webreserch wrote:

TimMcCool wrote:

webreserch wrote:

TimMcCool wrote:

…

what does shadowbanned mean?

blocking your whole account from setting cloud variables without telling you. see https://scratch.mit.edu/discuss/topic/838318/?page=43

we don't know if this is actually happening on purpose, there also could be a technical issue behind this.

ah, thank you I have been developing a workaround.. or we could just migrate to turbowarp or a cloud server host independent from scratches cloud host while using a third party application like scratch auth to avoid impersonation the workaround (for scratch not turbowarp) has been in the work for a bit now, so due to its large scale nature may take a few years due to it should run on other software I created as a sort of scratch attach “layer”

though I could probably setup a secondary server for scratchattach in maybe a few days emphasis on probably

pretty sure i have been shadow banned, im able to see the cloudlogs however i cannot modify the vars

wvzack wrote:

webreserch wrote:

webreserch wrote:

TimMcCool wrote:

webreserch wrote:

TimMcCool wrote:

…

what does shadowbanned mean?

blocking your whole account from setting cloud variables without telling you. see https://scratch.mit.edu/discuss/topic/838318/?page=43

we don't know if this is actually happening on purpose, there also could be a technical issue behind this.

ah, thank you I have been developing a workaround.. or we could just migrate to turbowarp or a cloud server host independent from scratches cloud host while using a third party application like scratch auth to avoid impersonation the workaround (for scratch not turbowarp) has been in the work for a bit now, so due to its large scale nature may take a few years due to it should run on other software I created as a sort of scratch attach “layer”

though I could probably setup a secondary server for scratchattach in maybe a few days emphasis on probably

pretty sure i have been shadow banned, im able to see the cloudlogs however i cannot modify the vars

I may create it but i would like official allowing of it first