Skip to content

Conversation

@eyedeekay
Copy link
Contributor

This goes with the other I2P base32 pull requests, it adds i2p base32 addresses and adds descriptions of what the I2P Addresses are to the table.

@Stebalien
Copy link
Member

Can we call this "i2p base64 (raw public key)" and "i2p base32 (hashed public key)"? Every time I see "base64" versus "base32" I get confused and re-ask myself why we aren't just using multibase. Then I remember that we're just using the base encodings to distinguish between two very different address formats.

@eyedeekay
Copy link
Contributor Author

eyedeekay commented Apr 5, 2019

No problem. Technically it's just slightly inaccurate in some cases because that's not all the new base32's (for encrypted leasesets: http://www.i2p.net/spec/proposals/149-b32-encrypted-ls2) have, but that is the default and far and away the most common case. Edit: I extended it a bit, hopefully that's an acceptable description?

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(good enough)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants