-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change to base62 encoding #1
Labels
Milestone
Comments
@appointy/golang |
srikrsna
changed the title
Change from base32 to base62 encoding. This potentially allows for shorter ids.
Change from base32 to base62 encoding.
Jan 31, 2019
srikrsna
changed the title
Change from base32 to base62 encoding.
Change from base32 to base62 encoding
Jan 31, 2019
srikrsna
changed the title
Change from base32 to base62 encoding
Change to base62 encoding
Jan 31, 2019
We can use this library as it also uses timestamp and randomness to generate id and uses base 62 encoding. |
Create a Merge request without breaking any tests and API using the new package. If it can work we will use it. Also make sure compare the benchmarks. |
@imnikhil27 Update? |
In process sir |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The current implementation uses an optimised Crockford's base32 encoding (A-Z, 0-9) that is url safe. However due to the limited character set the ids are too long and potentially take up more space. It would be nice if it could be changed to a base64 (url safe) but unfortunately we lose the ability to select a the whole id using a cursor because separation characters like '.'
Hence this should be changed to a base62 notation i.e. (A-Z, a-z, 0-9).
Tasks:
[]byte
tostring
of base62string
in to a[]byte
The text was updated successfully, but these errors were encountered: