IRC log of #cubox of Fri 02 Sep 2016. All times are in CEST < Back to index

12:25 topi` jnettlet: sorry, was very busy with another client :) I will look at that rw_regulator.tar.xz asap
12:25 jnettlet topi`, no hurry.
12:26 topi` jnettlet: it seems we're poorly synced :)
12:26 topi` I guess you were having vacations
12:27 topi` october is coming soon! is the 8040 board more or less in schedule?
12:27 jnettlet topi`, no actually my IRC bouncer have died so I was receiving messages but anything I sent out went into a black hole
12:27 topi` jnettlet: you'd need some diagnostics built-in to notice it :)
12:28 jnettlet topi`, well I just added some reconnection code to it. I think it reconnected but as some anonymous user or something.
12:28 jnettlet really I would like something better but most the solutions are still not to my liking.
12:28 topi` :)
12:29 topi` I once attempted to implement an IRC client that I could reattach with via a Web interface :)
12:29 jnettlet I have been looking at an IRC to slack bouncer to link our #cubox channels into the SolidRun slack
12:29 topi` but it would normally use Curses
12:29 topi` dunno about slack, our corporate solution is Hipchat
12:29 jnettlet yeah I prefer it to be a web page, and preferable with an Android client
12:30 topi` I need to find someone to finish my unfinished code :)
12:30 jnettlet ultimamtely I want a client that can take all these stupid services and normalize it
12:30 topi` the amount of different services is ... stupefying
12:31 jnettlet libpurple used to do that, but I want something server side and then stash everything as json in a messaging protocol like mqtt, or ampq.
12:33 jnettlet I guess that is what the signal protocol is supposed to be about.
12:34 jnettlet but I want all around messaging and not just chat messagaing
12:34 jnettlet messaging
12:36 jnettlet topi`, in case you missed my follow up. This will only fix the regulators for the main 2 usb ports...I have patches in another tree for the additional ports