On Thu, Oct 17, 2019 at 04:17:23PM +0100, Matthew Wild wrote:
> On Thu, 17 Oct 2019 at 13:34, JC Brand wrote:
> > "some other entity" isn't terribly well defined. How do I (or the
> > recipient of my stickers) know what other entity to ask?
>
> It's part of the identifier, e.g.
>
On Thu, 17 Oct 2019 at 16:17, Matthew Wild wrote:
>
> On Thu, 17 Oct 2019 at 13:34, JC Brand wrote:
> >
> > On Thu, Oct 17, 2019 at 01:23:18PM +0200, Marvin W wrote:
> >
>
> > > - I already dislike the fact that we do HTTP requests to arbitrary servers
> > > for file transfers, as we might be
On Thu, 17 Oct 2019 at 13:34, JC Brand wrote:
>
> On Thu, Oct 17, 2019 at 01:23:18PM +0200, Marvin W wrote:
>
> > - I already dislike the fact that we do HTTP requests to arbitrary servers
> > for file transfers, as we might be leaking IP addresses in such cases.
>
> The file servers are usually
TL;DR — we should avoid using XEP-0372 until "TODO: define character
appropriately" is removed and resolved.
On Thu, Oct 17, 2019, at 10:07, JC Brand wrote:
> Instead, I propose that we use XEP-0372 references to indicate that
> a particular shortname (e.g. :dancingpanda:) should be replaced with
> I'm not sure what you mean. The "begin" and "end" attributes on the
> element can encapsulate the shortname of the sticker.
I mean where the encapsulated text has to be somehow presented to the user
or fully replaced with the sticker as if it never was there.
I believe in some cases (not
On Thu, Oct 17, 2019 at 03:05:32PM +0300, Sergey Ilinykh wrote:
>Doesn't SIMS ([1]https://xmpp.org/extensions/xep-0385.html) resolve all
>the concerns yet?
Yes, SIMS is more comprehensive than my example. It's still uses a XEP-0372
reference, so it's conceptually similar.
>We can
On Thu, Oct 17, 2019 at 01:23:18PM +0200, Marvin W wrote:
> Hi,
> Regarding your proposal:
> - You should still add a hash in the reference somehow so that clients *can*
> cache entries (even if you won't do it in Converse)
Sure.
> - I already dislike the fact that we do HTTP requests to
Doesn't SIMS (https://xmpp.org/extensions/xep-0385.html) resolve all the
concerns yet?
We can have a with cid: uri too.
The only thing is missed as for me is an attribute where the referenced
text has to be removed or not.
Best Regards,
Sergey
чт, 17 окт. 2019 г. в 14:24, Marvin W :
> Hi,
>
Hi,
Regarding your proposal:
- You should still add a hash in the reference somehow so that clients
*can* cache entries (even if you won't do it in Converse)
- I already dislike the fact that we do HTTP requests to arbitrary
servers for file transfers, as we might be leaking IP addresses in
Just make a HTTP HEAD request, look how big the content is then start to
download.
This is not a problem specific of stickers, you have that problem always
when you want to download data, potentially the data can always be big.
or you add an attribute size, and trust the sending client.
regards
Hello
I'm currently working on adding support for non-unicode emojis to Converse.js.
Currently, users can't upload their own images to be used for custom emojis,
mostly because Converse is a thin client with no backend support for it.
So to add custom emojis, the web host needs to edit a
11 matches
Mail list logo
