Network based systems

Twitter launches its website on the Tor network


Twitter has launched its website on the Tor network (The Onion Router) according to an announcement made by software developer and internet security evangelist Alec Muffett on Twitter after midnight today.

In the past, Muffet has helped organizations like The New York Times, Wikipedia, and BBC News build services on the Tor network. According to him, he also helped Twitter engineers adopt the Tor network. Twitter has updated its list of supported browsers to include the Tor network and browser. It is accessible on the Tor network via: https://twitter3e4tixl4xyajtrzo62zg5vztmjuricljdp2c5kshju4avyoid.onion.

The company’s move comes at a time when the Russian government has banned access to sites like Twitter, Facebook and some news platforms in an apparent attempt to cut off domestic audiences from news and opinions from around the world.

While you could already access the normal Twitter website through the Tor network, the new .onion domain is only accessible through the Tor network and browser. Additionally, since the site is now on the Tor network, there is no need for traffic to be routed through a Tor exit node.

This means that the user and the web server they use are anonymized. Otherwise, user traffic is redirected through Tor relays before exiting the network through an exit node.

It also means the potential for malicious Tor exit nodes is mitigated, meaning users can mostly bypass national website blocks. According to Muffet’s blog, if you type in the exact .onion address of a website, you are guaranteed to connect to the actual website, or you won’t connect to anything at all.

If you’ve used the Tor network to browse regular websites, you may have noticed that they often require users to go through multiple CAPTCHA codes, and sometimes don’t work at all, displaying the message “Our systems have detected unusual traffic from your computer network. Please try your request again later.

This is based on the IP reputation of your exit node. Having a service built on Tor also alleviates this problem.

Source link