[Removed—please use language appropriate for everyone] its not meh username

“User ID” is your viewer number. If you are the first viewer, you have user ID 1. If you are not logged in to the Scratch website, you have user ID 0.

dr3w8
“User ID” is your viewer number. If you are the first viewer, you have user ID 1. If you are not logged in to the Scratch website, you have user ID 0.

I was wondering that, too

Each time a person visits the project they get the same userid for that project.

They need to bring back the cloud data

xtragamerpokemaster
They need to bring back the cloud data

They need to fix it and the userid block first.

But, yeah.

BoltBait wrote:

Each time a person visits the project they get the same userid for that project.

With enough blocks and enough variables, if it keeps the same UserID if you come back, you could make a working login system.

Tierage27 wrote:

BoltBait wrote:

Each time a person visits the project they get the same userid for that project.

With enough blocks and enough variables, if it keeps the same UserID if you come back, you could make a working login system.

Yup

BoltBait wrote:

xtragamerpokemaster wrote:

They need to bring back the cloud data

They need to fix it and the userid block first.

But, yeah.

What's wrong with the userid block?

MelonInc wrote:

BoltBait wrote:

xtragamerpokemaster wrote:

They need to bring back the cloud data

They need to fix it and the userid block first.

But, yeah.

What's wrong with the userid block?

I think some people were getting an ID that someone else had (not counting 0).

Another question, can the Scratch Team trace the member with the ID?

XDGames wrote:

Another question, can the Scratch Team trace the member with the ID?

No, I don't think so.

Tierage27 wrote:

XDGames wrote:

Another question, can the Scratch Team trace the member with the ID?

No, I don't think so.

Correction they can the could even before userid block using your ip this make it easier

MelonInc wrote:

BoltBait wrote:

xtragamerpokemaster wrote:

They need to bring back the cloud data

They need to fix it and the userid block first.

But, yeah.

What's wrong with the userid block?

Two main issues.

First, the userid block was not giving consistent results. The first time I ran my project I got a 2 for userid. The next time (and all subsequent times) I got a 3.

Second, the userid block was assigning the same userid to different people.

Both of these issues have been filed in their bug tracking system.

XDGames wrote:

Another question, can the Scratch Team trace the member with the ID?

No. The Scratch Team was rather silly and decided to store a hash of the username with the userid. This table is internal (not accessible to the public) so it seems unnecessary to have that level of security on it. It's not like they're storing a password or something.

Well, if they implement that feature, I think the chatroom problem will be solved.

But, let's not start another subject, though.

xtragamerpokemaster wrote:

They need to bring back the cloud data

They will. Be patient.

BoltBait wrote:

XDGames wrote:

Another question, can the Scratch Team trace the member with the ID?

No. The Scratch Team was rather silly and decided to store a hash of the username with the userid. This table is internal (not accessible to the public) so it seems unnecessary to have that level of security on it. It's not like they're storing a password or something.

The mappings are publicly available. Example.

nXIII wrote:

BoltBait wrote:

XDGames wrote:

Another question, can the Scratch Team trace the member with the ID?

No. The Scratch Team was rather silly and decided to store a hash of the username with the userid. This table is internal (not accessible to the public) so it seems unnecessary to have that level of security on it. It's not like they're storing a password or something.

The mappings are publicly available. Example.

Why was that done? It removes some of the privacy from the user (stored usernames can be checked against the hash if desired, and sometimes even used on an online hash database to get the source of the hash) and serves no purpose to an honest third party application.

nXIII wrote:

BoltBait wrote:

XDGames wrote:

Another question, can the Scratch Team trace the member with the ID?

No. The Scratch Team was rather silly and decided to store a hash of the username with the userid. This table is internal (not accessible to the public) so it seems unnecessary to have that level of security on it. It's not like they're storing a password or something.

The mappings are publicly available. Example.

I will assume that this is for debugging purposes only and is a security hole that will be closed before public release.

Other than that, I can't even imagine why this data is publicly available.

This Username/Password has some examples of using UserIDs and how this project could work when cloud variables are enabled.