smakersThis seems like a bad idea. Moving an already-established system to a completely different network is a rough move on its own, but you're planning to move it to a brand new network that is untested and unproven, as well as that network's admins. You're also moving it to a network that is different from where other TF2 irc channels exist.
Basically, when the moves are completed, a person wanting to be in the pug channels and the scrim channel will have to connect to quakenet, join tf2mix and tf2scrim, then also connect to geeksirc to join pug.na. It's convoluted and messy, and offers nothing above what's already offered by gamesurge. Hiding your address is a simple process.
We know gamesurge isn't going anywhere. We know gamesurge admins aren't abusive and power-hungry, ready to dole out bans on a whim. We know that gamesurge admins aren't farming IPs that they can later abuse. We also know that blindtalent's anti-proxy bot sometimes generates false-positives. Right now, if there is a false positive, that user just needs to create a gamesurge account (which takes 5 minutes) to circumvent the ban. What will that process entail when the proxy bot is also an IRC admin and the users get banned from the entire network? Why does a channel admin need to see the IP of every user? This is a completely unnecessary power.
What about old players returning to TF2 who join gamesurge and realize the channels don't exist? Are you intending to leave a redirection bot in the old channel on the old network forever?
I get that you want the shiny new features as an admin, and IPs of users being hidden from other regular users is a good feature, but this is a step in the wrong direction that offers nothing else to the users except a hassle.
1) Fog is incorrect, channel founders (or any channel ops for that matter) can not see IP addresses. Only IRC Operators can see IPs.
2) The channels have decided that they want to move themselves, and they selected GeeksIRC so don't point your finger at me.
3) "What will that process entail when the proxy bot is also an IRC admin and the users get banned from the entire network?" I have no idea what you mean by this sentence, the bot does not exist on our network as it does not need it.
4) I plan on removing the redirect bot from #tf2.mix.nahl by the end of the week and just reset the topic.
5) I am already staff on GameSurge, so I really am not loosing much...
6) The network has been tested and proven, it just received a new name a few months ago.
7) If 80% of the channel want to move to GeeksIRC and #tf2mix and #tf2scrim want to go to quakenet, then that is their own prerogative.
8) The bot technically has no false positives as it checks through known dnsbl (black list) databases, and as soon as it detects it, it automatically kicks in. (I realize, some users don't know they are there but as you said I'd rather have them sign up for an account then remove the bot and have another botnet/spam attack)
9) When old players return they will just read the topic and move on, not a big deal and for most pug players it's simply just adding a new favorite in their browser.
10) tf2mix is moving because their system (atf2) does not work with GameSurge, so you don't need to blame me for that one.
The point is the network has been around for a while, it just received a new name and new servers. Believe it or not, but the TF2 community is not the only community on it so it's not like I created a glorified network for TF2.
From the SpamMaster8000 Bot Developer:
Spammaster8000 A.K.A AntiTOR-Bot - The bot was designed to remove spam users from the channel that were not registered with AuthServ. The bot could detect the users IP addresses because the GameSurge IRC network did not cloak non-registered users. Sometimes false positives can happen. The GeeksIRC network uses an IRC server daemon that has this functionality built in and will not allow the users to connect to the network to begin with. Basically this bot was designed specifically for GameSurge because of the lack of protection from spammers.
On another note, people that have connected to our network have NOT had an issue with our spam protection yet.