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
diffe
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 loo
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, tho
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
___
> 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 degrade Markdown into is i
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 transfer.
You could use
On 6 January 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.
>
>
This is sort of true. The IETF attempt at addressing this is here:
https://tools.ietf.or
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
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 ty
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
___
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:
http://www.zinid.ru/cert.pem
__
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 identi
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 01/06/2016 12:53 PM, Ashley Wa
> 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 your tool
> to a format
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
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
> 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 messages.
>>
>> You w
> 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 messages.
>>
>> You w
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 thus the ideal time
> 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
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)
>
> 1)
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,
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:
before publication
What?
Why on earth do we want t
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 do we want to make changes before publication as a XEP
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 changes before publication as a XEP?
>>
>
> wouldn't such
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?
__
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 understand making sure we fix
thin
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 User
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 me. Also +1 on publishing.
>
> Cheers,
> Tobias
> 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
___
Standards mailing li
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 ea
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
difference
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:
Th
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 that there is no markup?
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 straight markdown would
>> be
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 t
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,
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 s
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.
>
> It appears to
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. T
40 matches
Mail list logo