[IRCServices] Services Protocol for InspIRCd 1.2

[Robin Burchell]

It probably wouldn't take (much) modification.

The way we quick-converted our source base over was more or less:
  - Convert FindNick to find by UID if isdigit(*nick)
  - Store UID in the user structure (you'll need to generate/store for
pseudoclients too, though, I guess. Though that code isn't too
complicated.)
  - ???
  - Profit!

That said, it may be a little more complex with services, depending on
how many functions are hardwired to send with nickname instead of UID.
As I recall, Services keeps a lot of these in core - when it would be
better served relegating some of the heavy lifting of formatting
messages, etc, to protocol modules.

Still. We'll wait and see, I guess. :)

On Nov 12, 2007 10:46 AM, Andrew Church <achurch at achurch.org> wrote:
> Hmm.  This is certainly an interesting (and useful) feature, but it may
> be incompatible with the design of Services, which assumes (among other
> things) that prefixes and command targets are nicknames.  I'll give it
> some more thought when I have time, but I may not be able to support
> this.
>
>
>   --Andrew Church
>     achurch at achurch.org
>     http://achurch.org/
>
> >To clarify exactly what this does..
> >
> >Each server has a unique ID (e.g. 000), and each user additionally has
> >their own ID (e.g. AAAAAA). The two are combined to make a unique
> >identifier which is then used network-wide for all server to server
> >traffic.
> >
> >e.g.
> >
> >:000AAAAAA KILL 001AAAAAA :spammer! get off the network
> >
> >instead of
> >:Admin KILL spammer :spammer! get off my network.
> >
> >Another example is that instead of KILLing users on nick collision, we
> >may simply force them to their UID. A useful feature for services
> >authors will be to do the same instead of rolling their own guest
> >nicks.
> >
> >Further discussion on what this is and examples of problems it solves
> >can be found at http://www.inspircd.org/wiki/Development/UID
> >
> >On Nov 11, 2007 1:22 PM, Craig Edwards <brain at winbot.co.uk> wrote:
> >> Yes the 1.2 protocol is different to 1.1.
> >> The 1.2 release isnt even due for beta until at least the new year,
> >> there is no rush, however, please note that the 1.2 protocol uses UUID
> >> for identifying clients. This prevents a whole boatload of race
> >> conditions that plague irc, but makes it slightly difficult for services
> >> authors. A hash that associates uuids with nicks and servers would be
> >> required.
> >>
> >> Brain
> >>
> >>
> >> Casey wrote:
> >> > Hi Andrew
> >> >
> >> > I haven't got InspIRCd 1.2 - it is being worked on.
> >> >
> >> > I would have thought the protocol would need to be updated for 1.2
> >> >
> >> >
> >> > - Casey
> >> >
> >> >
> >> >
> >> > Andrew Church wrote:
> >> >>> Will the Services Protocol for InspIRCd 1.2 be coming soon?
> >> >>>
> >> >> Does the current protocol module not work with InspIRCd 1.2?  If not,
> >> >> I'll look into updating it.
> >> >>
> >> >>   --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
> >> >>
> >> > ------------------------------------------------------------------
> >> > To unsubscribe or change your subscription options, visit:
> >> > http://lists.ircservices.za.net/mailman/listinfo/ircservices
> >> ------------------------------------------------------------------
> >> To unsubscribe or change your subscription options, visit:
> >> http://lists.ircservices.za.net/mailman/listinfo/ircservices
> >>
> >------------------------------------------------------------------
> >To unsubscribe or change your subscription options, visit:
> >http://lists.ircservices.za.net/mailman/listinfo/ircservices
> ------------------------------------------------------------------
> To unsubscribe or change your subscription options, visit:
> http://lists.ircservices.za.net/mailman/listinfo/ircservices
>