Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Goffi
Le lundi 16 octobre 2017, 13:46:02 CEST Dave Cridland a écrit : > On 16 October 2017 at 12:04, Georg Lukas wrote: > > * Dave Cridland [2017-10-15 11:06]: > >> A Snippet is a small item of content. It is normally referenced within > >> a chatroom or 1:1 chat. I'm only going to define use in MUC; >

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Dave Cridland
On 16 October 2017 at 12:04, Georg Lukas wrote: > * Dave Cridland [2017-10-15 11:06]: >> A Snippet is a small item of content. It is normally referenced within >> a chatroom or 1:1 chat. I'm only going to define use in MUC; > > I'm curious what the benefits are compared to just sending whatever >

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Jonas Wielicki
On Montag, 16. Oktober 2017 13:04:14 CEST Georg Lukas wrote: > > * Display inbound snippets. Since all content is a URI, web-based > > clients SHOULD use a sandboxed iframe, so XHTML should be fine. > > Couldn't we just use a sandboxed iframe to render XHTML-IM? That leads to horrible UX since yo

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Georg Lukas
* Dave Cridland [2017-10-15 11:06]: > A Snippet is a small item of content. It is normally referenced within > a chatroom or 1:1 chat. I'm only going to define use in MUC; I'm curious what the benefits are compared to just sending whatever snippet you want inside of a message, or using http-uploa

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Kevin Smith
On 16 Oct 2017, at 10:09, Dave Cridland wrote: > > On 16 October 2017 at 10:03, Kevin Smith wrote: >> It’s certainly the path of least resistance for web clients. I’m somewhat >> concerned that >> a) “anything goes” means you can have essentially no reliable >> interoperability - potentially e

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Dave Cridland
On 16 October 2017 at 10:03, Kevin Smith wrote: > It’s certainly the path of least resistance for web clients. I’m somewhat > concerned that > a) “anything goes” means you can have essentially no reliable > interoperability - potentially even between the same client, if it happens to > be runni

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Kevin Smith
On 16 Oct 2017, at 09:58, Dave Cridland wrote: > On 15 October 2017 at 11:22, Kevin Smith wrote: >> On 15 Oct 2017, at 10:03, Dave Cridland wrote: >>> I'm just polling for interest; I said I'd write this up properly >>> elsewhere, but is there interest in the following: >> Yes > Jolly good. I'll

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-16 Thread Dave Cridland
On 15 October 2017 at 11:22, Kevin Smith wrote: > On 15 Oct 2017, at 10:03, Dave Cridland wrote: >> I'm just polling for interest; I said I'd write this up properly >> elsewhere, but is there interest in the following: > > Yes > Jolly good. I'll XEPerize this on various trains later. >> A Snipp

Re: [Standards] A Quick and Dirty design for "Snippets"

2017-10-15 Thread Kevin Smith
On 15 Oct 2017, at 10:03, Dave Cridland wrote: > I'm just polling for interest; I said I'd write this up properly > elsewhere, but is there interest in the following: Yes > A Snippet is a small item of content. It is normally referenced within > a chatroom or 1:1 chat. I'm only going to define u

[Standards] A Quick and Dirty design for "Snippets"

2017-10-15 Thread Dave Cridland
I'm just polling for interest; I said I'd write this up properly elsewhere, but is there interest in the following: A Snippet is a small item of content. It is normally referenced within a chatroom or 1:1 chat. I'm only going to define use in MUC; The implementation consists of using two pubsub n