[JDEV] IRC?

temas temas at box5.net
Tue Dec 21 11:27:56 CST 1999


I know that TC answered this differently from what I'm about to say, but we
have discussed two versions of irc.  An irc service and an irc transport.  One
would just act like TC was explaining allowing a one to one user usage of irc
through the jabber server.  The other would be a server implementation, and yes
we would have to create different ones for the different networks, but we feel
this will not be a large issue if they become more widely accepted.  The actual
ircd developers may find it in there interest to jabberify there server to allow
it to work.  There's the current thoughts.

--temas

Jukka Tapani Santala [e75644 at UWasa.Fi] wrote:
> On Tue, 21 Dec 1999 Isotope2k at aol.com wrote:
> > I had very similar questions... 
> > Check out RFC1459, there seems to be a concensus that an IRC
> > transport implementation would be fairly straightforward.
> 
> Careful - the RFC, which isn't on standards track, and never can be - is
> pretty old and outdated. Not neccessarily anything that'd cause an
> immediate problem, but bad enough. Especially as the actual server-server
> communication on IRC is basically properietary to each network (There's
> some major development lines - Hybrid/Bahamut, Dreamforge, Undernet to
> name a few) and I can't see an useful "interface"(*) to IRC without making
> a pseudo-server for the purpose. Getting such a server dropped into any
> major network would be harder than ugly.
> 
> (*) Or would a transport just span a million and one separate connections
> to attack a poor, hapless IRC server..? Can you say... clone-kills!
> Mass-bans! ;)
> 
>  -Donwulff
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/19991221/b1be8bce/attachment-0002.pgp>


More information about the JDev mailing list