3
what wor you doing with it, all you had to do was transpose the robot-host to stuff like googlebot.com or 130.20.11.1|130.20.11.2|130.20.11.3 or 130.20.11.1-128|hackbot.com and so on to allow different patterns of robots in... I don't know where that 40 comes from... It is no where i can see in the code.
We should have a working bee, it should be with the preloaders -> pushing data between them both, I am not sure if that is working either.. Currently on mine i can't tunnel to port 43, for the abuse notices that your's also then, see when and IP comes up in it, it will dial into the whois and start looking up email addresses associated with it. And send them an Abuse Notice!! there is a template for it you should be more interested in looking up.. See spiders on the server operates as a sentry into the ban list so no bots from the knowlegde of the spider robot-hosts - don't get banned and you and us!! I am going to make a form one-day so people can enter there bot into the cloud and it push and pulls it.
Also Xortify Server should be using a different version of signup API Calls which it was working when i first tried on yours. And manually put you in the xortify.com site so it can be api called, but you should have been pushed my userbase by now, and it hasn't seem to happen? do you have some form of security on it with UserAgents cause they do exist in the software?