Project Editor:
v238:
* rewordings of status and error messages
* new dialog box on save failure with options for re-try to local save
* importing MP3 files now shows progress
* imported assets are uploaded *before* they appear in the project
* more progress dialogs so the user knows what's going on
* SWF calls a JS function to report the number of sprites and scripts when the project has loaded

Website:
* Minor refactoring and bugfix for project save code
* “Hot” backup of projects, assets, thumbnails, user avatars to Amazon S3
* Update to content for logged-out homepage (needs some style tweaks)
* Turn language support back on so that translators can test (should use browser lang setting and default to english)
* change cache on explore page to 1 hour

Wow, nice job!

I like the new logged-out homepage!

Nice! I always like the updates

Nice!

Yay! I can upload music now to the editor!

That's awesome! Now, can we at least get an update on how the cloud variables are doing?

comp500 wrote:

Yay! I can upload music now to the editor!

Great!! Glad to hear it's working better for you now!

cobraguy wrote:

That's awesome! Now, can we at least get an update on how the cloud variables are doing?

Slowly but surely - we have a strategy that we want to try during the beta, but we need to resolve a lot of other issues before we have time to implement it. The phishing thing is another issue we still have to work out… not totally sure how to prevent people from phishing passwords with cloud variables yet. But we'll get it sorted!

Lightnin wrote:

Slowly but surely - we have a strategy that we want to try during the beta, but we need to resolve a lot of other issues before we have time to implement it. The phishing thing is another issue we still have to work out… not totally sure how to prevent people from phishing passwords with cloud variables yet. But we'll get it sorted!

Put a warning before any project with cloud vars? It is indeed a big problem

roijac wrote:

Lightnin wrote:

Slowly but surely - we have a strategy that we want to try during the beta, but we need to resolve a lot of other issues before we have time to implement it. The phishing thing is another issue we still have to work out… not totally sure how to prevent people from phishing passwords with cloud variables yet. But we'll get it sorted!

Put a warning before any project with cloud vars? It is indeed a big problem

+1 I think that that would be a good idea.

roijac wrote:

Lightnin wrote:

Slowly but surely - we have a strategy that we want to try during the beta, but we need to resolve a lot of other issues before we have time to implement it. The phishing thing is another issue we still have to work out… not totally sure how to prevent people from phishing passwords with cloud variables yet. But we'll get it sorted!

Put a warning before any project with cloud vars? It is indeed a big problem

People don't want Scratch to be safe-except-where-marked-by-warnings—they want Scratch to be a safe and friendly community everywhere.

cobraguy wrote:

That's awesome! Now, can we at least get an update on how the cloud variables are doing?

Lightnin wrote:

Slowly but surely - we have a strategy that we want to try during the beta, but we need to resolve a lot of other issues before we have time to implement it. The phishing thing is another issue we still have to work out… not totally sure how to prevent people from phishing passwords with cloud variables yet. But we'll get it sorted!

Huh. I think people are educated enough not to put in real passwords. I think the system that could work is that if you type in your password, it will change it to before it gets to put it in a cloud list/variable.

Please hurry with these CVs. I really want to be able to make my chat client, and an April release date for it is looking unrealistic. So… Please work as quickly as you can.

tlangster wrote:

Huh. I think people are educated enough not to put in real passwords. I think the system that could work is that if you type in your password, it will change it to [PASSWORD] before it gets to put it in a cloud list/variable.

Not everyone. That's how phishing works.

Please hurry with these CVs. I really want to be able to make my chat client, and an April release date for it is looking unrealistic. So… Please work as quickly as you can.

Chat clients are strongly discouraged because they make moderation very difficult. The Scratch Team has a ton of work to do, and I don't think asking them to hurry up doing something they're already doing as fast as they can, just so you can make something that makes their work harder and Scratch a less safe community, is going to have a positive effect.

Lightnin wrote:

Slowly but surely - we have a strategy that we want to try during the beta, but we need to resolve a lot of other issues before we have time to implement it. The phishing thing is another issue we still have to work out… not totally sure how to prevent people from phishing passwords with cloud variables yet. But we'll get it sorted!

Alright, thanks. That's all I wanted to to know. I'm happy now!

I still think the solution to all cloud var issues is the report button.

bobbysq wrote:

I still think the solution to all cloud var issues is the report button.

But, what gets reported? The project? The project creator? The person who posts offensive content?

If it's the content poster, how to specify which content is offensive?

how about hitting the report button takes a screenshot of the project?
this way whatever they see that is offensive will likely be captured

BoltBait wrote:

bobbysq wrote:

I still think the solution to all cloud var issues is the report button.

But, what gets reported? The project? The project creator? The person who posts offensive content?

If it's the content poster, how to specify which content is offensive?

The project for being phishing/chatroom.

Lightnin wrote:

Project Editor:
v238:
* rewordings of status and error messages
* new dialog box on save failure with options for re-try to local save
* importing MP3 files now shows progress
* imported assets are uploaded *before* they appear in the project
* more progress dialogs so the user knows what's going on
* SWF calls a JS function to report the number of sprites and scripts when the project has loaded

Website:
* Minor refactoring and bugfix for project save code
* “Hot” backup of projects, assets, thumbnails, user avatars to Amazon S3
* Update to content for logged-out homepage (needs some style tweaks)
* Turn language support back on so that translators can test (should use browser lang setting and default to english)
* change cache on explore page to 1 hour

Umm… I am going to use scratch 2.0 to make a game for the STEMchallenge… entries are due april 24….. and the winners are released some where near mid may…..so could you not stop the beta until after june or july so I can use it for the contest?

xtragamerpokemaster wrote:

Umm… I am going to use scratch 2.0 to make a game for the STEMchallenge… entries are due april 24….. and the winners are released some where near mid may…..so could you not stop the beta until after june or july so I can use it for the contest?

It's a little sketchy using beta software for something like this - beta means we don't swear it won't have glitches or go down the day you need to show your project, know what I mean?

But I don't think we'll take the beta down until 2.0 is released.