1995-01-31 - Re: Frothing remailers - an immodest proposal

Header Data

From: Robert Rothenberg <rrothenb@ic.sunysb.edu>
To: kevin@elvis.wicat.com
Message Hash: 6f466060651e0e0b33a74e52dfcabbeaf967f9d655ad141ca89af0de4238a53a
Message ID: <199501312355.SAA11306@libws4.ic.sunysb.edu>
Reply To: <9501312152.AA10208@toad.com>
UTC Datetime: 1995-01-31 23:56:02 UTC
Raw Date: Tue, 31 Jan 95 15:56:02 PST

Raw message

From: Robert Rothenberg <rrothenb@ic.sunysb.edu>
Date: Tue, 31 Jan 95 15:56:02 PST
To: kevin@elvis.wicat.com
Subject: Re: Frothing remailers - an immodest proposal
In-Reply-To: <9501312152.AA10208@toad.com>
Message-ID: <199501312355.SAA11306@libws4.ic.sunysb.edu>
MIME-Version: 1.0
Content-Type: text/plain


: From kevin@elvis.wicat.com

Without quoting the entire message, I think I better solution, in terms of
ease to implement as well as conserving bandwidth would be to have a
sophisticated remailer script-language.

For instance, the script language could tell the remailer to check if a
site is on-line (perhaps within certain GMT hours or dates) and use the
next site if not available, or to randomly choose from a list of sites
the active ones, etc.

Maybe even have it work with a data haven? Mail the message to a data haven
and send another message to a remailer chain to pull the message from the
data haven and post the data (not flaws in this: don't want remailers getting
files from people's accounts and posting them to usenet etc.).

Seems like this is a "safer" solution that is more flexible then broadcasting
which remailers are active. Also allows for future add-ons like delays,
file-splitting, etc.





Thread