jdev - 2022-04-26

archiving preferences are broken

movim set it per default to contact list

means if someone writes me in a muc a PM, this is not saved to the archive

if my client loses network connection, and in this time some user writes me

server does not archive the messages ..

so i never receive them, but the user also gets no error back

that seems broken, although it has not really something to do with archiving preferences

should the server not store the messages as offline messages if he sees with stream management that the messages were never acked?

(conflicting use-cases in an interoperable network, *surprise*)

but really, archive preferences break syncing with multiple devices

when people use it they think: Uh yeah i dont want to store these messages

but in reality they choose: Uh i dont want to sync messages with my other devices anymore

its even worse if server operators do the choosing for the users

lovetox, I agree, I really regret adding those options

Which is partly why I split them out of '313

But a surprising number of clients already implement it

How do these clients react if the 0441 toggles aren’t exposed?

im not understanding the question Link Mauve

As some server set defaults that are a none starter

it would be foolish of clients not to expose this setting