You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The technical reports we generate need to make it possible to understand how we concluded that the mentioned information was actually transmitted in each request.
In 6ba8233, I implemented that by simply linking to the hosted documentation on trackers.tweasel.org. That is fine for now, but in the long run we'll want to include the relevant documentation in the report.
Main reasons why I'm not doing that already: tracker-wiki is still undergoing some changes and we haven't settled on final decisions yet. Also, the documentation there is generated by Hugo and I'm not sure of what the best way of reproducing that in JS is (ideally without maintaining two copies of the same code in different languages).
The text was updated successfully, but these errors were encountered:
The technical reports we generate need to make it possible to understand how we concluded that the mentioned information was actually transmitted in each request.
In 6ba8233, I implemented that by simply linking to the hosted documentation on trackers.tweasel.org. That is fine for now, but in the long run we'll want to include the relevant documentation in the report.
Main reasons why I'm not doing that already: tracker-wiki is still undergoing some changes and we haven't settled on final decisions yet. Also, the documentation there is generated by Hugo and I'm not sure of what the best way of reproducing that in JS is (ideally without maintaining two copies of the same code in different languages).
The text was updated successfully, but these errors were encountered: