<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdir/src/hsdir_ring.rs, branch arti-v1.1.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-01-28T17:43:08Z</updated>
<entry>
<title>netdir: Implement ring-param constructors and time period accessors</title>
<updated>2023-01-28T17:43:08Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-24T15:46:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5236c5cf887af0bd321ca80fb6dba991289549d6'/>
<id>urn:sha1:5236c5cf887af0bd321ca80fb6dba991289549d6</id>
<content type='text'>
This logic is a bit tricky, so I've tried to document it and add
fairly good tests.  The silver lining is that the external API for
all of this logic will make it invisible and hidden.

There are some cases where I added functions that I think might
eventually get lowered into MdConsensus: But I don't want to lower
too much right now, since the convention for our netdoc accessors is
that they are fairly unsophisticated, and they show you the document
as it is.

Closes #686
</content>
</entry>
<entry>
<title>Adjust onion service ring APIs in light of prop#342</title>
<updated>2023-01-11T14:04:13Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-10T14:23:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5b74ef7af9be657918b1b2c8672f35b269c23198'/>
<id>urn:sha1:5b74ef7af9be657918b1b2c8672f35b269c23198</id>
<content type='text'>
* It is the NetDir's responsibility to tell the caller what the time
  period is.
* There can be up to two secondary time periods.
* Each time period has a single SRV.
* Secondary time periods only apply for onion services, when they
  publish.
* When publishing, the correct input is a time period.
</content>
</entry>
<entry>
<title>Sketch APIs for the onion service directory ring.</title>
<updated>2023-01-11T14:04:13Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-09T17:10:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f24f8d295cf3ec324034c824fbbb40a694acb6f1'/>
<id>urn:sha1:f24f8d295cf3ec324034c824fbbb40a694acb6f1</id>
<content type='text'>
These are a bit complex internally, but the API they present is
pretty simple.  I've left some discussion of points where the design
isn't totally fleshed out, and where we need to look harder at the
spec.

Part of #716.
</content>
</entry>
</feed>
