On Tue, 6 Aug 2013, Daniele Ricci wrote:
Please correct me if I'm wrong at any point, just to be sure I
understand XEP 198 and how I can use it in the right way.
On Tue, Aug 6, 2013 at 9:58 PM, Matthew Wild wrote:
On 6 August 2013 20:51, Daniele Ricci wrote:
Hi Kevin,
XEP 198 lets you ack
On Mon, 12 Jul 2010, Dave Cridland wrote:
I missed these.
On Mon Jun 7 18:16:54 2010, Matthew Wild wrote:
Having recently implemented an initial version of XEP-0198
acknowledgements support for Prosody, I have some feedback:
2) I'm not sure how much sense it makes for the period between ack
On Fri, 25 Jun 2010, Matthew Wild wrote:
On 25 June 2010 10:02, Dave Cridland wrote:
On Thu Jun 24 21:52:22 2010, Matthew Wild wrote:
On 24 June 2010 21:33, Justin Karneges
wrote:
It's a common problem to join a muc that already thinks you are joined,
and
then the presence you send is int
On Tue, 22 Jun 2010, Steven te Brinke wrote:
When I read XEP-0184, I thought about a few situations which are not
explicitly addressed in the XEP, so I did draw my own conclusions. It might be
desired to add (some of) these to the XEP explicitly. I leave that for someone
else to decide. I just
On Fri, 30 Apr 2010, Jonathan Schleifer wrote:
I only had a short look at it now in the bus, but after that short read,
it seems like my phone would ring every time I get a message, even
though there's another resource where I actually read the message?
Assuming your phone opted in to it (3.2
On Sat, 17 Apr 2010, Stephen Pendleton wrote:
My feeling is that XEP-0277 doesn't scale well, especially with PEP and
frequently reconnecting mobile clients in the mix. In particular the
rebroadcasting of messages (for example the replies to A that get
broadcasted to everyone subscribed to A no
tion. Mesh-based designs are
more resilient.
--
Bruce Campbell.
[1] He says, having suggested a new client protocol for private chats.