The only issue I can foresee with this approach is if you have 3 messages,
Initial Message, Corrected Message and Other Message, you could
potential only fetch Initial Message and Other Message and the client
would not know that Initial Message had been subsequently corrected.
Maybe this isn't
Hi,
On 17 May 2013 20:49, Spencer MacDonald
spencer.macdonald.ot...@gmail.com wrote:
One of the features from XEP-0136 that I would like to see included in
XEP-0313 is message removal.
Would it be possible to include this?
Without saying yes or no... I'll just ask, what's the actual use
No problem, I can understand your concerns as XEP-0136 is very bloated and
complicated.
Simply if you say something that is incorrect or in the wrong chat then you
will want to delete it.
Also you may say something that is confidential that you might want to
remove after the recipient has
On Sat, 18 May 2013, 14:23:43 CEST, Spencer MacDonald
spencer.macdonald.ot...@gmail.com wrote:
Also you may say something that is confidential that you might want to
remove after the recipient has acknowledged it.
You really want to use some end-to-end encryption for that.
Carbons (XEP-280)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/18/13 6:23 AM, Spencer MacDonald wrote:
No problem, I can understand your concerns as XEP-0136 is very
bloated and complicated.
Simply if you say something that is incorrect or in the wrong chat
then you will want to delete it.
Also you
On 18 May 2013 14:33, Kim Alvefur z...@zash.se wrote:
On Sat, 18 May 2013, 14:23:43 CEST, Spencer MacDonald
spencer.macdonald.ot...@gmail.com wrote:
Also you may say something that is confidential that you might want to
remove after the recipient has acknowledged it.
You really want to use
One of the features from XEP-0136 that I would like to see included in
XEP-0313 is message removal.
It could follow the same logic as message retrieval, just instead of
query it would be remove and be of type set:
iq type='set' id='remove1'
remove xmlns='urn:xmpp:mam:tmp'
