Remove console.log in src/ about signal-protocol

[derhuerst]

The debug module might also work.

[elsehow]

@derhuerst That could be good!

I am not sure yet which of these messages the caller might care about or want to work with programmatically, and which of these messages are, "everything is working fine, FYI!"

[derhuerst]

Theoretically, all the messages that a caller is interested in should be available via returns values, events, or something similar. Console logging a very unintuitive and also inflexible way of getting messages, but certainly necessary in debugging. That's why I propose debug for internal messages that only contain messages related to the inner workings of the module and events/return values/exceptions for all messages interesting to "outsiders".

[elsehow]

Sounds good to me. If someone ends up needing a value or event, we can always pass it up as an event later.

As an initial step, I may just go through and comment out all of the console.log statements. The comments can serve as a guide for helpful things to debug.

[elsehow]

I commented out all the console.logs in 79f7037 and published v0.0.6

I think I will close this issue for now. If callers end up needing these messages, we can use debug or whatever else makes sense for their usecase 👍