We have changed from a simple 4-bit per character md5 style session ID, to a 6 bit per character sha512 hash.
The effect is that all "sid" session ID values will be much longer and contain a wider range of characters.
Example md5 hash (old sid): 9e107d9d372bb6826bd81d3542a419d6
Example sha512 hash (new sid): UX8ScxaAoJI2i9WvhUSrHw6vVzJFkCZ3-4vsbiRmA,kylJ4C0DY5qT0T5sGmPX2Ixyiimn0Yn-,QKxVqIzE4T2
Please note that sha512 hashes in 6 bit mode contain the full range of alphanumeric characters, including capitals and lowercase, but also the comma and dash characters.
This shouldn't pose any problems unless you have set the sid in your programs to be a particular variable type (it used to be hexadecimal values only), or if you happen to run any kind of sanity checking on sid values.
Please report any issues this latest update causes with your use of the API.
I wanted to ask about the "Crowd". Me and my friend tried using it but we could not make a new Crowd. Is there some step we are missing or is it incomplete?
I wanted to ask about the "Crowd". Me and my friend tried using it but we could not make a new Crowd
