>> Therefor deprecating/obsoleting XEP-0184 seems like a very bad idea to
>> me, I'd rather remove the received/acknowledged feature from XEP-0333
>> and rename it to read markers (which is the only part most implement
>> anyway) so we don't have an overlap in features and people stop claiming
>>
On Wed, 4 Mar 2020 at 11:45, Marvin W wrote:
> XEP-0184 is doing one job, that is to notify the sender when a message
> was delivered to the recipient's client. That's literally what the title
> is. While in setups with MAM and SM, far less messages get lost, the
> pure specification of XMPP
ср, 4 мар. 2020 г. в 16:46, Marvin W :
> In contrast XEP-0333 serves a mostly different purpose: it notifies the
> sender only of the last received/displayed/acknowledged message.
And that is the right way to do it. In the decades of using XMPP
intensely I have probably had a dozen of incidents
At the risk of AOLing, I think I agree with pretty much everything Marvin says
here.
/K
> On 4 Mar 2020, at 11:45, Marvin W wrote:
>
> XEP-0184 is doing one job, that is to notify the sender when a message
> was delivered to the recipient's client. That's literally what the title
> is. While
XEP-0184 is doing one job, that is to notify the sender when a message
was delivered to the recipient's client. That's literally what the title
is. While in setups with MAM and SM, far less messages get lost, the
pure specification of XMPP does not guarantee every message to be
delivered to the
