<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/README.md, branch arti-v1.8.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-11-10T19:30:48Z</updated>
<entry>
<title>tor-netdoc: Introduce "encode" feature for the like-named module</title>
<updated>2025-11-10T19:30:48Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-07T18:04:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=31f1e62db6dea15bb325cb3d3477282ca8512829'/>
<id>urn:sha1:31f1e62db6dea15bb325cb3d3477282ca8512829</id>
<content type='text'>
We're going to introduce facilities for encoding more generally, and
we'll want a way to enable them.

Instead, have a separate feature for *encoding* documents.
</content>
</entry>
<entry>
<title>tor-netdoc: Deprecate the netdoc "builder pattern"</title>
<updated>2025-10-07T18:09:39Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-07T17:53:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=24fbc687637a7d583e8a45c1a9f2b347447069eb'/>
<id>urn:sha1:24fbc687637a7d583e8a45c1a9f2b347447069eb</id>
<content type='text'>
We're going to eventually implement the traits in `src/build.rs` for
the network document types.

But, this feature mainly covers `doc/*build*`.  That (a) isn't used
in-tree (b) isn't really needed now that the fields are all pub
(c) is currently marked experimental.
</content>
</entry>
<entry>
<title>tor-netdoc: Document the `hs-client` and `hs-service` features</title>
<updated>2025-10-07T17:53:04Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-07T17:53:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5b2217df0b08bb8a7f2d5714a439910df0429e27'/>
<id>urn:sha1:5b2217df0b08bb8a7f2d5714a439910df0429e27</id>
<content type='text'>
And mention that there are experimental and undocumented features.
</content>
</entry>
<entry>
<title>tor-netdoc: Rename ns-consensus to plain-consensus</title>
<updated>2025-08-18T17:40:48Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-18T15:44:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=187a73606a3f248086d67c74a50af0ea22212028'/>
<id>urn:sha1:187a73606a3f248086d67c74a50af0ea22212028</id>
<content type='text'>
ns-consensus doesn't seem to have ever been released.

This is part of abolishing the use of "ns" to mean "plain".
</content>
</entry>
<entry>
<title>run ./maint/readmes.sh</title>
<updated>2021-11-29T11:29:28Z</updated>
<author>
<name>dagon</name>
<email>dagon12@tutanota.com</email>
</author>
<published>2021-11-29T11:29:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d5c48c616fd40313f0428d14bae97419ae3dac95'/>
<id>urn:sha1:d5c48c616fd40313f0428d14bae97419ae3dac95</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move all crates into a `crates` subdirectory.</title>
<updated>2021-08-27T13:53:09Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-08-27T13:53:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=557a0ff40b3731d4690767de27010bbeff08777d'/>
<id>urn:sha1:557a0ff40b3731d4690767de27010bbeff08777d</id>
<content type='text'>
This will cause some pain for now, but now is really the best time
to do this kind of thing.
</content>
</entry>
</feed>
