Basically i started to type a message on my phone and saw it appearing on desktop. So basically they sync up a draft.
Toxihas left
Ge0rG
That's actually quite a nice UX.
Ge0rG
I've had that situation multiple times, that I wanted to send a message from the PC enriched with a link from my phone, or to switch typing in the middle of things because typing on the PC is so much easier
antranigvhas joined
jubalhhas left
jgarthas joined
jubalhhas joined
marc0shas left
marc0shas joined
alhas left
marc0shas left
marc0shas joined
edhelas
I'm wondering how this could be replicated on XMPP š¤
edhelas
I can actually sync it in Movim easily between the different tabs :p
Ge0rG
edhelas: write a XEP to send message drafts as a custom element in the <message> to your own JID, implement it together with XEP-0352 to prevent constant flooding on each typed letter
aramhas joined
edhelas
why not use a pep node and store draft messages there :p
edhelas
with itemid = JID of the future receiver
Link Mauve
Implement XEP-0301!
Martin
> I'm wondering how this could be replicated on XMPP š¤
Maybe stuff from RTT could be reused. Afair Dino has something.
Ge0rG
<message from="georg@yax.im/desktop" to="georg@yax.im">
<draft xmlns="urn:xmpp:message-draft" to="jdev@muc.xmpp.org">
I was thinking abo
</draft>
</message>
Ge0rG
edhelas: the big challenge is how to E2EE your drafts
Martin
Multi-Device Support to sync input between different instances of Dino. With this, a user can start composing a message on one device and finish on another. (Details, see here)
https://wolfieanmol.github.io/gsoc-blog/support-for-multiple-devices-muc/
Ge0rG
Sending RTTs to the MUC might not be such a wise idea
pep.
Ge0rG, how e2ee your drafts? At first glance I don't see this particularly hard
antranigvhas left
Link Mauve
pep., one issue could be that as you know a former draft is very likely to be a prefix of a latter one, it could weaken the encryption.
pep.
With OMEMO you're not sending to yourself (the same device) so that's fine. If you send to your own jid you might want to include in clear that it's a draft, or not even since you'd be able to know with the id that it comes from you..
pep.
hmm
Link Mauve
The more the attacker knows about your plain text, the more your encryption could be vulnerable.
Link Mauve
Although Iām not aware of any such issue in current algorithms.
sonnyhas left
sonnyhas joined
sonnyhas left
sonnyhas joined
aramhas left
sonnyhas left
sonnyhas joined
sonnyhas left
sonnyhas joined
sonnyhas left
sonnyhas joined
debaclehas left
jubalhhas left
jubalhhas joined
huhnhas joined
Martinhas left
Martinhas joined
goffihas left
goffihas joined
Wojtekhas joined
jgarthas left
goffihas left
pulkomandyhas joined
Kevhas left
Kevhas joined
pulkomandyhas left
pulkomandyhas joined
jubalhhas left
hiranhas joined
goffihas joined
Zashhas left
hiranhas left
Zashhas joined
xeckshas left
xeckshas joined
tskhas joined
marmistrzhas left
pulkomandyhas left
debaclehas joined
Kevhas left
Kevhas joined
Kevhas left
Kevhas joined
marmistrzhas joined
marchas left
marchas joined
jubalhhas joined
Mx2has left
Mx2has joined
goffihas left
goffihas joined
marchas left
x51has joined
dezanthas joined
pulkomandyhas joined
pulkomandy
If you append some salt to the draft before encryption, you can easily make sure it's not a strict prefix
pulkomandy
Maybe even better to prepend some salt?
pulkomandyhas left
jubalhhas left
marmistrzhas left
marchas joined
antranigvhas joined
raghavgururajanhas joined
pep.
There is an rpad element in SCE already. If oldmemo is used maybe it can be specified where to put that pad (and that's where I bail out, don't know much about that)
Zash
Nice things only being available if you move forward might help push forward nice things?
pep.
The endless loop of going forward(tm)
Zash
Something something wheels and turning.
marmistrzhas joined
jubalhhas joined
emushas left
emushas joined
larmahas joined
Toxihas joined
marmistrzhas left
antranigvhas left
antranigvhas joined
antranigvhas left
marmistrzhas joined
Toxihas left
antranigvhas joined
selurveduhas joined
antranigvhas left
pasdesushihas left
pasdesushihas joined
me9has joined
Kevhas left
Kevhas joined
Kevhas left
Kevhas joined
junaidhas joined
marmistrzhas left
pulkomandyhas joined
marmistrzhas joined
pulkomandyhas left
pulkomandyhas joined
marc0shas left
marc0shas joined
serge90has left
xeckshas left
atomicwatchhas left
serge90has joined
atomicwatchhas joined
marmistrzhas left
marc0shas left
marc0shas joined
marchas left
jgarthas joined
marchas joined
Toxihas joined
9lakeshas left
Kevhas left
Kevhas joined
9lakeshas joined
marmistrzhas joined
rom1dephas left
goffihas left
xeckshas joined
Link Mauvehas left
marmistrzhas left
Link Mauvehas joined
debaclehas left
homebeachhas left
Matrix Traveler (bot)has left
Matrix Traveler (bot)has joined
homebeachhas joined
rom1dephas joined
lovetox
bitlbee code comment about caps in presence
lovetox
it doesnt send the hash attr
lovetox
/* The XEP wants this hashed, but nobody's doing that. */
lovetox
i think they didnt really get what the xep was about
lovetox
ok so i get it they didnt want to hash their disco info, because it was too much work
lovetox
now they put in just the client version so ver=3.6.1
Zash
How old is that line?
lovetox
but obviously this is not sha-1 hash
lovetox
so they dont add the hash attr
Zash
Very very very old things don't
lovetox
would it still be an improvement if we add hash=sha-1?
lovetox
if they only change disco features between released versions, this would still work
lovetox
no it would not for gajim, as it hashes the disco info itself and would report it if it does not is the same
Vaulorhas left
lovetox
... so i still get a warning in logs
Zash
https://xmpp.org/extensions/xep-0115.html#legacy
Zash
Huh, this was only done in 2007?
Petehas left
Zash
And then we have https://xmpp.org/extensions/xep-0390.html