Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T13:30:40Zhttps://gitlab.torproject.org/legacy/trac/-/issues/28207Cleanup duplicate and near-duplicate chutney networks2020-06-13T13:30:40ZteorCleanup duplicate and near-duplicate chutney networksThere are a bunch of chutney networks that are duplicates or near-duplicates of each other.
Instead of duplicating code, we could turn the network code into a function, and then call it from all similar networks.There are a bunch of chutney networks that are duplicates or near-duplicates of each other.
Instead of duplicating code, we could turn the network code into a function, and then call it from all similar networks.https://gitlab.torproject.org/legacy/trac/-/issues/17240Refactor the HS code to support both current and proposal 224 design2020-06-13T14:49:55ZDavid Gouletdgoulet@torproject.orgRefactor the HS code to support both current and proposal 224 designThis is an important task since we need both system to live in parallel for multiple years and before we start the heart of the work on proposal 224, we need to accomodate the code so we avoid huge amount of code duplication.
Would be a...This is an important task since we need both system to live in parallel for multiple years and before we start the heart of the work on proposal 224, we need to accomodate the code so we avoid huge amount of code duplication.
Would be also a good opportunity to add unit tests while doing so!
Here are some notes on a possible start up point to refactor: https://people.torproject.org/~dgoulet/hs224-refactor.txt