Hi from Japanese.

As you know, cloud data got restriction for a 128 character limit at the time. We Japanese say this happening “cloudshock”.
And then, cloud chat has been banned entirely. We also say it the 2nd cloudshock.

Since the cloud variables only had numbers from the beginning of the implementation, the cloud shock virtually restricted only the capacity of the cloud data. So it seems to be a main cause that lacking of the server space or processing power.

But on the 2nd cloudshock, cloud chat problem became famous, and then cloudshock has being explained like this: “cloudshock is the incident that cloud variables got restricted so as not to make chat rooms”.

Although there is no mention of the server space, does “Causing it to be unreasonable to support financially” intend that it costs too much for servers?

Are the server space issues involved in the cloud data restriction?
And are suggestions like “local cloud data for each scratcher” simply unfeasible for the server space issues??

Thank you.

My guess is the main issue isn't space (storage is cheap) but the computation power and network bandwidth required to handle live updates to all the cloud variables.

I think it was reduced to reduce traffic, I doubt an extra 128 characters would cost (a lot) more money. Also, cloud chats were banned because users could say anything they want, including inappropriate things.

the wiki says:

To avoid overloading the cloud data infrastructure, cloud data updates are limited to a certain number per second when a project is being run. One should always avoid attempting to update a cloud variable in a fast loop that does not wait between updates. Generally, one should carefully consider how often a cloud variable is updated and try to limit any updates to only times when it is needed, such as when the value actually changes, and to limit how often the variable is updated on the server.

“cloud data updates are limited to a certain number per second”; Setting this limit appropriately, it might be able to increase the total capacity of cloud data?
And cloud variable should be updated as fast as possible to synchronize each of projects, but such a “local cloud data for each scratcher” does not need to be interactive among players and also not need to be updated so fast. therefore, this does not seem to be impossible.

So the cloud chat should be regulated by community guidelines and not be done by limitation of cloud data capacity?

tabakenn wrote:

So the cloud chat problems should be regulated by community guidelines and not be done by limitation of cloud data capacity?

I think they limited cloud variable data about a year before (2018) they blocked cloud chat rooms (2019), so they probably have nothing to do with each other. As I have said, they banned cloud chats because users could send inappropriate content through them.