<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/doc/netstatus/rs/vote.rs, branch main</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=main</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-05-18T15:55:05Z</updated>
<entry>
<title>tor-netdoc: rs referenced doc digests: Use FixedB64</title>
<updated>2026-05-18T15:55:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-05-18T15:52:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bcc4a6b7e4c374859b95f18c7ec321b465dc0435'/>
<id>urn:sha1:bcc4a6b7e4c374859b95f18c7ec321b465dc0435</id>
<content type='text'>
FixedB64 is the right type for these, when they are present.

This abolishes some ad-hoc boilerplate.  Sadly we still need a bit of
that for Reasons.
</content>
</entry>
<entry>
<title>tor-netdoc: Fix comments in rs variety files</title>
<updated>2026-05-18T15:53:08Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-05-13T13:52:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a7e34e64869b139f318a7cb8c99a6e3d373136ab'/>
<id>urn:sha1:a7e34e64869b139f318a7cb8c99a6e3d373136ab</id>
<content type='text'>
This is router *status* not router *descriptor*.
</content>
</entry>
<entry>
<title>tor-netdoc: Apply much rustfmt churn</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-20T18:10:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b6128c3fb592c141d7ff78b0b51bd95d7c962852'/>
<id>urn:sha1:b6128c3fb592c141d7ff78b0b51bd95d7c962852</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Provide some Vote things</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-21T09:39:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a45ac5ef2ab8311d4f3f8448fd54e3c84b3ac8d7'/>
<id>urn:sha1:a45ac5ef2ab8311d4f3f8448fd54e3c84b3ac8d7</id>
<content type='text'>
And export *RouterStatus with the macro, and *Header.
</content>
</entry>
<entry>
<title>tor-netdoc: Introduce experimental ns-vote feature</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-20T17:53:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=55accf2c26709cec1a9a239526608fa34434ee91'/>
<id>urn:sha1:55accf2c26709cec1a9a239526608fa34434ee91</id>
<content type='text'>
Now we can start actually having code to do with votes.

This feature doesn't actually contain any new API surface yet.
</content>
</entry>
</feed>
