Jonathan Schleifer wrote: > Am 02.10.2008 um 13:36 schrieb Pedro Melo: > >> small clients that are willing to implement Jingle + E2E but can't >> afford to implement any of the ping/ack XEPs out there? > > The problem is that they *DON'T* (and I already said that before) > implement Jingle + E2E, thus can't warn the receiver of a message that > was unable to decrypt, because it's not supported!
Even if the new client supports it, it will fail because a secure session is between clients, not users. But still, I do not get why you want to notify the receiver. You wrote you saw the following message: [This is part of an encrypted session. If you see this message, something went wrong.]. Now what? What can you do? Nothing except sending a message to the sender that something is wrong and you can not read the message. Well, the sender already knows that. Dirk -- System going down at 1:45 this afternoon for disk crashing.
