Hello!
Philipp Hancke пишет:
Am 02.07.2016 um 18:19 schrieb Константин Козлов:
Hello!
There's something, I still cannot understand in XEP-0167. I tried to ask
in both j...@conference.jabber.org and x...@muc.xmpp.org but got no
answer so far.
XEP-0167 chapter 5 says about *session-initiate* re
Version 1.1.1 of XEP-0167 (Jingle RTP Sessions) has been released.
Abstract: This specification defines a Jingle application type for negotiating
one or more sessions that use the Real-time Transport Protocol (RTP) to
exchange media such as voice or video. The application type includes a
straig
Hello,
We needed to have a working solution to support easily MUC on mobile today,
so we made the simple possible change on MUC to support that. It basically
allow users to become MUC subscribers. No need to send presence to room to
receive messages.
We described it there:
https://blog.process-on
Hello Vaibhav
There are various extensions that can be used together with In-band
registration to make it more secure.
One way, it to secure it using CAPTCHA, as outlined in XEP-0158:
http://xmpp.org/extensions/xep-0158.html. This method tries to seed out bots by
assuring a human user creates
Hi All,
I realised the subject was not in the correct format for the email I sent
in the morning. Please ignore that email.
I am a newbie software developer who recently started looking into XMPP
XEP's. In Band registration was something that caught my eye, as the XEP
itself said that it is utter
On 7 Jul 2016, at 11:00, Dave Cridland wrote:
>
> Folks,
>
> XEP-0313 §4 says:
>
> "The final response MUST include an RSM element indicating
> the UID of the first and last message of the (possibly limited) result set."
>
> This seems plausible, but looks like a hangover from the marker me
