operation without a public facing server

In the current version, replication uses CouchDB to copy entire databases. This requires a server with an IP address and possibly a DNS name. Since the metadata of public things is published via BitTorrent seeding, this should not be required.
What seems to be needed is a .torrent file fetcher that would download the .torrent file and add the meta data from the .torrent file to a local copy of the remote things public database - as if it were replicated via CouchDB.
This would probably be written as a external server (node.js?) spawned by CouchDB that would monitor the thing_tracker database. For things (SHA1 hash codes) that had no local metadata, it would request Deluge to download the .torrent file and possibly the attachments (data files) as well. When the torrent file is downloaded, update CouchDB and delete the torrent from Deluge.