Re: BOPM CTCP VERSION Patch
tabris <[email protected]>
| Newsgroups | gmane.network.irc.bopm |
|---|---|
| Message-ID | <[email protected]> |
On Saturday 05 March 2005 10:28 am, nv wrote: > Hello, > I have been going through the BOPM Mailing list and found out there > is a CTCP Version Patch which CTCP the clients when connect and > match/kline them. I couldn't find the patch anywhere...Any Idea where > I can find it? I'd think you'd be better off just having something like NeoStats SecureServ. or Unreal's SpamFilter (you still have to send a CTCP request). Or just code your own regexp bot in Perl. a socketbot coded in perl isn't too hard to do really. and it'll be a) easier to test b) easier to code. I have a feeling that this kind of thing might qualify as freeping creaturism. When I go on a service call I don't normally bring a combination blowtorch/screwdriver/knife/pliers/coping-saw. Just the screwdriver and pliers will be fine, and if I need the blowtorch I'll get it from my vehicle ;). Simplicity is the UNIX way. Maybe what we need (I have a developer/friend who would agree even) is an extensible framework, like NeoStats (tho I'd prefer something better), that you can insert various kinds of modules into. Thus you have both simplicity (modular) while not 20 separate bots either, as some ppl seem to want. I'd suggest SurrealServices core-code but it's in perl which not everyone would appreciate. Hopefully we'll have time to make a C version, later. If anyone DOES want to see SurrealServices, I'll reply with a link. > > http://lists.blitzed.org/pipermail/bopm/2003-February/000976.html > http://lists.blitzed.org/pipermail/bopm/2003-February/000975.html > > Thanks -- "There are three principal ways to lose money: wine, women, and engineers. While the first two are more pleasant, the third is by far the more certain." -- Baron Rothschild, ca. 1800
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBCKfaNgbFCivvqDfQRApbTAJ0QwwMXt3L+QBa6J+oTEBpMvehzEwCgoZiw +3AAdSMUz7jcBxL9qgi4t/0= =1HXG -----END PGP SIGNATURE-----