say [support]
if <not <[someone] = [Support]>> then
    
say [He lied] forever::looks
end

AonymousGuy wrote:

I think whoever made the project should automatically keep a back-up copy in case a malicious user decides to delete it. I don't know about transferred projects, though, because then it would more “give copy of:” then “transfer”.

dracae wrote:

I'm glad you brought this issue up in particular: “Would this power be too risky for abuse?”
This is a HUGE problem, and in my opinion, I feel like the positive outcomes of your suggestion do not outweigh the potential abuse.

Sorry, but no support.

LightBulb80 wrote:

No support, i thought this was rejected
Still no support

CGRises wrote:

AonymousGuy wrote:

I think whoever made the project should automatically keep a back-up copy in case a malicious user decides to delete it. I don't know about transferred projects, though, because then it would more “give copy of:” then “transfer”.

dracae wrote:

I'm glad you brought this issue up in particular: “Would this power be too risky for abuse?”
This is a HUGE problem, and in my opinion, I feel like the positive outcomes of your suggestion do not outweigh the potential abuse.

Sorry, but no support.

LightBulb80 wrote:

No support, i thought this was rejected
Still no support

/\/\/\
Don't forget PMing: the reason it was rejected by the stickies.

-Carbonate- wrote:

semi-support

I'm quite concerned about how the saving is going to work. If two people are working on the project at once, if Scratch still uses its methods of saving, then when one person saves, the other person would get their work overwritten. If it saves automatically all the time like Google Docs, it might get too laggy.

Blaze349 wrote:

Saves automatically

BoyKetchup wrote:

Don't know if someone's said this already, but it could work like google docs where multiple people can edit at the same time and view the changes live.