Anope IRC Services

Anope Development => Feature Requests => Topic started by: Slutwig on February 22, 2007, 09:02:28 PM

Title: Vhost improvement
Post by: Slutwig on February 22, 2007, 09:02:28 PM: Well, basicly, i'm looking for a module (or something else) which will do what i do manually.

Automatically gives vhost like <ident>@regnick.rank.network.net

Where the regnick is the reg nick of the user.

This will be nice to have this at the IDENTIFY command.

IRCops could choose different group for user as rank.

Lambda user gets user, and upon levels or other, get mod, op or whatever the ircop choose.

I don't really know how this could be done, finally this a usefull tool in srvx.

Thanks.
Title:
Post by: owine on February 22, 2007, 10:19:34 PM: There is a module called hs_nethost which will set the HostServ host of newly registered nicks to <nick>.user.network.tld. The Srvx implementation only allows you to customize the part before the network name if I remember correctly. Anope's implementation of vHosts allows full customization. IRCops can just set the updated host mask as opposed to just setting a rank/group.
Title:
Post by: rassi on February 22, 2007, 10:37:12 PM: Look this link -> http://forum.anope.org/viewthread.php?tid=789#pid4393
Title:
Post by: Slutwig on February 22, 2007, 10:52:08 PM: Thanks for your answers.

hs_nethost will suit my needs, but how can I be sure that this will run on 1.7.18 ...

I could try anyway ...
Title:
Post by: Slutwig on February 22, 2007, 11:32:22 PM: well, http://www.anope.org/modules/hs_autohost.c , this one is working but how to define groups ... that's another story :)
Title:
Post by: Jan Milants on February 23, 2007, 12:13:36 AM: hs_nethost works fine too on 1.7.18... use it on my net
Title:
Post by: n00bie on February 23, 2007, 01:30:25 PM: well, the main flaw of this module is that when users having/using a nick with special chars example: My^Example|Nick registered a nick on the network, it cannot automatically sets a vhost for them because it contains special chars. Other than that, it is good ^^
Title:
Post by: katsklaw on February 23, 2007, 10:10:29 PM: This type of hostmasking also creates other problems, such as banning users with clients/scripts that automaticlly choose ban mask types since they are dynamic. Since it's a hostname, a dynamic ban using the very popular banmask type 3, which is *!*users@*.host.tld, will affect ALL the users in your channel that have your *.users.network.tld type mask. Even Anope uses ban mask types for dynamic bans.

IMHO this type of hostmangling is a very nasty hack. Conventional hosts as used by HostServ and the more popular hostmasking is a better option as far as that goes and alot of users prefer to custom hostmasks anyway.
Title:
Post by: sapphire on August 02, 2007, 09:05:36 PM: couldn't this be done by the user if you use a module that provides a #vhost channel? It would seem like that could help fix the problem katsklaw mentioned :)