Joe Hildebrand wrote:
On Jul 29, 2008, at 8:23 AM, Peter Saint-Andre wrote:
Dirk Meyer wrote:
Only client but IIRC adding a friend to the roster resulted in
getting
an iq result without sending a get or set. Very confusing.
So you sent presence type='subscribe'/ and you received an IQ
This may be of interest here. We've talked before about producing
implementation reports regarding the XMPP RFCs (for advancement to Draft
Standard) and also for XEPs (for advancement from Draft to Final). We
could use a lightweight format like this for such reports.
/psa
Original
Pavel Simerda wrote:
On Sat, 02 Aug 2008 21:40:49 +0200
Maciek Niedzielski [EMAIL PROTECTED] wrote:
Jehan wrote:
But still for most end users, the best is wysiwyg
And this is why xhtml-im needs to be about formatting, not semantics:
most end users want to get (and send) what they see. And
Jonathan Schleifer wrote:
Hi!
I'm a Gajim developer and we have implemented ESessions. However, as
we're currently the only XMPP client to my knowledge implementing it
and the XEP is currently deferred, we plan to make a few changes and
like to get them back in the XEP.
We talk some about
Pedro Melo wrote:
On Jul 22, 2008, at 2:12 AM, Ovidiu Craciun wrote:
Excerpt from:
http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-06.html
Section: 8.3. Generation of Resource Identifiers
A resource identifier can be security-critical. For example, if a
malicious entity
Pedro Melo wrote:
On Jul 31, 2008, at 5:21 PM, Dave Cridland wrote:
On Thu Jul 31 17:17:40 2008, Pedro Melo wrote:
Moving forward, this would allow clever clients to observe that it
wasn't a IM client capable of handling calendaring requests, but a
dumb calendaring bot working on behalf
Olivier Goffart wrote:
I'm about off topic here, but since you mention this spec i'd like to add my
two cent.
It would be cool to add a way to specify a new jid, so the server could reply
with a gone/ error with the new Jid
or even forward message to the new one.
What prevents a malicious
Hi Gato,
Thanks for the feedback. It seems that I will need to poke other
developers directly. :)
/psa
Gaston Dombiak wrote:
Hey Peter,
Openfire uses the SASL support provided by Java. That means that SASL PLAIN,
DIGEST-MD5, GSSAPI, etc. are provided by Java. The only SASL mechanisms that
Ahoj Pavle,
That all sounds good. Now we just need to update the spec (which the
Council is currently voting on!). I'll try to do that soon.
Peter
Pavel Simerda wrote:
On Thu, 31 Jul 2008 08:07:04 -0600
Peter Saint-Andre [EMAIL PROTECTED] wrote:
Pavel Simerda wrote:
On Wed, 30 Jul 2008
