I just had an idea to see if some ATers would like to create a local cloud server that redirects traffic. It would run on the client in the form of a userscript redirecting traffic from Scratch's server the a local websocket server.

If this is against any terms of service, I wouldn't see why. It would be redirecting traffic instead of sending traffic.

This would be useful to test cloud projects (such as things that use the ScratchAPI cloud interface) locally instead of on the Scratch servers.

If something like this was made public so anybody could access unofficial cloud servers would that be breaking any rules?

bybb wrote:

I just had an idea to see if some ATers would like to create a local cloud server that redirects traffic. It would run on the client in the form of a userscript redirecting traffic from Scratch's server the a local websocket server.

If this is against any terms of service, I wouldn't see why. It would be redirecting traffic instead of sending traffic.

This would be useful to test cloud projects (such as things that use the ScratchAPI cloud interface) locally instead of on the Scratch servers.

If something like this was made public so anybody could access unofficial cloud servers would that be breaking any rules?

I don't believe it would be breaking any rules. I remember someone making this but I forgot the link

Yes

I think this is what you're looking for: https://scratch.mit.edu/discuss/topic/151802/

Znapi wrote:

I think this is what you're looking for: https://scratch.mit.edu/discuss/topic/151802/

thank you

herohamp wrote:

Znapi wrote:

I think this is what you're looking for: https://scratch.mit.edu/discuss/topic/151802/

thank you

Just as another reminder, that code is only intended for local testing - If you expose it to the internet, there are SQL injection vulns that could be exploited.

Also, the code may or may not suck.

I will look into writing my own one in nodeJS

That would be cool