Talk:$BotINFO

Sedulus

is this enough info? what about maxslots, maxuploadlimit, slotsper_hub? perhaps one should adopt xml syntax here instead..

GagGet

Well it's a good start for collecting some info users might be interested for the hublist. Only www.hublist.org bot collects now this information afaik, 557 of 2272 online hubs gives it. Bot won't mind if there is more or less fields separated by dollars, it just collects available data from the beginning.

Sedulus

I will for now assume that: - this command can only be sent once the client has been validated - an empty field will denote unlimited (or not-available where appropriate) would that be correct?

GagGet

Well HubINFO will be requested once by hublist.org pinger and pinger leaves immediately after it's got NickList, OpList and HubINFO (It waits 10 seconds for HubINFO after nicklists before leaving). Empty field = not available.

Sedulus

- hrmz.. so I'll have to add high integers for MaxUsers and MaxHubs? not good.. perhaps one could have a -1 denote unlimited then? - ".. will be requested once .." was not the answer. I meant, is the command first sent when the client has sent or recieved it's own MyINFO, on recieving Hello, or even earlier? currently the HubRules plugin will only accept it after it has been Validated (on dch++ that means that the client is able to send a GetNickList to recieve NickList/OpList/MyINFO's from all users including itself. if GetNickList is not sent, HubName would be the one identifier to go by)

GagGet

- If MaxUsers0 or MaxHubs0 then it's considered as unlimited (doesn't show on hub property page). - Pinger sends $BotINFO after it's logged on, most hubs don't like additional commands before logging so to avoid being kicked, it's usually the last command pinger sends. Btw, pinger should not send any $ConnectToMe or $Search commands.

b_w_johan

Bot description can be any string, usually information regarding, and address of, the hublist

i was wondering, what if something like this would be send in $BotINFO

$BotINFO <website>$$<address/filename>$$<.xml>,<.conf>,<.xml.bz2>$$<registeradres>$$<hubvote>|

website: obviously will leed to some weboutput of the hublist

address/filename: will be like website/hublist

extensions: seperated with, will be added to the website/hublist part, so hub can print this link in main perhaps?

registeraddress: hub can add (if not there) to the list

hubvote: percentage of * the hub is on that moment.

so if this would be a default string, wouldn't that be way handyer for hubsofts, or scripters like for px and other hubsofts?

b_w_johan

$BotINFO <website>$<address/filename>$<.xml>,<.conf>,<.xml.bz2>$<registeradres>$<hubvote>|

i'll make my pinger using this string, hope other hublists will use same in pinger so we have some default in it, had a little discussion, and the idea was mentioned better use 1 $ to splitt, orr add $$ before the | so im now using seperation with just 1 $ why add more useless chars. i'll read this discussion often, so hope on comments and so we get a default for it wich hubsoft and hublist can use. one more note to my idea :P hubvote is gonna be a integer 0-5, where 0 = unvoted.

NeiSep What about have total ping and total fail ping ? like this: $BotINFO <website>$<address/filename>$<.xml>,<.conf>,<.xml.bz2>$<registeradres>$<total ping>$<total fail ping>$<hubvote>|

So the hub can check how many times the ping has failed.