Mike Greenberg

@hoffmabc if we're pursuing this, I'd like to see the following improvements after doing a quick scan through: 0) Update the PR description indicating what impact these changes will have....

Thinking about this further, I like that this was produced as a separate manager from a pattern perspective. However, I think that our message sending is getting spread across a...

Worst case: Any errored message which gets processed by this could potentially be processed more than once depending on where the message processing fails. Not all of our message handling...

> Currently, the only messages which persist with an error are pb.Message_ORDER_COMPLETION messages, but there's is nothing limiting it to just this type. Errored message means an OB message which...

After discussing the suggestion in private, @amangale is on board with the plan as originally described above. For historical purposes, my observations are outlined below: --- Some thoughts after reviewing...

Additionally, we briefly discussed the plan of attack for this large scope w/ @drwasho and @amangale. The idea was raised to begin in the ETH wallet implementation as it is...

@IzzySoft Yes, I expect it would work the same as any other ARM-based architecture computer, but I haven't tried it personally. You could try to manually build on the bananapi...

I'm sorry to say that I have not been able to invest time on this. I don't know whether I will be able to in the near future as our...

Had a meeting with the folks from Textileio and got some additional insight. Updated the description with this gained insight. Will begin exploring how to close the dependency gap as...

Some additional thoughts: we only care about these offline order messages for as long as someone might be using the order. The longest use cases of the order remaining active...