[IRCServices Coding] send_cmd in non-protocol modules

Craig Edwards brain at winbot.co.uk
Tue May 10 05:03:35 PDT 2005


nobody pays any attention to them because a lot of it was unfortunately 
IRCNet specific. What makes it worse is that now IRCNet is throwing 
their own specs in the bin (without writing new ones i might add to take 
their place) -- for example did you know the pipe character ("|") is now 
ILLEGAL in nicknames on ircnet? - it's a new feature of their ircd2.x 
line. They took it *out* of the BNF for allowed nicknames, i'm not just 
referring to a Q line! Not just this but there have been many other 
changes 'in the name of compatibility'. Compatibility? pffft.

Brain

Andrew Church wrote:
>      That would certainly be preferable, but so far nobody seems to have
> done that (nor do the ircd developers seem very interested in working
> together on creating such a document).
> 
>      Actually, that's not quite accurate, since RFCs 2810-2813 were
> published at one point, but nobody seems to be paying attention to them...
> 
>   --Andrew Church
>     achurch at achurch.org
>     http://achurch.org/
> 
> 
>>	Would it not therefore seem more logical to update or create new RFCs pertaining to IRC, instead of having to customize Services each time another non-RFC-compliant IRCd implements a 'desireable' feature?  I'm no software developer, but if I were, I wouldn't consider it unreasonable to set out some guidelines within whose confines I'd prefer to remain.
>>	That being said, if IRCServices continues to implement a number of ad-hoc modifications which don't follow an RFC, what happens if/when a new RFC *is* written which serves to address the aforementioned ad-hoc changes?  More work for the developers, from what I can tell, to ensure their previously implemented workarounds meet the newly released standards.
>>
>>David
>>
>>
>>On 07/05/2005 at 11:01 PM Craig Edwards wrote:
>>
>>
>>>IRC is changing. It has been changing since day one, the software which 
>>>is used for IRC must change with it. IRCServices is being left behind by 
>>>other software which *does* tolerate changes to the spec, and it saddens 
>>>me to see software i love becoming deprecated because of it :-(
>>>
>>>I'm sure there are many IRCu users out there who would disagree with 
>>>your opinion, and as it stands ircservices simply cannot support them, 
>>>even though it is one of the most popular IRCds. I'd say this ircd has 
>>>more problems than mine as mine is tolerant to 'assumptions' and will 
>>>rewrite the RFC commands to something it understands -- IRCu (P10) will 
>>>not ;-)
>>>
>>>Brain
>>>
>>>Andrew Church wrote:
>>>
>>>>>IRCServices 5 has protocol modules which allow it to connect to many 
>>>>>different kinds of ircds easily. Great idea. However, the core blatantly 
>>>>>uses send_cmd, and makes assumptions about the format of specific 
>>>>>commands,
>>>>
>>>>
>>>>     This is by design.  The only reason for protocol modules in the
>>>
>>>first
>>>
>>>>place is to kludge around variations in what ought to be a standard.  If
>>>>you have an ircd that's so bizarre it can't even understand a NOTICE
>>>>message, then Services won't support it.  Sorry, but I don't have the
>>>
>>>time
>>>
>>>>or interest to deal with such software.
>>>>
>>>>  --Andrew Church
>>>>    achurch at achurch.org
>>>>    http://achurch.org/
>>>>------------------------------------------------------------------
>>>>To unsubscribe or change your subscription options, visit:
>>>>http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
>>>>
>>>>
>>>
>>>-- 
>>>WinBot IRC client developer: http://www.winbot.co.uk
>>>ChatSpike - The users network: http://www.chatspike.net
>>>InspIRCd - Modular IRC server: http://www.inspircd.org
>>>Online RPG Developer: http://www.ssod.org
>>>--
>>>------------------------------------------------------------------
>>>To unsubscribe or change your subscription options, visit:
>>>http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
>>
>>
>>
>>------------------------------------------------------------------
>>To unsubscribe or change your subscription options, visit:
>>http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
> 
> ------------------------------------------------------------------
> To unsubscribe or change your subscription options, visit:
> http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
> 
> 

-- 
WinBot IRC client developer: http://www.winbot.co.uk
ChatSpike - The users network: http://www.chatspike.net
InspIRCd - Modular IRC server: http://www.inspircd.org
Online RPG Developer: http://www.ssod.org
--