(country :: sensing)

(language :: sensing)

(language :: pen)

(North American Countries :: list)

Nambaseking01 wrote:

No support.

The workaround is really simple with the new translating extension in 3.0. Your project could just have a sprite asking what the language of the player is and it will automatically switch to that language. This could also be meant as “barging into information”, because some Scratchers might only want people that view their profile to see their location but this block could be used to send the location of the player to the creator using a few simple cloud and encrypting and decrypting scripts.

The location feature has even gone to the point to which some Scratchers suggested it be removed, but it became a rejected suggestion. This suggestion could cause a lot of disrespect and drama.

46009361 wrote:

Nambaseking01 wrote:

No support.

The workaround is really simple with the new translating extension in 3.0. Your project could just have a sprite asking what the language of the player is and it will automatically switch to that language. This could also be meant as “barging into information”, because some Scratchers might only want people that view their profile to see their location but this block could be used to send the location of the player to the creator using a few simple cloud and encrypting and decrypting scripts.

The location feature has even gone to the point to which some Scratchers suggested it be removed, but it became a rejected suggestion. This suggestion could cause a lot of disrespect and drama.

You are right in the fact that there is a language block, but I'm trying to show you that the main focus is for a hypothetical block called country. I know that the other thing is rejected because I saw the article the other day. I'm just saying that, as of the time of writing, the Scratch Team has yet to comment on the discussion. What I mean is that it would make coding easier for people because even if they use English, they may expect to see “colour” next and find “color” instead. This way, it would automatically determine which variation of English to use (especially if you have to switch to the right costume) based on the country of the user's profile. These two blocks (suggested and language already in extension) would be very good to use together. For example, it would be easier to use the same project for both people who speak British English and people who speak American English.

when green flag clicked
forever
if <(country :: sensing) = [Somepoorcountryeveryonehates-landia]> then 
say [Get out of this project NOW!]
else
broadcast [start project v]
end
end

VeryAnza wrote:

This block could be easily used to block users from specific countries from projects.
For example:

when green flag clicked
forever
if <(country :: sensing) = [Somepoorcountryeveryonehates-landia]> then 
say [Get out of this project NOW!]
else
broadcast [start project v]
end
end

(project [loves v] :: sensing)

VeryAnza wrote:

This block could be easily used to block users from specific countries from projects.
For example:

when green flag clicked
forever
if <(country :: sensing) = [Somepoorcountryeveryonehates-landia]> then 
say [Get out of this project NOW!]
else
broadcast [start project v]
end
end

46009361 wrote:

-snip-
You are right in the fact that there is a language block, but I'm trying to show you that the main focus is for a hypothetical block called country. I know that the other thing is rejected because I saw the article the other day. I'm just saying that, as of the time of writing, the Scratch Team has yet to comment on the discussion. What I mean is that it would make coding easier for people because even if they use English, they may expect to see “colour” next and find “color” instead. This way, it would automatically determine which variation of English to use (especially if you have to switch to the right costume) based on the country of the user's profile. These two blocks (suggested and language already in extension) would be very good to use together. For example, it would be easier to use the same project for both people who speak British English and people who speak American English.

46009361 wrote:

This way, it would be easier. Someone who creates the project may know lots of different variations of English (maybe classes, or Google Translate, or moving to different countries), and want it to show to the other people. They would probably just put American English if something such as Antarctica is set on the profile, or automatically (in the project) check if a user speaks Singaporean English or Canadian English or British English or Indian English or American English etc.

46009361 wrote:

-snip-
Oh well. It's the same concept as the rejected block

(project [loves v] :: sensing)

, according to The Complete List of Rejected Suggestions by @Za-Chary*. Anyway, I was thinking that, if they were to add the block, they would put a policy in place on the Announcements forum saying you cannot do that. Because people who have a verified email address will be notified if they still have access to the email account and are logged in at the time, even if they are not on Scratch, and most people update email addresses on their accounts regularly and verify them to allow them to continue receiving updates. Say, a Scratcher receives the email and finds a project that forces them to stop unless in Canada, but already lives in the United States. They also don't want to fake their location on a profile. It wouldn't be hard to moderate one extra thing as there are so many members helping out, reports are received regularly and checked multiple times a day, and according to this video, saying that asking if there is one lion shadow or two (which doubles the threat) is a very different question than asking if there are 96 shadows or 97 (which is basically nothing), even though there's one more lion shadow in both questions. It's the same concept in Scratch; there are so many policies, and adding one is essentially the same as adding no policies which would not make it that hard to moderate the website.

Nambaseking01 wrote:

46009361 wrote:

-snip-
You are right in the fact that there is a language block, but I'm trying to show you that the main focus is for a hypothetical block called country. I know that the other thing is rejected because I saw the article the other day. I'm just saying that, as of the time of writing, the Scratch Team has yet to comment on the discussion. What I mean is that it would make coding easier for people because even if they use English, they may expect to see “colour” next and find “color” instead. This way, it would automatically determine which variation of English to use (especially if you have to switch to the right costume) based on the country of the user's profile. These two blocks (suggested and language already in extension) would be very good to use together. For example, it would be easier to use the same project for both people who speak British English and people who speak American English.

46009361 wrote:

This way, it would be easier. Someone who creates the project may know lots of different variations of English (maybe classes, or Google Translate, or moving to different countries), and want it to show to the other people. They would probably just put American English if something such as Antarctica is set on the profile, or automatically (in the project) check if a user speaks Singaporean English or Canadian English or British English or Indian English or American English etc.

I understand the suggestion, I just disagree with it. I am trying to say that people dislike the location feature already, and if this gets implemented then it would cause tons of drama. If you take a look at Anza's post, it gets clarified that this block could get flame wars started about politics (and the ST is completely against things like that).

46009361 wrote:

-snip-
Oh well. It's the same concept as the rejected block

(project [loves v] :: sensing)

, according to The Complete List of Rejected Suggestions by @Za-Chary*. Anyway, I was thinking that, if they were to add the block, they would put a policy in place on the Announcements forum saying you cannot do that. Because people who have a verified email address will be notified if they still have access to the email account and are logged in at the time, even if they are not on Scratch, and most people update email addresses on their accounts regularly and verify them to allow them to continue receiving updates. Say, a Scratcher receives the email and finds a project that forces them to stop unless in Canada, but already lives in the United States. They also don't want to fake their location on a profile. It wouldn't be hard to moderate one extra thing as there are so many members helping out, reports are received regularly and checked multiple times a day, and according to this video, saying that asking if there is one lion shadow or two (which doubles the threat) is a very different question than asking if there are 96 shadows or 97 (which is basically nothing), even though there's one more lion shadow in both questions. It's the same concept in Scratch; there are so many policies, and adding one is essentially the same as adding no policies which would not make it that hard to moderate the website.

You are thinking about the millions of people that do not see a rude project made by someone, but someone does need to see it if it has to get reported, right? Being scared for FNAF projects is one thing, you will forget that in a bit of time but if you know thousands of people are disliking you throughout your life, can you ever get out of that? Like I said, this block would cause tons of drama and in the worst case even depression and anxiety.

By the way, please use paragraph breaks when you post — that way it's not confusing to read your posts.

KingOfAwesome58219 wrote:

So:

(language :: sensing) // gives the language that the scratcher is using scratch in
(country :: sensing) // gives the country the scratch has selected on their profile

I really like this idea. Support!

What would the (country) block return if the scratch had no country selected? Just a “No Given Location,” or maybe undefined?

As with the username block, it should have a “This project can detect which country you have selected on your profile,” and “This project can detect which language you have selected,” What would happen if you had multiple of these messages?

if <(country) = [(Random Country so I don't affend anybodydy)]> then
say [Your country is TRRRASH and you KNOW IT]
end

Boomer001 wrote:

No support.
People could use encoding and decoding scripts and put the encoded text in a cloud variable, so anyone can see where the person lives. I believe nobody likes that.

VeryAnza wrote:

This block could be easily used to block users from specific countries from projects.
For example:

when green flag clicked
forever
if <(country :: sensing) = [Somepoorcountryeveryonehates-landia]> then 
say [Get out of this project NOW!]
else
broadcast [start project v]
end
end

when green flag clicked
if <(☁ selected country) = [Spain]> then
set [language] to [Spanish]
end

NogSan wrote:

VeryAnza wrote:

This block could be easily used to block users from specific countries from projects.
For example:

when green flag clicked
forever
if <(country :: sensing) = [Somepoorcountryeveryonehates-landia]> then 
say [Get out of this project NOW!]
else
broadcast [start project v]
end
end

Yeah, but they could then just report the project.

when green flag clicked
if <(☁ selected country) = [Spain]> then
set [language] to [Spanish]
end

This block, for example, could be useful

NogSan wrote:

Boomer001 wrote:

No support.
People could use encoding and decoding scripts and put the encoded text in a cloud variable, so anyone can see where the person lives. I believe nobody likes that.

Yeah, I know, but if the block used the place where the username wrote he was it would be the same as looking in their profile.

PizzaAddict4Life wrote:

Support! I am pretty sure you can see a user's country anyway, so it wouldn't reveal info. That could be used for a lot of interesting things

when green flag clicked
if <[(country)] = [some country that receives a lot of racism]> then
say [I hate you! Your country is the worst! You don't deserve to play this game!]
stop [all v]
else
say [Glad you're not from the bad country  ]
broadcast [Start game v]
end