I want blocks like this:

<geolocation on? :: sensing>
(latitude :: sensing)
(longitude :: sensing)

Pros:
Fake GPS check
Storing them in cloud list engines to determine how far a player has gone since the last visit
Time-zoned leaderboards
Cons:
Preventing them from playing unless they are in a specific location, like:

when green flag clicked
if <not <(longitude :: sensing) = (0)>> then
  say [You must go to the equator to view this project!
  repeat until <(longitude :: sensing) = (0)>
    say (join [You have been here for ] (join (timer) [ seconds and you're still not on the equator yet!]))
  end
  broadcast [start v] and wait
else
  broadcast [start v] and wait
end

A possible violation of COPPA compliance for a site aimed mainly at children aged 8–16

How much decimal points would be the maximum? (I don't want users to find out where exactly in Czech Republic do I live.)

WindOctahedron wrote:

How much decimal points would be the maximum? (I don't want users to find out where exactly in Czech Republic do I live.)

I don't know. There would probably be a warning before the project starts, as well as maybe seeing it as an extension in the bottom instead of in the Sensing category. And then, most users would think before clicking the flag if there are cloud variables right next to it.

kChiaEC19 wrote:

There would probably be a warning before the project starts, as well as maybe seeing it as an extension in the bottom instead of in the Sensing category.

Something like this:
"This project can track your location and may also contain cloud data. Please think twice before starting.

Support, I've got some more blocks too:

(scratcher's country:: pen)// gets the country the scratcher has picked (the one on the account page)
(country:: pen)// gets the country the scratcher is currently in

C0nyc0n wrote:

Support, I've got some more blocks too:

(scratcher's country:: pen)// gets the country the scratcher has picked (the one on the account page)
(country:: pen)// gets the country the scratcher is currently in

Why did you change the color from sensing color to pen color?
There does appear to be a duplicate of your quote here (not this whole thread here, but just your quote): https://scratch.mit.edu/discuss/topic/223436/

From a thread about a similar suggestion:

Paddle2See wrote:

If it was just the country (not the city or county), I don't think it would be much of a safety issue.

But the other thing to think about is how useful would it be?

kChiaEC19 wrote:

C0nyc0n wrote:

Support, I've got some more blocks too:

(scratcher's country:: pen)// gets the country the scratcher has picked (the one on the account page)
(country:: pen)// gets the country the scratcher is currently in

Why did you change the color from sensing color to pen color?
-snip-

Because they thought that it would be an extension, and this is the color for all extensions (not just Pen) in Scratch 3.0.

Geolocation… What purpose would that serve? And if the scratcher's haven't got any connection to the internet? How would that block work in that case? Seems like a simple block but so much stuff has to be considered…

Depending on how it outputs, I'm going to agree with this. However, this should not be refined, since it can be exploited.

Banana

niamrogn wrote:

Geolocation… What purpose would that serve? And if the scratcher's haven't got any connection to the internet? How would that block work in that case? Seems like a simple block but so much stuff has to be considered…

Sorry, I wasn't checking on this topic for a while. However, the direct latitude and longitude (not the name of the associated place on an online [not downloaded, offline] map, but just the floating-point numbers of the coordinates) can be obtained without an internet connection, provided that the user agrees for the browser to send the coordinates at the time to the built-in JavaScript Geolocation API.

banana439monkey wrote:

Depending on how it outputs, I'm going to agree with this. However, this should not be refined, since it can be exploited.

Banana

Do you mean refining the suggestion? But the suggestion may need to be refined because the number of digits to round to in the geolocation wasn't specified in the OP (though WindOctahedron asked a question about how many digits, but I haven't thought of an answer yet).

Edit: After my bump, the topic left the first page before barely 24 hours were up.

This would ust lead to things like geoblocking… So no support

_chai_latte_ wrote:

This would ust lead to things like geoblocking… So no support

I agree this could be used for that, but you can also use the username function to block users. I support.

_chai_latte_ wrote:

This would ust lead to things like geoblocking… So no support

Just because a part of a script containing a block can be used to block users from viewing a project unless a user is in a (range of) physical location(s) doesn't mean that the block will be used to violate the Community Guidelines in such a way. Same with the username block; it can be used in that way, but it most likely and usually doesn't (for the few projects that do, the Report button is sufficient).

Wouldn't this project be able to get a approximate idea of where you are, therefore putting the user at risk

JPOWERPUFFGIRLS wrote:

Wouldn't this project be able to get a approximate idea of where you are, therefore putting the user at risk

Yes, somebody could create a script like this:

when green flag clicked
insert (join (join (longitude ) (latitude)) (username)) at (1 v) of [list v]

And then create a list of usernames and locations, essentially doxing people.

pavcato wrote:

JPOWERPUFFGIRLS wrote:

Wouldn't this project be able to get a approximate idea of where you are, therefore putting the user at risk

Yes, somebody could create a script like this:

when green flag clicked
insert (join (join (longitude ) (latitude)) (username)) at (1 v) of [list v]

And then create a list of usernames and locations, essentially doxing people.

Then people can know where you are, in a more detailed way than just your country, no support

JPOWERPUFFGIRLS wrote:

pavcato wrote:

JPOWERPUFFGIRLS wrote:

Wouldn't this project be able to get a approximate idea of where you are, therefore putting the user at risk

Yes, somebody could create a script like this:

when green flag clicked
insert (join (join (longitude ) (latitude)) (username)) at (1 v) of [list v]

And then create a list of usernames and locations, essentially doxing people.

Then people can know where you are, in a more detailed way than just your country, no support

Yep, people could dox you and find your location. I would only support this if it kept to country. No support.

pavcato wrote:

JPOWERPUFFGIRLS wrote:

pavcato wrote:

JPOWERPUFFGIRLS wrote:

Wouldn't this project be able to get a approximate idea of where you are, therefore putting the user at risk

Yes, somebody could create a script like this:

when green flag clicked
insert (join (join (longitude ) (latitude)) (username)) at (1 v) of [list v]

And then create a list of usernames and locations, essentially doxing people.

Then people can know where you are, in a more detailed way than just your country, no support

Yep, people could dox you and find your location. I would only support this if it kept to country. No support.

But the problem is that cloud lists don't exist and lists' data disappear when the browser refreshes the page, provided it isn't modified from the .sb3 file. People would then have to resort to using a cloud list engine, but cloud data is limited per project.

How about we just don't allow projects to put latitude/longitude in cloud variables?
Like, when you put a latitude/longitude variable in a cloud variable, it simply wouldn't let you. Of course, you could just add their location to another variable that transmits that to a cloud variable though.

Also, would the output be something like “0 L” or just “0”? I would support it being “0 L” because then to store data in a cloud variable, you have to also encode/decode it, making a lot of work to do that.

geometric_ghast wrote:

Also, would the output be something like “0 L” or just “0”? I would support it being “0 L” because then to store data in a cloud variable, you have to also encode/decode it, making a lot of work to do that.

just remove the L i guess. just store every character in a list, remove the last one or two (because of the space) and the reassemble it.