Comments
TallestSkil wrote
Is there a way to transplant the Tor protocols onto a different browser engine? Say, WebKit? Why hasn’t anyone forked Tor as a result of their behaviors?
BlackWinnerYoshi wrote
You would have to make the browser engine run through the Tor proxy (socks5://127.0.0.1:9050), including DNS requests to resolve onions. But why no one forked Tor? It's probably because Firefox and its Gecko browser engine aren't dead yet, but it might be in the future, so it's probably a good idea to use Pale Moon as a replacement, especially with the Proxy Privacy Ruler, which allows for applying the proxy only for private windows and/or certain domains. But they'll probably not do that and just accept to use Chromium and its Blink browser engine (I mean, Pale Moon is bad... but it's still better than what Chromium is trying to do).
GadgeteerZA wrote
That does not look like the correct link to the source? It is posts about the Tor Project standing up with rights of the LGBTQIA+ community. Where is the reference to any paedophile community? They're standing up for pride and privacy, which is a good thing for freedoms.
BlackWinnerYoshi wrote
Clearly, there are worse things the Tor Project did, such as removing a Clownflare discussion (notice how it doesn't exist on GitLab) and moving from Trac to GitLab, which caused disabling anonymous contributions. And let's not forget the Mozilla dependency…