-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > You know the issue that when you enter a channel and a client is +o and > +v, and he deops himself, most clients will not show him moded at all > (the +v is not shown until you perform a /names <channel>). The issue is > located in the fact that ircu does not transmit both modes to the > client upon join. By sending both modes if they apply the client is > aware of them, and will show the client having both +vo as such, thus > when he deops himself the client is already aware of him being +v'd and > will correctly parse this. Patches tested with all major IRC clients and > turned out to be ok, not breaking the clients in any way. >
I've spoken to client authors about a similar patch and they are all very enthusastic, however this does break some clients. When you've got a network the size of undernet, you've got to be careful before you deliberately break RFC compatability. Undernet's helping out getting protocol negotiation working with other networks and client coders, when the protocol negotiation is accepted, the first "negotiation" that has been requested by clients is changing it from: @foo +bah baz to: @+foo!~[EMAIL PROTECTED] +bah!~[EMAIL PROTECTED] [EMAIL PROTECTED] so they don't have to refresh the IAL on join either. Of course, this involves people organising to get the protocol negotiation standardised. - -- My computer can beat up your computer. - Karl Lehenbauer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: Only when you are sure they have you, can you stop being paranoid iD8DBQE9sfRQcAgRpy8z8UQRAjnpAKDe51GjZ3q6F7Qf3dFOr+RKA6TunwCdGiJO FvDrhstPDspzvWA40wImU6s= =b60O -----END PGP SIGNATURE-----
