Skip to content

Why these three encodings? #6

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

Open
domenic opened this issue Jul 1, 2021 · 2 comments
Open

Why these three encodings? #6

domenic opened this issue Jul 1, 2021 · 2 comments
Labels
blocker Something isn't working

Comments

@domenic
Copy link

domenic commented Jul 1, 2021

The README makes the claim they are the most common:

This is a first pass with just the 3 most common encodings. Support for "base62", "base32", and various other encodings can be added after initial consensus and implementation.

Is there any way to back this up? Apparently there are a lot: https://en.wikipedia.org/wiki/Binary-to-text_encoding

@lucacasonato
Copy link
Owner

These three encodings are the ones available in all of the environments mentioned in the proposal (Go, Dart, Node.js, Deno) out of the box. This suggests that they are the most commonly used encodings.

@domenic
Copy link
Author

domenic commented Jul 7, 2021

Elsewhere, @bakkot says that apparently Node.js's Buffer.from(x, "base64"), as well as CSP, support mixing base64 and base64 URL in the same string, when decoding. That might be an encoding worth supporting as well.

Cross-linking to tc39/proposal-arraybuffer-base64#7 (comment) for related analysis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants