|
Top-level
 The various groups were working together, even though there were some socio-technical rivalries among them. For example, people representing Tor said I2P's documentation sucked. I2P thought Tor's domain name system was poorly conceived. That sort of thing. But they all had common cause: prevent this obscure privacy problem. Then #Meta (at that time, #Facebook) showed up. 🧵 /3 2 comments
While Tor, I2P, GNU, and Namecoin were working an RFC through the IETF process, Facebook and Tor/Appelbaum broke away from the group. Why? Because they were bigger than the rest. Facebook was too important to wait for the piddly-little anonymizing projects, like I2P. Tor was just too popular. That was the basic argument. They broke off their own RFC, got it approved very quickly, and facebookcorewwwi.onion went live in 2016, complete with an HTTPS certificate. 🧵 /5 |
Gregory's Server
Facebook was looking into setting up their own Tor hidden service, what would eventually become facebookcorewwwi.onion (the fact that I can recall that URL is a BIG DEAL, ask me why later).
So they partnered with Tor, specifically the now infamous Jacob Appelbaum (a serial sexual abuser -- https://en.wikipedia.org/wiki/Jacob_Appelbaum#Allegations_of_sexual_misconduct)
Facebook's goal was to get IETF standardization so they could get a domain certificate for their .onion service. (Ask me why later, more nerdery).
🧵 /4
Facebook was looking into setting up their own Tor hidden service, what would eventually become facebookcorewwwi.onion (the fact that I can recall that URL is a BIG DEAL, ask me why later).
So they partnered with Tor, specifically the now infamous Jacob Appelbaum (a serial sexual abuser -- https://en.wikipedia.org/wiki/Jacob_Appelbaum#Allegations_of_sexual_misconduct)