<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ao2-client/src/vli.c, branch master</title>
<subtitle>AO2 client fork</subtitle>
<link rel='alternate' type='text/html' href='https://git.sof.beauty/ao2-client/'/>
<entry>
<title>Add the extension packets</title>
<updated>2026-03-29T22:22:25+00:00</updated>
<author>
<name>Osmium Sorcerer</name>
<email>os@sof.beauty</email>
</author>
<published>2026-03-22T18:16:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sof.beauty/ao2-client/commit/?id=6c30e71ed08cdb838b77b3fe52dea30774574230'/>
<id>6c30e71ed08cdb838b77b3fe52dea30774574230</id>
<content type='text'>
Introduce the subprotocol ("Einsof"), its prototype serialization and
parsing functions, and its first set of messages.

These messages are carriers of public-key authentication mechanism which
involves client request, server challenge, and client response. An
"ident" message is used to tell a compatible server that you support a
particular version of the subprotocol.

Note: the functions that handle encoding are very specialized.
They're not representative of how the wire format should be generally
handled, and were written this way because the first set of messages is
tiny and simple enough.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Introduce the subprotocol ("Einsof"), its prototype serialization and
parsing functions, and its first set of messages.

These messages are carriers of public-key authentication mechanism which
involves client request, server challenge, and client response. An
"ident" message is used to tell a compatible server that you support a
particular version of the subprotocol.

Note: the functions that handle encoding are very specialized.
They're not representative of how the wire format should be generally
handled, and were written this way because the first set of messages is
tiny and simple enough.
</pre>
</div>
</content>
</entry>
</feed>
