[Standards] Proposed XMPP Extension: Mediated Information eXchange (MIX)

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Mediated Information eXchange (MIX) Abstract: This document defines Mediated Information eXchange (MIX), an XMPP protocol extension for the exchange of information among multiple participants through a mediating service.

Re: [Standards] UPDATED: XEP-0071 (XHTML-IM)

Le mardi 5 janvier 2016, 16:10:56 Sam Whited a écrit : > On Tue, Jan 5, 2016 at 4:03 PM, Goffi wrote: > > The diff page don't seems to work for me (iceweasel or chromium), am I the > > only one ? I see no diff highlighted, just the full XEP, and left/right > > arrow don't work. >

[Standards] XEP-0313: why it is *really* not a good idea to use MAM with Pubsub

G'day, MAM is a great tool which solves several problems for messages management. It also offers the ability to get items from a PubSub node when the "node" attribute is used. We have implemented this feature in our PubSub/PEP component, and I haven't seen any other implementation for PubSub

Re: [Standards] Markdown in XMPP IM

On 06.01.2016 14:08, Matthew Wild wrote: > On 6 January 2016 at 13:00, Peter Waher wrote: >> Hello Travis, Steven, Goffi, Andreas & others >> >> Thanks for your input. My responses below: >> >>> Isn't the point of markdown that it's perfectly readable as plain text, >>> ie

[Standards] OX (OpenPGP for XMPP): A new OpenPGP XEP

Hello everyone, Joachim and I met many interesting people at the GSoC Mentor Summit 2015. Amongst those where the developers of OpenKeychain, an OpenPGP provider for Android: Dominik and Vincent. We soon got into a discussion about the current state of OpenPGP in XMPP. For those of you unaware:

Re: [Standards] Markdown in XMPP IM

On 01/06/2016 08:00 AM, Peter Waher wrote: > Sending markdown encoded as markdown has several benefits. But also many downsides, there is not really such a thing as a markdown standard. There are different 'flavors', such as github-flavored-markdown, and then there are just major/minor

Re: [Standards] Markdown in XMPP IM

Hello Matthew, Florian & others Thanks for your input. Regarding your comments: > >> Isn't the point of markdown that it's perfectly readable as plain text, > >> ie that there is no markup? I'd think sending straight markdown would > >> be just fine. > > > > The point of markdown is that it's

Re: [Standards] Markdown in XMPP IM

Hello Travis, Steven, Goffi, Andreas & others Thanks for your input. My responses below: > Isn't the point of markdown that it's perfectly readable as plain text, > ie that there is no markup? I'd think sending straight markdown would > be just fine. The point of markdown is that it's easy

Re: [Standards] XEP-0313: why it is *really* not a good idea to use MAM with Pubsub

Hello, I think it is a good idea for there to be a search extension for pubsub. One thing to keep in mind would be is that the extension could become really complicated depending on the search fields that you are going to have and the type of filter you want. If there are user defined fields,

Re: [Standards] Markdown in XMPP IM

On 6 January 2016 at 13:00, Peter Waher wrote: > Hello Travis, Steven, Goffi, Andreas & others > > Thanks for your input. My responses below: > >> Isn't the point of markdown that it's perfectly readable as plain text, >> ie that there is no markup? I'd think sending

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

> On 30.12.2015, at 22:48, Lance Stout wrote: > > The prose has the original but the example shows > . > > > Aside from that nit, I'm +1 on publishing this version. Same goes for me. Also +1 on publishing. Cheers, Tobias

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

On 6 January 2016 at 15:38, Philipp Hancke wrote: > before publication What? Why on earth do we want to make changes before publication as a XEP? Prior to publication as a XEP, this is not an XSF document. After, we discuss it, make changes, and so on. I can

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

Am 06.01.2016 um 17:00 schrieb Dave Cridland: On 6 January 2016 at 15:38, Philipp Hancke wrote: before publication What? Why on earth do we want to make changes before publication as a XEP? wouldn't such a change to the schema need a namespace bump?

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

Am 06.01.2016 um 17:15 schrieb Dave Cridland: On 6 January 2016 at 16:13, Philipp Hancke wrote: Am 06.01.2016 um 17:00 schrieb Dave Cridland: On 6 January 2016 at 15:38, Philipp Hancke wrote: before publication What? Why on earth

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

and my +1 also. On 6 January 2016 at 14:33, Tobias M wrote: > > On 30.12.2015, at 22:48, Lance Stout wrote: > > The prose has the original but the example shows > . > > > Aside from that nit, I'm +1 on publishing this version. > > > Same goes for

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

Am 17.12.2015 um 11:50 schrieb XMPP Extensions Editor: The XMPP Extensions Editor has received a proposal for a new XEP. Title: Jingle ICE Transport Method Abstract: This specification defines a Jingle transport method that results in sending media data using datagram associations via the

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

On 6 January 2016 at 16:13, Philipp Hancke wrote: > Am 06.01.2016 um 17:00 schrieb Dave Cridland: > >> On 6 January 2016 at 15:38, Philipp Hancke >> wrote: >> >> before publication >>> >> >> >> What? >> >> Why on earth do we want to make

Re: [Standards] Markdown in XMPP IM

> On 6 Jan 2016, at 16:28, Goffi wrote: > > Le mercredi 6 janvier 2016, 15:29:31 Peter Waher a écrit : > >>> Alternatively, if it's just about easier input, support Markdown on >>> the sending side and use XHTML-IM. I don't think we really need more >>> ways of formatting

Re: [Standards] Markdown in XMPP IM

> On 6 Jan 2016, at 16:28, Goffi wrote: > > Le mercredi 6 janvier 2016, 15:29:31 Peter Waher a écrit : > >>> Alternatively, if it's just about easier input, support Markdown on >>> the sending side and use XHTML-IM. I don't think we really need more >>> ways of formatting

Re: [Standards] Markdown in XMPP IM

On 01/06/2016 12:53 PM, Ashley Ward wrote: > text/x-markdown Except markdown means nothing, there is no standard, and no common implementation. I love markdown, but just because your markdown converts with your tool to a format you want, doesn't mean anyone else can get that same output with any

Re: [Standards] Markdown in XMPP IM

Restructured text is a more standard format similar to markdown. I believe it started with python function documentation. http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html -- Tory > On Wed Jan 6, 2016, at 11:04 , Travis Burtrum wrote: > > On

[Standards] XMPP client certificates for SASL EXTERNAL

Hello, Could anybody send me a few X.509v3 certificates of XMPP clients that can be used for SASL authentication. I am looking for certs that satisfy the cases presented in XEP-0178, page 3: a) If the client certificate contains only one JID, then the client MAY include an authorization

Re: [Standards] XMPP client certificates for SASL EXTERNAL

Wed, 6 Jan 2016 13:28:54 -0500 "Emil Romascanu" wrote: > Hello, > > Could anybody send me a few X.509v3 certificates of XMPP clients that > can be used for SASL authentication. I am looking for certs that > satisfy the cases presented in XEP-0178, page 3:

Re: [Standards] XMPP client certificates for SASL EXTERNAL

Hi Evgeny, If I click the link you gave me: http://www.zinid.ru/cert.pem, I get a text box with the following message: "This is not a certificate authority certificate, so it can't be imported into the certificate authority list"/ Thank you, Emil Romascanu

Re: [Standards] Markdown in XMPP IM

Hello Ashley, and others. >> I?m sure this must have been discussed and dismissed before, but would >> adding a some kind of content/MIME type attribute to the body help at all? >> That way a client can stick markdown or yaml or whatever the flavour of the >> day is into the body, give it a

Re: [Standards] XMPP client certificates for SASL EXTERNAL

Hi Evegeny, Could you change the '.pem' extension of the file to '.bin' to allow the download? Probably the browser is trying to import the .pem file and because it's not being a CA cert from a trusted CA it prevents its transfer. Thank you, Emil Romascanu

Re: [Standards] XMPP client certificates for SASL EXTERNAL

Wed, 6 Jan 2016 14:14:27 -0500 "Emil Romascanu" wrote: > Could you change the '.pem' extension of the file to '.bin' to allow > the download? Probably the browser is trying to import the .pem file > and because it's not being a CA cert from a trusted CA it prevents > its

[Standards] Summit XIX and FOSDEM: Help and sponsors needed.

Folks, Your Standards Development Organization needs YOU! If you're coming to the 19th XMPP Summit on the 28th/29th of this month, we've a list of useful things you can help with: * The XSF Dinner will be going ahead, and needs sponsors. Unlike "full" XSF sponsorship, XSF Dinner Sponsorship can

Re: [Standards] Markdown in XMPP IM

> On 6 Jan 2016, at 18:04, Travis Burtrum wrote: > > On 01/06/2016 12:53 PM, Ashley Ward wrote: >> text/x-markdown > > Except markdown means nothing, there is no standard, and no common > implementation. > > I love markdown, but just because your markdown converts with

Re: [Standards] OX (OpenPGP for XMPP): A new OpenPGP XEP

Hi Florian. On Wed, Jan 6, 2016 at 3:32 PM, Florian Schmaus wrote: > Hello everyone, > > After a few more weeks of hard work on a ProtoXEP, we are now pleased to > announce a first preview of our work. Some parts are still not finished, > but everything important is there and

Re: [Standards] Markdown in XMPP IM

Le mercredi 6 janvier 2016, 15:29:31 Peter Waher a écrit : > > Alternatively, if it's just about easier input, support Markdown on > > the sending side and use XHTML-IM. I don't think we really need more > > ways of formatting messages. > > You would not be able to recover the markdown this way,

Re: [Standards] Markdown in XMPP IM

gt; This is definitely possible. It it might also be undesireable, as if a > non-markdown-compliant client sending a message to a markdown-compliant > client. Such text should be displayed as normal text. > > > > > I do not see any reason to wrap markdown in an extra element like it is &g

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

On 1/6/16 9:19 AM, Philipp Hancke wrote: Am 06.01.2016 um 17:15 schrieb Dave Cridland: On 6 January 2016 at 16:13, Philipp Hancke wrote: Am 06.01.2016 um 17:00 schrieb Dave Cridland: On 6 January 2016 at 15:38, Philipp Hancke wrote:

[Standards] Fwd: [Council] Minutes 2016-01-06

FYI > Begin forwarded message: > > From: Kevin Smith > Subject: [Council] Minutes 2016-01-06 > Date: 6 January 2016 at 16:28:48 GMT > To: XMPP Council > > Room logs: http://logs.xmpp.org/council/2016-01-06/ > > 0) Roll call > Lance, Peter, Dave, Tobi, Matt present. > (Kev minutetaking) > >

Re: [Standards] Markdown in XMPP IM

If people are sending extensive essays to each other with embedded HTML and things, then an interpretation flag isn't enough, I agree. But for chat, which I took to be the target given the subject line, I'd expect that a simple hint *should* be sufficient, and the bare markup wouldn't be much

Re: [Standards] Markdown in XMPP IM

> On 6 Jan 2016, at 19:29, Dave Cridland wrote: > > > Ash's suggestion of an additional marker element is probably easier for most > implementations to handle, though. > > Not particularly keen on an alternate body, since the only thing I can think > of to sensibly

Re: [Standards] Standards Digest, Vol 146, Issue 10

Hello Dave & Ashley, and others: > I'd be OK with having a namespaced attribute on the indicating > markdown (with optional variant); the fallback to text seems reasonable > enough. > > Ash's suggestion of an additional marker element is probably easier for > most implementations to handle,

Re: [Standards] XMPP client certificates for SASL EXTERNAL

Thank you Evgeny, I was able to download the certificate. Emil ___ Standards mailing list Info: http://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___

Re: [Standards] Markdown in XMPP IM

I'd actually be very much against this approach; having a hint as to the type of content sounds find, but making it this generic just means that no two clients will ever display the same things, support the same formats, etc. You'll end up with clients sending restructured text to everyone that