<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/doc/netstatus/rs/build, 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-06-15T11:53:20Z</updated>
<entry>
<title>tor-netdoc: routerstatus entries: Add `stats` item (votes only)</title>
<updated>2026-06-15T11:53:20Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-06-01T17:37:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0b215ef42d7d4d4e957e4b6a124995190414f64e'/>
<id>urn:sha1:0b215ef42d7d4d4e957e4b6a124995190414f64e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: routerstatus entries: Add `id` item (votes only)</title>
<updated>2026-06-11T12:26:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-06-03T13:12:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6e4a7696b3d5b09e39b1d19b74e97c5eaa13cf6a'/>
<id>urn:sha1:6e4a7696b3d5b09e39b1d19b74e97c5eaa13cf6a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: routerstatus entries: Add `p` item</title>
<updated>2026-06-11T12:26:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-06-01T17:18:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=90bfd45527aa8eadcaa9a9b17de49e5f5d350c46'/>
<id>urn:sha1:90bfd45527aa8eadcaa9a9b17de49e5f5d350c46</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: routerstatus: r item: add dir-port argument</title>
<updated>2026-06-11T12:26:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-06-03T11:47:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=26f1102b14d68c287a6edd92f6bc65e676d7e559'/>
<id>urn:sha1:26f1102b14d68c287a6edd92f6bc65e676d7e559</id>
<content type='text'>
This was simply missing.
</content>
</entry>
<entry>
<title>tor-netdoc: Rename RelayWeights to RelayWeightsItem</title>
<updated>2026-05-27T14:38:26Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-05-18T16:18:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5e9498a6423efd0e0f2f9ac400cbac9fe5845dc3'/>
<id>urn:sha1:5e9498a6423efd0e0f2f9ac400cbac9fe5845dc3</id>
<content type='text'>
Prompted by
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3991#note_3413168
</content>
</entry>
<entry>
<title>tor-netdoc: Introduce RelayWeights and use it in RouterStatus</title>
<updated>2026-05-27T14:38:26Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-05-14T11:14:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=307822741164adfc4fd4439d2ad3157e41d91eb2'/>
<id>urn:sha1:307822741164adfc4fd4439d2ad3157e41d91eb2</id>
<content type='text'>
For encoding, we need to represent the raw parameters.

This change is carefully arranged so that when the retain unknown feature is
disabled (ie, in clients), the per-router data structure remains the
same.
</content>
</entry>
<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: Make Nickname have its own parsing error type</title>
<updated>2026-04-20T14:42:09Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-04-15T10:48:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4fbbf59bec47196e2abaaa7da225903523564eb7'/>
<id>urn:sha1:4fbbf59bec47196e2abaaa7da225903523564eb7</id>
<content type='text'>
This will let us use it in more places, more sensibly.

Sadly it means a lot of syntactic vinegar at many of the call sites in
the old parser, which has very janky ideas about how errors should
work.
</content>
</entry>
<entry>
<title>netdoc: Remove protocol interning.</title>
<updated>2025-12-03T15:18:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-12-02T15:52:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6ff5b20a2e5403024589115e4439d5964345d38b'/>
<id>urn:sha1:6ff5b20a2e5403024589115e4439d5964345d38b</id>
<content type='text'>
(It's now done in tor_protover.)
</content>
</entry>
<entry>
<title>tor-netdoc: rs builder: Take Into&lt;RelayFlags&gt;</title>
<updated>2025-11-18T19:44:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-11-18T18:27:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0a56f469d2568ba4e5339bde5d6b0b68a26581ba'/>
<id>urn:sha1:0a56f469d2568ba4e5339bde5d6b0b68a26581ba</id>
<content type='text'>
Many call sites pass one flag.  We're going to have a type-level
distinction between a single flag and a set.  But that's annoying at
many of the call sites which want to specify a fixed single flag.

Note that `set_flags` doesn't only set flags.  It replaces them.
</content>
</entry>
</feed>
