Am Sa., 7. Sept. 2019 um 13:05 Uhr schrieb Andrew Nenakhov
:
>
> Seems like a copy of XEP-0367 Message Attaching. It also shares the same
> problem: no explanation whatsoever on how to fetch these attachments from a
> Message Archive in any efficient way. Ideally, we should retrieve a message
>
Seems like a copy of XEP-0367 Message Attaching. It also shares the same
problem: no explanation whatsoever on how to fetch these attachments from a
Message Archive in any efficient way. Ideally, we should retrieve a message
from an archive with all its attachments. We should also have some kind
Am Sa., 7. Sept. 2019 um 12:54 Uhr schrieb Sergey Ilinykh :
> Regarding references. Andrew Nenakhov gave me a good idea what to reference
> to when want to just an audio message.
> It's a text for clients which do not support SIMS. For example it can be an
> HTTP link to the audio record or
Thanks for the feedback Jonas.
Honestly I already thought about this after implementation and I agree with
you.
Removing "coding" in favor of always base64(u8) would make things way
easier and still sufficient.
And I'm fine with
---
Regarding references. Andrew Nenakhov gave me a good idea
On Mittwoch, 19. Juni 2019 19:46:02 CEST Sergey Ilinykh wrote:
> Hi
>
> I mostly implemented SIMS in Psi and see next problems
>
> 1) The requirement for top-level reference element looks strange.
>In Most of the case when I want to share something, I don't want to
> refer to anything.
>
On Samstag, 7. September 2019 13:08:39 CEST Daniel Gultsch wrote:
> Am Sa., 7. Sept. 2019 um 10:51 Uhr schrieb Marvin W :
> > On 07.09.19 11:55, Daniel Gultsch wrote:
> > > To cover the use case Sergey is talking about here (stand alone voice
> > > message, stand alone image, stand alone file)
Am Sa., 7. Sept. 2019 um 10:51 Uhr schrieb Marvin W :
>
> On 07.09.19 11:55, Daniel Gultsch wrote:
> > To cover the use case Sergey is talking about here (stand alone voice
> > message, stand alone image, stand alone file) without any description
> > wouldn’t it make more sense to be able to put a
On 07.09.19 11:55, Daniel Gultsch wrote:
> To cover the use case Sergey is talking about here (stand alone voice
> message, stand alone image, stand alone file) without any description
> wouldn’t it make more sense to be able to put a sims as a direct child
> of a message (and essentially the only
Am Mi., 19. Juni 2019 um 19:07 Uhr schrieb Sergey Ilinykh :
> Then yes the xep has to be updated with use-cases. Since for now only
> internal elements looks usable and it's hard to imagine any
> good UX for the top-level one.
To cover the use case Sergey is talking about here (stand alone
