Hi,
https://www.torproject.org/projects/torbrowser/design/#identifier-linkabilit... writes:
While the vast majority of web requests adheres to the circuit and connection unlinkability requirement there are still corner cases we need to treat separately or that lack a fix altogether.
"lack a fix altogether" links back to the design document itself: https://www.torproject.org/projects/torbrowser/design/
is that the correct URL or a copy-paste error?
thanks!
nusenu:
Hi,
https://www.torproject.org/projects/torbrowser/design/#identifier-linkabilit... writes:
While the vast majority of web requests adheres to the circuit and connection unlinkability requirement there are still corner cases we need to treat separately or that lack a fix altogether.
"lack a fix altogether" links back to the design document itself: https://www.torproject.org/projects/torbrowser/design/
is that the correct URL or a copy-paste error?
Neither. :) I made a typo in the source and the resulting HTML file got an empty href attribute, which led to the link pointing to the design doc itself.
This should be fixed now, thanks (and visible once the website rebuilds).
Georg
thanks!
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Georg Koppen:
This should be fixed now, thanks (and visible once the website rebuilds).
Thank you for addressing this so timely.
btw: It would be nice if every subsection (i.e. "SPDY and HTTP/2" would have an anchor so we can easily link to it).
nusenu:
It would be nice if every subsection (i.e. "SPDY and HTTP/2" would have an anchor so we can easily link to it)
in what trac component would I file this request?
"Webpages/Website"?
nusenu:
nusenu:
It would be nice if every subsection (i.e. "SPDY and HTTP/2" would have an anchor so we can easily link to it)
in what trac component would I file this request?
"Webpages/Website"?
Sounds good to me, thanks.
Georg
-
Georg Koppen -
nusenu