Replies: 12 comments
|
Agreed.
Yes, but I think that you should at least tell users that they are most likely violating the ToS by using ScratchAttach. |
|
Yes, I agree, they should be warned of the risk of getting banned by accessing the API externally (the exact reason I got banned). I may start a PR on this |
Out of curiosity, were you performing social interactions with the API or just looking at stuff? |
|
I was using scratchattach to work with cloud variables. Repo here |
I see, that makes sense. |
|
Maybe there should be a warning in the README. Possibly also a warning (that can be disabled) when you import the library or login to any session. |
|
Personally, I think they'll only use the TOS against you if you're using scripts that are doing malicious things. Services like ScratchAuth and those applications posted in the Advanced Topics haven't been shut down. Search engines still crawl the website. |
|
And yet I got banned for running a script that changes cloud vars... |
True, but it's better to alert people explicitly because they could change that any day without notice. |
|
I suppose you're right.
Not to disregard what you're saying, but it could be for a different reason. |
|
I might want to to add that the Scratch Foundation has official documentation on the Scratch API https://github.com/scratchfoundation/scratch-rest-api/wiki |
Uh oh!
There was an error while loading. Please reload this page.
To quote Section 11.13 of the Scratch Terms of Service:
Wouldn't this imply that most, if not all, usage of ScratchAttach violates the ToS, by virtue of programmatically-extracting data from Scratch?
All reactions