jdev - 2022-04-27

d

hello

hope you are ok

lovetox, I was wondering if a hypothetically well-configured server didn’t even expose the footgun settings, would clients stop considering MAM as available or would it have no consequence?

block the iq-set with some policy error?

I was thinking about moving the prefs handling into a different module eventually.

Perhaps a community one.

Separating archiving from the query protocol was also a thought.

Link Mauve, prevs have nothing to do with considering if mam works

prevs are only queried by the user if he wants to change them

as a client i never look at them, i dont care if they exist or not

s/prevs/prefs/?

yes

i mean maybe i should care, maybe i should warn the user that his server has set a policy that could lead to message loss

There was talk about replacing it with a retention control instead of yes/no

As in, "how long"

not too much difference though

i still have to warn the user that he might experience message loss with too low retention

but of course dataretention policy would be a nice feature

someone should propose this for the archive pref xep

im just not sure if it is really necessary to have the "store nothing" case at all

like xmpp gives so much freedom, everybody can setup their own servers

you can use E2E encryption

there is relly much you can do if you want to secure your data

better ways than to break message delivery with a "no store" policy ✏

you want to use the internet, but nobody should store anything for more than 2 seconds ...

seems unreasonable