We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ffffffffffffffffffffffffffffffff
Compare the output from jxskiss/base62 to that from keys-pub/keys/encoding:
package main import ( "fmt" "github.com/jxskiss/base62" "github.com/keys-pub/keys/encoding" ) func main() { id := []byte{255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255} fmt.Println(base62.EncodeToString(id[:])) fmt.Println(encoding.EncodeBase62(id[:])) }
Output:
fffffffffffffffffffffffffH 7n42DGM5Tflk9n8mt7Fhc7
I believe keys-pub/keys/encoding is correct and jxskiss/base62 is not.
The text was updated successfully, but these errors were encountered:
FWIW, encoding/base64 emits _____________________w.
_____________________w
Sorry, something went wrong.
Playground
The two libraries use different algorithm to do encoding, which generates different output. You may read READM.md for details about the algorithm.
Interesting. I was just super surprised to see it be so uniform and long.
No branches or pull requests
Compare the output from jxskiss/base62 to that from keys-pub/keys/encoding:
Output:
I believe keys-pub/keys/encoding is correct and jxskiss/base62 is not.
The text was updated successfully, but these errors were encountered: