On Thursday, January 15, 2015 06:56 EST, Dave Cridland d...@cridland.net
wrote:
So there's the player's login name - jid - and a character name. I
understand what you've written to mean there's only one active character
(though there may be multiple characters).
Correct.
Well, you can
On 14 January 2015 at 05:57, David Bolack dbol...@missingworldsmedia.com
wrote:
On Monday, January 12, 2015 03:14 EST, Dave Cridland d...@cridland.net
wrote:
In general, proposing a XEP that's rejected because it's a terrible idea
adds more value than doing something that's a terrible
is appropriate.
In my experience it's worth writing a simple standards document like an XEP
even if you plan to keep it proprietary. The documentation exercise makes
your idea more robust and your implementation more straight forward.
In short, it's always appropriate to write a spec. The worst
On Monday, January 12, 2015 03:14 EST, Dave Cridland d...@cridland.net wrote:
In general, proposing a XEP that's rejected because it's a terrible idea
adds more value than doing something that's a terrible idea without
discussing it. Even if you choose not to go as far as a formal protoXEP,
I am working on a project where we want to use the resource id as a secondary
authentication field and force the use of that value for muc nicknames.
While we expect most users will use our clients, we'd like to document things
so folks who prefer their client and can set the resource id to be
Lauri Kaila wrote:
2007/12/1, Peter Saint-Andre [EMAIL PROTECTED]:
(1) XEP-0155 and XEP-0168 are not normative dependencies in XEP-0166,
and we mention them only to help implementors. However, I think it would
be best to move those references to XEP-0208. I am also open to delaying
the
2007/12/1, Peter Saint-Andre [EMAIL PROTECTED]:
(1) XEP-0155 and XEP-0168 are not normative dependencies in XEP-0166,
and we mention them only to help implementors. However, I think it would
be best to move those references to XEP-0208. I am also open to delaying
the advancement of XEP-0208
Currently the core Jingle spec (XEP-0166) refers to both XEP-0155
(Stanza Session Negotiation) and XEP-0168 (Resource Application
Priority). The context is describing how to determine which resource to
communicate with when starting a Jingle session. I had a chat about this
with Robert McQueen the
