Home/ Questions/Q 108329
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T01:53:41+00:00

Recently, I’ve been reading up on the IRC protocol (RFCs 1459, 2810-2813), and I

  • 0

Recently, I’ve been reading up on the IRC protocol (RFCs 1459, 2810-2813), and I was thinking of implementing my own server.

I’m not necessarily looking into adhering religiously to the IRC protocol (I’m doing this for fun, after all), but one of the things I do like about it is that a network can consist of multiple servers transparently.

There are a number of things I don’t like about the protocol or the IRC specification. The first is that nicknames aren’t owned. While services like NickServ exist, they’re not part of the official protocol. On the other hand, implementing something like NickServ properly kind of defeats the purpose of distribution (i.e. there’d be one place where NickServ is running, and one data store for it).

I was hoping there’d be a way to manage nicknames on a per-server basis. The problem with this is that if you have two servers that have some registered nicknames, and they then link up, you can have collisions.

Is there a way to avoid this, without using one central data store? That is: is it possible to keep the servers loosely connected (such that they each exist as an independent entity, but can also connect to one another) and maintain uniqueness amongst nicknames?

I realize this question is vague, but I can’t think of a better way of wording it. I’m looking more for suggestions than I am for actual yes/no answers. So if anyone has any ideas as to how to accomplish nickname uniqueness in a network while still maintaining server independence, I’d be interested in hearing it. Note that adhering strictly to the IRC protocol isn’t at all necessary; I’ve got no problem changing things to suit my purposes. 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. There’s a simple solution if you don’t care about strictly implementing an IRC server, but rather implementing a distributed message system that’s like IRC, but not exactly IRC.

    The simple solution is to use nicknames in the form ‘nick@host’, much like email. So instead of merely being ‘mipadi’, my nickname could be ‘mipadi@free-memorys-server.net’. So I register with just your server, but when your server links up with others to form another a big ole’ chat network, you can easily union all the usernames together. There might be a ‘mipadi’ on otherserver.net, but then our nicknames become ‘mipadi@free-memorys-server.net’ and ‘mipadi@otherserver.net’, and everything is cool.

    Of course, this deviates a good deal from IRC. 🙂

    • 0