HackerNCoders blog

I will update this blog post when I change my mirrors, or if I have other information I think is important

My current mirrors are hosted on the invidious.site domain:

www.torproject.org > tor.invidious.site
support.torproject.org > support.tor.invidious.site
tb-manual.torproject.org > tb-manual.tor.invidious.site
gettor.torproject.org > gettor.tor.invidious.site
community.torproject.org > community.tor.invidious.site
blog.torproject.org > blog.tor.invidious.site
2019.www.torproject.org > 2019.tor.invidious.site
metrics.torproject.org > metrics.invidious.site

It allows Tor Browser downloads (at first my tor.encryptionin.space mirror didn't, and some future mirrors may not). I have changed the support article on how to verify Tor Browser such that it points to tor.invidious.site which I hope will allow people to verify Tor Browser.


sha256sums-unsigned-build.txt for TB 11-build1 is 3e0aa856640f7ad01a27d76ee38731ecea8efffabf28b673814107c3d22c2c80 ——-BEGIN PGP SIGNATURE——-

iQIzBAEBCAAdFiEEU9vi1DNGvZsRSCmw29qkcHgyA5cFAmGH71MACgkQ29qkcHgy A5fRCw/9ErF7KRnWJ99+V1yUlKr8vxKNrZIchoWyBFZP/Xmq+YzKYE54mSha5ktI jElam8kTuOmyOn9yFW1GBVmCkR13Uwo7PmVnU+Mi2oGYSNwKMavDtRnY38HbW6jG O2CnTaa/vBv4PquZLXB6OlhlG8BdnMhc0E2+afh56B01P6Msm7PxHX29Ya8lTsls J/BYKcAPVEC/WKkBrlnBxV43YF91xJsyi08drTR7zWbeC4rKZ6MJx+LnA8a6Mt5e IhifF2u1nHAXZ0iLHTA2R0JeaXxu8mo1Kl6TwOm0d05A22PeBhjLq6QKE5Tn5mKO dtW/GqBrOQZ5J9pY1xsO4pa97nu6k/XtbSvzPlzH8c20WG30zsDAzbvi5clheiXk GbbKGMNSQa+vMH4LzEWrGw3fMnZacZ9krtxFl2zPs0AteE5npbaFA0cLl9zElFTz YdAxNOBUobm58bIRNWR6LseMsbpnar7KaxUcD3jAlpgOWj2d0J/1ZjaJb+l2vjlL Shtn/yU6hu1pq8Lpwmhom8ZpS7z//7JMXGkrNqxB9SVDoCANj/ItsDPpkrGAz8Lg T1oMl1y4U0SvSCudo/XJ037YU+WQLpL2qYoVLT/NGmi6j4nLmO4VOQ+MY/u8ynyd s4rHflNapz75mwzSmOma0yiS76JDBhKXVMN1iiAOaOqz16VixlQ= =t4Uf ——-END PGP SIGNATURE——-

I have a habit of building Tor Browser, for no good reason. Today I did it again.

Oh well, this is what Tor Browser 11.0a9 will look like and probably also close to what TB 11 will look like

About a week ago, Gus had a simple question: “is there an easy way to find the percentage of offline bridges with distribution mechanism = none?”. He asked if I'd maybe be interested in working on it, which of course I would.


I realized that there may be people coming here without technical knowledge of Tor and Onion services, an “HSDir” is a Tor node that has information about onion services, e.g. how to connect to them.
HSDirs that run a version of Tor without v2 onion support will not accept the information of a v2 onion. Which means, if all 6 of a v2 onion service's HSDirs don't understand v2, it will be impossible to access it.
You might want to see the How do onion services work? page to learn more.

I made a script* to track how many HSDirs run a version of tor that understands v2 onions. It runs every hour, downloads the current consensus, finds all relays that have the HSDir flag and checks their tor version. If the tor version is 0.4.[6-9] or or** it is counted as being “nonv2” otherwise it is counted as “v2”

This is what it looks like as a chart:


I have made yet another site! This time we're going inside the Tor network, with an onion service. Simple as day, http://r2uc5s7zoqhujl4lqcp3kkbicmp4qqvrzyondbdgobaqogmyvjzmvhid.onion allows you to stream Sintel or Glass Half (two Blender Open Movies, licensed under CC-BY 3.0/4.0).