jdev - 2022-04-29

Played a bit with the rpad generation: go build . && journalctl -f|./go-sendxmpp -i --ox JID1 JID2

message length: 122

rapd length: 78

rpad: /MjJz/2Nv+XNCU1&!f,cB)-?lVUduWWKRSVWq173Xh1jkiPn(-bXA/WZd+gM3L+Q$n5Ym%+3)j,3sb

message length: 122

rapd length: 78

rpad: Wh1a!__?2zC3f8§h(cgQngmjYTpTq)FPIxUA)vRklcFZNUJn/Y.$ztFx3=m3y;(ZR&AqibI=0a/,Tf

message length: 94

rapd length: 6

rpad: ,k_+-C

message length: 94

rapd length: 6

rpad: 7K790T

message length: 103

rapd length: 97

rpad: Tb48%m9F9RB5of)?aUV9(§79SBjcUB,XeHfsjWNi34§tU1qpo1&J§iK7iqUi_cXNER5cb+t1QY%Y_aTDD,kvK?)FEvg;Usi!(

message length: 103

rapd length: 97

rpad: %XB+Dhv.DeGF4yzyEng(Iw/dD.(XHO4REvo5rTA57FX;VN+ceOdBizf_)Oq6Pdas;OG?OqRanz2oE0&lMJbV1WZa§9thvEJ?F

message length: 104

rapd length: 96

rpad: 0FQjzqzBBq_5D4Q/pT6ep/lk)pPY2I,§3RE,/qyuemj,tDP6$A_RtyzT9+Lid%-JSEG1!I)w)%Glv&C6=Fbm__DC5P,iGuN.

message length: 104

rapd length: 96

rpad: cu§qkOMvVL3M4gYU;t53%Hvsajm8A?&n3+1$-NM19zJtw7LKR8lFvoI2B$m7b8r-ZzjNf5_-t0OnB§KXs?bs(&vBHhKR3F3h

message length: 104

rapd length: 96

rpad: Z-2j-mNjXz+muFFUn/3/)FA-5nVLE91KHmyJYBHd%)8WWm0OLVcfjm_,(dw0gwzD(uNZ,jm)Cry4_§/CQBf//yEHrX2g)ljV

message length: 104

rapd length: 96

Meh

Copy paste error. Mea culpa.

I wanted to paste just https://paste.debian.net/1239385/

;-(

Martin, I am courious oabout the "journalctl" in the command line. what's its purpose?

Just providing me some input.

journalctl -f just shows you the 'syslog'.

I don't suppose XMPP has an equivalent to Threemas way of acknowledging or rejecting messages? (That is, the thumbs up down stuff on messgaes, a /very/ explicit kind of "I read this" marker that only is send on user interation)

It's very neat to me to use this instead of read markers, since it shows me which messages my conversation partner has acknowledged instead of just "happened to have the chat open" or any other heuristic scenarios that may cause the client to send the read marker

yes the protocol exists, but nobody implements it

and if someone implements it, it's not merged yet

and if it is, it's behind a feature flag

Well, I can implement it :D... If i know which XEP it is... don't think Renga has any feature flags whatsoever

https://xmpp.org/extensions/xep-0444.html is the latest I think

(Funny, also... I can use a keyboard with Siskin IM but not send messages, only adds newlines. Still have to press the button manually :/)

I am very confused by that XEP, what does it mean with the reaction contains an emoji? Is unicode mathematical symbols illegal? Is it only allowed to send a single character? What about combining characters? It's very vague to me I'm also unsure of why this is even tied to emoji in the first place

Because that's how it's usually used in other things

In matrix they also tried to do "with emoji" but in practice because of their validation rules it is perfectly valid to "react" with "Have you ever heard of the tragedy of darth plageius the wise?" to messages, i suppose this is similar?

Odd to have such restrictions in the protocol I guess. Why couldn't I react with "lol" ?

Zash: atleast the Threema case above has nothing to do with emoji, it only serves to show "I acked this" or "I reject this" pretty much

UI/UX considerations in network protocols is weird 🤷️

What do you mean by that?

If i want to assign a meaning to a message surely the protocol has to know so clients can be sure that the meaning exists? If i just interpret random stuff to mean "they probably ment this as an ack" that is not that usefull for interopability i would think?

I mean I think it is can out of place for a network protocol specification to dictate things that belongs in high level application design

If you want a protocol exactly for your Threema use case, then you might need to write a XEP

Hm

Actually, there's one

Well, why specify reactions in the first place then? Is it any different from any other message referencing another message?

https://xmpp.org/extensions/xep-0333.html had something about explicit acknowledgement

I thought we were going to delete that tho

nephele, we don't have that either

or, we have 3 different XEPs nobody implements for other kinds of references

Well, matrix went with specifying reactions /AND/ replies, incompatibly... I hope we can avoid that mess :P

what is a reaction if not a compact way to display a reply?

I Suppose I can implement the reaction thing, but ignore the "only emoji" part and treat it as a string? I don't see how I would realistically validate input to be emoji only...

I think reactions and replies are essentially the same thing, just rendered a bit differently

Complications like this might be why 0444 isn't 03xx something

do the XEP numbers have meaning?

No

Assigned mostly serial by the XEP Editor

ah

Like RFCs

I meant in that why 0444 wasn't published much earlier, ie with a lower number

Ah, that makes sense

see also https://xmpp.org/extensions/xep-0372.html https://xmpp.org/extensions/xep-0367.html

oh, and https://xmpp.org/extensions/xep-0461.html

right, so we actually have something like emails In-Reply-To now

I'm getting the feeling that xmpp has its own "This is terrible, we need one standard to unify them all!" situatuion with XEPs

Yes.