Jacopo Scazzosi

@noodlefrenzy yes, absolutely. I'd say there could be even hours of no messages being sent - mostly at night. @noodlefrenzy @mbroadst thanks for your support. I guess I'll refactor things...

@noodlefrenzy my best guess would be anywhere between 2 to 5 days from starting the system @ 100 - 2k messages per day per link, received in bursts of 10...

Quick follow-up @noodlefrenzy @mbroadst: We've just seen the same error making an appearance after two weeks without glitches. This time, though, it's taken a complete reboot of the VM to...

@noodlefrenzy: I'm sorry I have come across in the wrong way - I absolutely did not mean to imply that your code was responsible for that. My intent is to...

:) I will give that a try over the next few days and report back with my findings. Once again, thanks a lot. On Tuesday, August 18, 2015, Michael Lanzetta...

Hello @noodlefrenzy, hello @mbroadst. Here's another follow-up on this issue. Over the last two weeks we had the same thing happen two times. I've been able to check the machine's...

Hello @noodlefrenzy. 1) Nope, I've never heard from them. 2) Yes, I realized a while ago that it had been published on NPM. Unfortunately, I'm still to be scheduled the...

Hello @noodlefrenzy and @mbroadst. Unfortunately we're yet to switch to V2. However, I believe I have some useful feedback (which might also relate to #152). As partly mentioned in my...

Hello @noodlefrenzy. Thank you for getting back at me so quickly. Ok, I understand about the networking issue. Will tell the team. Yes, the credentials are still the same. >...

> It's not really a bug but we can improve the experience by: > > * optimistic update > * add hot/slow hours and/or increased polling when actions are taken...