As of 10 Sept 2017, the cloud data features of Scratch were migrated to use a new infrastructure. The changes include the following:

Encrypted websocket as the communication channel
Projects that send data too quickly to the backend infrastructure will have their connection dropped temporarily

You may notice that when a project that uses cloud data is in the non-running state, there are reconnections to the backend infrastructure. This occurs because web browsers aggressively shutdown websockets that appear to be idle.

Please let us know how well it does or does not seem to work!

codubee wrote:

As of 10 Sept 2017, the cloud data features of Scratch were migrated to use a new infrastructure. The changes include the following:

Encrypted websocket as the communication channel
Projects that send data too quickly to the backend infrastructure will have their connection dropped temporarily

You may notice that when a project that uses cloud data is in the non-running state, there are reconnections to the backend infrastructure. This occurs because web browsers aggressively shutdown websockets that appear to be idle.

Please let us know how will it does or does not seem to work!

Great! Now I can finish working on that multiplayer from 9 months ago.

codubee wrote:

Projects that send data too quickly to the backend infrastructure will have their connection dropped temporarily

Is this per-session, or per-project?

If it's per-project, wouldn't it be susceptible to a form of DoS attack? i.e. one user sends a whole bunch of data at once, so all the other users get their connections dropped.

novice27b wrote:

codubee wrote:

Projects that send data too quickly to the backend infrastructure will have their connection dropped temporarily

Is this per-session, or per-project?

If it's per-project, wouldn't it be susceptible to a form of DoS attack? i.e. one user sends a whole bunch of data at once, so all the other users get their connections dropped.

The connection throttling is per-session not per-project and is specifically designed to prevent DoS.

Yay!

TheUltimatum wrote:

Yay!

Yay indeed my friend. Yay indeed.

Any chance of getting a real socket interface instead of a singular state value that anyone can edit at any time?

WooHooBoy wrote:

Any chance of getting a real socket interface instead of a singular state value that anyone can edit at any time?

No.

Someone just shared a weird cloud data bug with me. While renaming cloud variables, the cloud icon ☁ got included with the new names, effectively turning them into normal variables which no longer accessed cloud data and confusing the user. I diagnosed it after seeing the cloud data page and a variable with two clouds in the name. My suggestion, replacing all the cloud variables, corrected the original project which is now un-shared, but I saved a remix of the bugged project as well as a screenshot of the original project's bugged cloud data included as a Stage costume in my remix.

I'm not sure if this has anything to do with the update, but I've never heard of this rename error before, so I thought I share it here too. I'm not expecting any direct reply or resolution to this post. just a fyi. By the time I saw the bugged, original project, it only set new cloud variables once per second. I asked the user about setting speed but they were aware of the speed limitation and seemed to be taking it into account.