furry: :ferret_beg: hello, tox protocol is fucked
c-toxcore devs: :gutkato_malprofito: we don't intend to do anything about it

well'p.

@icedquinn i wonder if there is anything vaguely modern which isn't shit from a protocol perspective.

@bonifartius guess we're going back to xmpp with the ole privacy plugin

@icedquinn i never got anything except plain text to reliably work with xmpp, expecially file transfers.

i think the old line based protocols like IRC are residing in a very deep local optimum. everyone tries to replace them, and either it's not really worth it or things are killed by the own complexity.

only problem IRC has is that E2EE is hard to do within 512 characters ;)

@bonifartius i used the thing that came before omemo for a while. i think we only trashed it because omemo is supposed to work with group chats.

not real big on line protocols. i prefer things carry length prefixes :neocat_woozy:

@icedquinn nothing wrong with prefixed lines, it's more about how the data is formatted. sonething IRC, SMTP, etc. do seems to be correct.

unfortunately everything is bloated json now which somehow manages to be even worse than bloated xml.

@bonifartius i shitposted about using OSC for something like this :neocat_woozy:

the ember+ specs are not too bad. they are kind of long, although not entirely without reason. those model everything in the world as a tree though.

@icedquinn ASN.1 is probably one of the more sane choices for encoding things, yeah. I do like the ascii line protocols though because they are rediciously easy to parse as well, even when they not follow a particular standard.

ember looks interesting!

@bonifartius they subset BER and then use it to encode a graph of nodes with parameters. seems like a pretty clean way to go actually.
Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.