Hmmm, I've just been reading up a bit on TOR & I'm tempted to leave deploying it up to the OS (integration into network settings would be great!)... I'm not 100% sure whether or not the `torsocks` command would be enough to Torify Rhapsode, but Tor can certainly be configured as the system HTTPS proxy with Rhapsode respecting that!
Or you could mess with the DNS resolver to understand *.onion addresses? Could do this within Rhapsode but I think it'd be best done outside.
I certainly like the privacy aspect of TOR, but my bigger motivation is to let websites decide they can sacrifice human readable identifiers for decentralization.
The "Zooko's Triangle" theory I'm working from being that between decentralization, human readability, & uniqueness an identifier can only have two. (Unless you use blockchain!) While I'm generally happier leaving naming to the OS (I've got enough to do), I'm not happy with us all renting identifiers from ICANN.
This is a family server