dax 2017-02-28 19:45:27
i don't care whose bots it was, and your insistence on caring makes you tedious
amnet 2017-02-28 19:45:30
That's fine, but it doesn't help solve the problem.
amnet 2017-02-28 19:45:33
Ban the bots.
rizon30 2017-02-28 19:45:37
dax i said only once
dax 2017-02-28 19:45:45
so you can't count either then, gotcha
amnet 2017-02-28 19:45:46
Their commander is irrelevant until they connect to the network.
dax 2017-02-28 19:45:49
anything else while you're here
rizon30 2017-02-28 19:45:55
who said i was trying to help solve the problem
rizon30 2017-02-28 19:46:21
i was simply saying
amnet 2017-02-28 19:46:26
If you're not trying to help then you're just being an ass.
rizon30 2017-02-28 19:46:31
lol
amnet 2017-02-28 19:46:39
Nobody needs to care about this after the bots are banned.
rizon30 2017-02-28 19:46:42
you can simply state something without being an ass
dax 2017-02-28 19:46:49
yawn
dax 2017-02-28 20:01:25
Rage_Banken: looking, sec
dax 2017-02-28 20:02:05
Rage_Banken: done, it's active now and will activate on future connections when you identify to NickServ
dax 2017-02-28 20:04:08
Rage_Banken: you don't really "do anything" with cloaks, they just change your hostname
dax 2017-02-28 20:04:20
so yours is now "unaffiliated/rage-banken/x-2555762"
dax 2017-02-28 20:04:47
and when you log into your NickServ account on future connections it'll change it to that again
dax 2017-02-28 20:04:51
Rage_Banken: no worries
dax 2017-02-28 20:06:23
Rage_Banken: if you have the ability to change the PTR record for your current IP address, then you'd set that to your domain and set an A record on your domain to your current IP address
dax 2017-02-28 20:06:25
otherwise, no
dax 2017-02-28 20:06:53
http://freenode.net/kb/answer/cloaks lists cloaking format, it's basically unaffiliated/nickhere unless you have some sort of peer-directed project affiliation and they request one for you
dax 2017-02-28 20:08:27
:)
dax 2017-02-28 20:14:36
RuGaL: hi
dax 2017-02-28 20:15:01
RuGaL: generally 10 weeks of inactivity, with some exceptions
dax 2017-02-28 20:16:07
RuGaL: Yep. If you /nick to it I can drop it so you can group it, if that's what you're wanting
dax 2017-02-28 20:18:34
RuGaL: /nick to it
dax 2017-02-28 20:19:24
RuGaL: change your nick to it and I will drop it for you. I cannot drop it if you are not on it
dax 2017-02-28 20:19:59
yes
dax 2017-02-28 20:20:28
Fahad: good. now do /msg nickserv group
dax 2017-02-28 20:21:03
Fahad: all done, you now have both Fahad and RuGaL on the same account :)
dax 2017-02-28 20:21:38
Fahad: yes
dax 2017-02-28 20:24:19
brimonk: WHOIS with one parameter (local whois) does not have a limit. WHOIS with two parameters (remote whois, which talks to the server the target user is on) is rate-limited server-wide (not per-user) and if you're programmatically using it you should detect and handle rate limiting failures
dax 2017-02-28 20:24:41
brimonk: and to clarify/emphasize: the rate limit there is not on how often your bot uses it, it's on how often any user on the server the bot is on uses it
dax 2017-02-28 20:24:56
hi starrify
dax 2017-02-28 20:31:44
starrify: yes
dax 2017-02-28 20:31:59
starrify: idle time is kept track of by the server that the target user is on. so if you're on the same server, local whois will get it. if not, remote whois is needed
