Re: Cleaning up rcirc

[Philip Kaludercic]

Tassilo Horn <tsdh@gnu.org> writes:

>> A few IRCv3 specs have already been implemented, as listed in the new
>> option rcirc-implemented-capabilities. I plan to add these sooner or
>> later:
>>
>> - https://ircv3.net/specs/extensions/account-notify
>> - https://ircv3.net/specs/extensions/account-tag
>> - https://ircv3.net/specs/extensions/extended-join
>> - https://ircv3.net/specs/extensions/away-notify
>> - https://ircv3.net/specs/extensions/echo-message
>> - https://ircv3.net/specs/extensions/labeled-response
>> - https://ircv3.net/specs/extensions/multiline
>> - https://ircv3.net/specs/extensions/sasl-3.1
>>
>> and
>>
>> - https://ircv3.net/specs/client-tags/reply
>> - https://ircv3.net/specs/client-tags/react
>> - https://ircv3.net/specs/extensions/chathistory
>
> I'm afraid I'm not a very knowledgeable IRC user.  I know how to chat,
> /msg, /join, and /part, or how to identify to NickServ.  That's about
> it.  So I can report back if something very basic breaks but if you
> would like me to test some more advanced things, you have to guide me a
> bit.

I'm not sure if that will happen without a bouncer, but rcirc-print
tries to order the messages by the server-time, and I've noticed edge
cases where the messages don't appear in the right order. But other than
that, I hope that I didn't break any of the basic stuff.

> Bye,
> Tassilo

-- 
        Philip K.