"I assume from that answer robix is a very customised version of robin?"
No it's as close to the equivalent version of robin as I can manage at the time, I am trying to clone exactly but due to nodogsplash issues on x86 and a slightly different base openwrt there are nigglie differences ie the coova one found and fixed by darrenp (to be included in next release see - "Bug in robix with Coova. (with fix!)" in this forum). Its just that these things take more time than you think and require me to look very closely at all the changes, over a hundred so far, from the last build I copied to assess their arch significance. For example the next release may well have to deal with the re-included mtd flashing program which has no counterpart in x86 as far as I'm aware. I will also have to work out how to include the customized code for udhcpd (having noticed it in the first place); plus the inclusion of the new batmand binary to sort. I would also like to try and include usb support as some people would like that but that might be a step too far, given the number of changes I have to catch up on.
And theres the fact that I'm a bit slow, I can't help it, but I try.
Early on in the development of robix I did clone and maintain and host (with the assistance of opensourcemesh) online updates but his proved to be too much of a time drain and given the early nature or robin / robix at the time and singular brain resources available I had to leave it be for the time being. This process may now have become more complex if it also includes the use of mtd. Haven't looked at it for a bit. There is also the single point of failure for all robix machines world wide to consider. I think it best to not provide this facility until robix is based on a stable release of robin. But the facility is in there all the same for anyone to change the website that robix uses away from opensourcemesh and host their own update scripts / programs.