-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Thijs,
On 04.03.2014 11:36, Thijs Alkemade wrote: > On 4 mrt. 2014, at 10:24, Lars Noschinski > <[email protected] >>> Legend e: empty l: local (client) jid bl: bare local jid dl: >>> domainpart of local jid s: server jid o: other jid > The changes to Pidgin were proposed for the situations where to=e > and from=l/dl/s, because those are used by a number of (broken) > servers out there. I have not seen it necessary to look at the > other possiblities in your table, I agree that your choices for Pidgin look sensible. > except for to=l from=e, which is empty in your table, but should be > allowed (I've submitted a new patch to Pidgin for this, but it > hasn't been accepted yet). Do you mean l or bl here? From your rule below, I guess you meant bl? Have you seen this combination in the wild? Or is this an instance of 'be liberal in what you receive'? > So I think it makes sense to add the rule: "if you do use an > explicit JID, that's not your own bare JID, the reply must match > exactly". -- Lars -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJTFbQ9AAoJEOUX5T7UhMS6sjAIAIjb8p7EYtT5vhbDNEARhj2J PCzUTw1qORjVg4wZ6fM4sBQCC0u7F/A503XwLjPlNQZcGmphS6lR6/3IRxnI6PFp navWTNF68gE39YVGcmPtgZ+9KqyC4SFM94eOeWLg/Cv+Pr2Nj6WL8mtHfrGv99/6 63lBY+RJUJT3nVIHlZyD5ETW7NQPg/EiGvXsDxhtTAZxwRK8lT7+kinZMST+GwVV sbRjnlvrciZazQAvOmA1KVjT49759XKMuwAouNGRbiQZ1kxLos731xq2wHmfVu55 8Zo6WXAnPMDKElxJSLywjfWz61Rg2jTSJ2ZDezcJ6hWmewCWoWklLliG4DGq/hE= =OJij -----END PGP SIGNATURE----- _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
