Weedy
2014-05-11 05:28:04 UTC
I just finished up with a wonderful experience where
card.freenode.netbecame a steaming pile of crap.
I'm not really active on freenode as of late so I didn't notice how many
time or how often I was lagging out, By the time I fixed the problem I was
banned from almost every channel on the network.
Two things:
1. Why doesn't /reconnect have a -next or -cycle?
2. Why aren't there any heuristics for server where if I'm dropped X times
in a hour it's probably a bad server and we need to try another. Or at
least every say 3 reconnects try another server.
Thank you for your time.
card.freenode.netbecame a steaming pile of crap.
I'm not really active on freenode as of late so I didn't notice how many
time or how often I was lagging out, By the time I fixed the problem I was
banned from almost every channel on the network.
Two things:
1. Why doesn't /reconnect have a -next or -cycle?
2. Why aren't there any heuristics for server where if I'm dropped X times
in a hour it's probably a bad server and we need to try another. Or at
least every say 3 reconnects try another server.
Thank you for your time.