Log all messages received

[atoulme]

Upon receiving a message, the program should increase its number of hops. It should then log to stdout the contents of the message. The log line should be timestamped.

[adam-hanna]

TBD

https://github.com/agencyenterprise/gossip-host/blob/6c5adf566b389edd47656e75a229e354c06e1e57/internal/host/pubsub.go#L31

[araskachoi]

will need to have these fields in the log:

• Message type - topic of the message
• Message origin - sending address
• Message destination - receiving address
• Last relaying node - the previous node that sent the message
• Message nonce - chronology of the sent message
• Message size - the message size will be in bytes
• MessageID - unique string associated with that message
• HopCount - number of hops the message had to make in order to reach its destination

[adam-hanna]

@araskachoi regarding hop count, how can I add 1 to the message hop count before sending to the next subscriber?

Did you implement that functionality in your original implementation? If so, could you point me to the line in your code, please?

Here's the TODO in mine:
https://github.com/agencyenterprise/gossip-host/blob/dab11fd173ae02f9004ebc78ffa45c11a5c24521/internal/host/pubsub.go#L28

[araskachoi]

We did not have this implemented inside ours. I found this which might be what we need
https://github.com/libp2p/go-libp2p/blob/master/p2p/host/relay/autorelay.go#L175

If this does not give what we need, we can just implement this in our application logic to trace the previous sender and keep tracing it back to the origin, which will be the number of hops. Doing it retroactively like this will be tedious and computationally exhaustive but cannot be helped if all other options do not work.

[araskachoi]

We will need to ask PL if we can alter the source code to make sure that we can edit the message struct to increase the hop count. @adam-hanna will ask PL about this and update on what they say!

[adam-hanna]

I asked this question to Steve Allen yesterday, along with asking for his signoff on our host implementation. I'll revert when he responds.

We can always just do this via our analysis layer. I don't think it'll be necessary to edit the PL gossip library.