Trying to integrate consento-crypto with hypercores I noticed that the naming didn't seem to be right, particularly when talking about the encryption properties. To see how it would feel differently I tried in this PR to replace Receiver with Reader and Sender with Writer to give a sense on what they enable to do under the aspect that the interaction is based on the channel. Looking at the documentation it does seem much clearer now what one can do with this API.
Trying to integrate consento-crypto with hypercores I noticed that the naming didn't seem to be right, particularly when talking about the encryption properties. To see how it would feel differently I tried in this PR to replace
Receiver
withReader
andSender
withWriter
to give a sense on what they enable to do under the aspect that the interaction is based on the channel. Looking at the documentation it does seem much clearer now what one can do with this API.Readme.md
Do you think these changes are an improvement in the readability?
Note: this PR is based on #6 and #3 respectively, those should be merged before this one.