If the
TorBrowser
takes too much RAM, then one thing to try on Debian-like Linux distribution Bash
console is the following:
Censorship lovers hate the Tor network and
Orwellian 1984
lovers, who want to
log all
visitors, sometimes block all Tor exit
relays,
computers, where traffic exits the Tor network to the plain WWW. At some
point "monkey-see, monkey-do", which leads to some otherwise reputable
hosting company network administrators block Tor exit relays. As of
2025_04_04 I have not understood, why they want to block part of the
Internet
that way, because it certainly does NOT save their company from Denial
of Service attacks, nor does it stop Russian/North-Korean hackers from
connecting to hacked servers from various corrupt regions of planet Earth. I
suspect that the blocking of Tor exit relays by otherwise reputable hosting
companies has something to do with the company not wanting to pay for various
employee working hours and legal fees for "explaining" to the state at court
that the state procecutor's claims about hosting company responsibility are
total nonsense from Information Technology point of view.
Now, what does that tell us about relying on monetary profit oriented
businesses to enforce human rights and freedom of speech and the right to
have a non-parasitical fruitful life? A company can always say that it's
cheaper for them to just comply with what ever the state/supermafia orders
rather than to stand up for even the constitution of the state/supermafia
itself. A specially nasty example are plain phone companies, which actively
facilitate eavesdropping by the state rather than sell/promote phone-call
encryption devices, which might have been very handy during the era of
"land-lines". I guess in year 2025 the solution might be some WiFi-enabled
Raspberry_Pi_zero that delegates the encryption and sound digitization part
to a microcontroller based sub-block so that the encryption keys never reach
the more easily back-doorable Raspberry_Pi_zero.
Tor is essentially a pipe that redirects an operating system port like the port
80 to a form Foo.onion:portnumber. Tor relay servers that are at public IP
addresses act as bounce servers, so there is no need to configure NAT (Network
Address Translation) at LAN routers, including home LAN WiFi routers. As of
2025_04_04 setting up Tor to redirect a
plain http server port
is as easy as editing a tor configuration file template
and running as plain user at Linux Bash console:
tor -f /full/path/to/the/custom/config/file.txt &
Unfortunately there might be a need for a cron job that runs something
like this once in every 5 minutes.
Just imagine an IoT implementation that