Scratch

The

search [foo] on [google v]

search [something inappropriate] on [google v]

bubby3 wrote:

or should look like this

<[] or []>

The or block already exists. 

lalala3 wrote:

Mokat wrote:

The

search [foo] on [google v]

could be dangerous because for example, someone could put

search [something inappropriate] on [google v]

or something like that.

Well, that argument doesn't work. Why? Because someone can go take anything inappropriate and put it in their project anyways. What's the difference? If you want to stop that line of inappropriate content:
1. Ban sprite costumes. Inappropriate content can be shown in them.
2. Ban backgrounds. Inappropriate content can be shown in them, too.
3. Ban pen blocks. Inappropriate content can be shown using these as well.
4. Ban variables/lists/etc. that are showing on the screen, for the same reason.
5. Ban sounds, again, see above for reason.

What lovely Scratch projects this would make. What lovely Scratch projects indeed. Anything that gives output being banned makes for a pretty boring project. Oh, and I forgot. Projects can't have titles and users can't have usernames, either. Now do you see why that doesn't work?

But the ST can't ban Google.  They can remove the Google block.

lalala3 wrote:

Firedrake969 wrote:

lalala3 wrote:

Well, that argument doesn't work. Why? Because someone can go take anything inappropriate and put it in their project anyways. What's the difference? If you want to stop that line of inappropriate content:
1. Ban sprite costumes. Inappropriate content can be shown in them.
2. Ban backgrounds. Inappropriate content can be shown in them, too.
3. Ban pen blocks. Inappropriate content can be shown using these as well.
4. Ban variables/lists/etc. that are showing on the screen, for the same reason.
5. Ban sounds, again, see above for reason.

What lovely Scratch projects this would make. What lovely Scratch projects indeed. Anything that gives output being banned makes for a pretty boring project. Oh, and I forgot. Projects can't have titles and users can't have usernames, either. Now do you see why that doesn't work?

But the ST can't ban Google.  They can remove the Google block.

If you can't read all of it, at least read this part.

However, I did read all of it.  The Google thing is harder to be implemented as well.

lalala3 wrote:

Mokat wrote:

The

search [foo] on [google v]

could be dangerous because for example, someone could put

search [something inappropriate] on [google v]

or something like that.

Well, that argument doesn't work. Why? Because someone can go take anything inappropriate and put it in their project anyways. What's the difference? If you want to stop that line of inappropriate content:
1. Ban sprite costumes. Inappropriate content can be shown in them.
2. Ban backgrounds. Inappropriate content can be shown in them, too.
3. Ban pen blocks. Inappropriate content can be shown using these as well.
4. Ban variables/lists/etc. that are showing on the screen, for the same reason.
5. Ban sounds, again, see above for reason.

What lovely Scratch projects this would make. What lovely Scratch projects indeed. Anything that gives output being banned makes for a pretty boring project. Oh, and I forgot. Projects can't have titles and users can't have usernames, either. Now do you see why that doesn't work?

Well, another argument for the GOogle block is that sometimes, even when searching something that seems like it shouldn't bring up inappropriate content, things come up anyways that wouldn't be safe for Scratch. And, if a kid finds this stuff and it originated from Scratch, that would make it the ST's fault that the kid got to the inappropriate stuff. Plus, the ST would have to get Google's permission to have that block too, and besides, when would you even really use it?

lalala3 wrote:

Firedrake969 wrote:

lalala3 wrote:

If you can't read all of it, at least read this part.

However, I did read all of it.  The Google thing is harder to be implemented as well.

Really, now? So you think it would be fine if everything listed there was banned? Also, I fail to see how it would be a challenge for the ST, given what they've already accomplished.

No, that's not what I said.  Here's a different version.  I read all of it.  The internet will NEVER be perfectly safe, no matter what people do.  Google is a rather large company.  It won't just say "sure, whatever" to the ST.  It's not that simple.  You have legal matters, privacy policies, and such.  It could potentially crash someone's computer.

forever
search [foo bar] on Google

30-1 wrote:

jvvg wrote:

bubby3 wrote:

or should look like this

<[] or []>

The or block already exists. 

The or block looks like this:

<<> or <>>

bubby3 wrote:

or should look like this

<[] or []>

Workaroundable
if pick random 0 to 1 = 0
case 1
else
case 2

Firedrake969 wrote:

lalala3 wrote:

Firedrake969 wrote:

However, I did read all of it.  The Google thing is harder to be implemented as well.

Really, now? So you think it would be fine if everything listed there was banned? Also, I fail to see how it would be a challenge for the ST, given what they've already accomplished.

No, that's not what I said.  Here's a different version.  I read all of it.  The internet will NEVER be perfectly safe, no matter what people do.  Google is a rather large company.  It won't just say "sure, whatever" to the ST.  It's not that simple.  You have legal matters, privacy policies, and such.  It could potentially crash someone's computer.

forever
search [foo bar] on Google

could crash your browser and possible computer.  The ST cannot force you to put SafeSearch on.

I meant that SafeSearch was on by default, and one had to deliberately turn it off to see inappropriate content. Are we clear now? For the infinite search thing, there are ways to stop that. For example, it could pause the project for a fraction of a second, allowing you to stop the project before any harm is done.

Last edited by lalala3 (2012-12-29 14:31:49)

iTweak0r wrote:

The

search [blah] on [google v]

could be dangerous because for example, someone could put

forever
  search [blah] on [google v]

That would overload your browser tabs.

Okay. Seeing as my previous response was hidden (because of someone with an overactive Report-button finger, no doubt), I'll put it in nicer terms. Looking up five posts from yours, you will find this:

Firedrake969 wrote:

forever
search [foo bar] on Google

could crash your browser and possible computer.

Notice the similarity? I even quoted it in the post I made, directly above yours, by the way.

Last edited by lalala3 (2012-12-29 22:48:13)

lalala3 wrote:

Firedrake969 wrote:

lalala3 wrote:

Really, now? So you think it would be fine if everything listed there was banned? Also, I fail to see how it would be a challenge for the ST, given what they've already accomplished.

No, that's not what I said.  Here's a different version.  I read all of it.  The internet will NEVER be perfectly safe, no matter what people do.  Google is a rather large company.  It won't just say "sure, whatever" to the ST.  It's not that simple.  You have legal matters, privacy policies, and such.  It could potentially crash someone's computer.

forever
search [foo bar] on Google

could crash your browser and possible computer.  The ST cannot force you to put SafeSearch on.

I meant that SafeSearch was on by default, and one had to deliberately turn it off to see inappropriate content. Are we clear now? For the infinite search thing, there are ways to stop that. For example, it could pause the project for a fraction of a second, allowing you to stop the project before any harm is done.

Safe search isn't as reliable as you think. I've gotten inappropriate results even with it on. If you enter a keyword that is itself inappropriate, I think you will get at least some inappropriate results.

As for infinite search, that's still not enough. If I get up from my computer with a project open and come back to find 50 new tabs of a Google search, I won't be happy.

Nobody reads the stickies... This is never coming in Scratch...

You can do this

when [space v] key pressed 
jump

jump
repeat (10)
  change y by (10)
end
repeat (10)
  change y by (-10)
end

Last edited by bubby3 (2012-12-30 15:25:56)