Those vCards are *invalid* -- file bugs against those
clients. By allowing such problems to continue, we are
allowing the Jabber protocol to become like HTML -- and that
is my worst nightmare.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a server bug *and* a client bug. If a client sends
<vcard> (which it shouldn't do), the server will accept it
(which it shouldn't do), and remember it as <vcard>.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=9539
Those vCards are *invalid* -- file bugs against those
clients. By allowing such problems to continue, we are
allowing the Jabber protocol to become like HTML -- and that
is my worst nightmare.
Logged In: YES
user_id=410366
So, may this bug be treated as server bug? As far as I know
the server being requested for vCard can respond with VCARD.
Logged In: YES
user_id=9539
This is a server bug *and* a client bug. If a client sends
<vcard> (which it shouldn't do), the server will accept it
(which it shouldn't do), and remember it as <vcard>.