> On 23 Nov 2017, at 22:18, Matthew Wild wrote:
>
> On 23 November 2017 at 18:33, Daniel Gultsch wrote:
>> 2017-11-23 18:33 GMT+01:00 Kevin Smith :
>>> The main use case for having gc messages in the archive is “I remember I
>>> saw someone say something interesting about X, so now I’m going t
2017-11-23 23:18 GMT+01:00 Matthew Wild :
> I'd rather just not archive type=groupchat in the first place (which
> is what current implementations are actually doing anyway). You are
> perfectly right that the user archive server is 1) not the best place
> to archive these messages and 2) not in th
On 23 November 2017 at 18:33, Daniel Gultsch wrote:
> 2017-11-23 18:33 GMT+01:00 Kevin Smith :
>> The main use case for having gc messages in the archive is “I remember I saw
>> someone say something interesting about X, so now I’m going to search my
>> archive for X to find it”, which really ne
Filter options will be necessary in the future or MUC Archives will become
unusable.
Conversations now stores chatmarkers with the store hint inside MUC
Archives, add receipts to that, and you have in a room with 10 people for
every message up to 20 non body messages (1 receipt, 1 chatmarker) stor
Thu, 23 Nov 2017 19:19:38 +0100
Kim Alvefur wrote:
> It does make some sense to allow a for a future where MIX is common
> and the problems with storing MUC messages in personal archives has
> gone away.
How will it be gone away? MIX still suggests using MUC archives
directly when you're joining
2017-11-23 18:33 GMT+01:00 Kevin Smith :
> The main use case for having gc messages in the archive is “I remember I saw
> someone say something interesting about X, so now I’m going to search my
> archive for X to find it”, which really needs to have all the messages you’ve
> seen available, rat
I agree that for “catch-up”, it’s not particularly useful, but knowing exactly
what messages you’ve seen is.
Makes sense if we see the Archive as Store of all messages we have seen.
I often forget thats that the original idea, because of OMEMO PFS i does
not serv that purpose.
Also if we
On Thu, Nov 23, 2017 at 06:11:32PM +0100, Daniel Gultsch wrote:
> ignoring the »A server SHOULD also include messages of type
> 'groupchat' that have a \« statement from the XEP.)
I must have either overlooked that text or forgotten about it.
> For me it doesn't ever make sense to store type=grou
On 23 Nov 2017, at 17:11, Daniel Gultsch wrote:
>
> Hi,
>
> today I stumbled over an interesting behaviour of ejabberd MAM implementation.
> While ejabberd usually does not store messages of type groupchat into
> the users archive (ignoring the »A server SHOULD also include messages
> of type 'g
is and what would client
developers want?
i also found this out the hard way, thats why i drop all messages
type=groupchat immediatly on a user archiv query.
i dont see a use for this.
___
Standards mailing list
Info: https://mail.jabber.org/mailm
On Thu, 2017-11-23 at 17:02 +0100, Jonas Wielicki wrote:
> > * 5.2 Corrections for Color Vision Deficiencies
> >
> > > 5.2.1 Red/Green-blindness
> > > Divide the angle by two.
> >
> > This will change *all* angles, with the exception of 0, when
> > toggling
> > between traditional and color-blind
Hi,
today I stumbled over an interesting behaviour of ejabberd MAM implementation.
While ejabberd usually does not store messages of type groupchat into
the users archive (ignoring the »A server SHOULD also include messages
of type 'groupchat' that have a « statement from the XEP.) it
does store t
> If we would be choosing a modern hash function, something from the SHA3 family
> or blake would be more sensible.
Please consider using either SHA-1 or SHA-256, not blake.
The reason: It at least makes Java implementations easier, because those are
available on every implementation of the Jav
Hi Marcel,
Thank you very much for your feedback. There’s some valuable stuff in there.
On Mittwoch, 22. November 2017 09:36:48 CET Marcel Waldvogel wrote:
> Jonas Wielicki wrote:
> > Yes, I plan to clarify this soon. Will take a few days though, for
> > reasons beyond my control.
> > FTR: the t
14 matches
Mail list logo