[bitfolk] Terms and Conditions update (no actual changes in …

Top Page

Reply to this message
Author: Andy Smith
Date:  
To: users
Old-Topics: [bitfolk] Proposal: Security incidents postings
New-Topics: Re: [bitfolk] Proposal: Security incidents postings
Subject: [bitfolk] Terms and Conditions update (no actual changes in terms)
I think it's a great idea. Hearing what is actually going on in the real
world helps awareness for the rest of us sharing it. I reserve the right
to eat these words if it all turns out to be too depressing...!

Ross


From brendanpiater@??? Fri Dec 07 05:45:31 2012
Received: from mail-wg0-f54.google.com ([74.125.82.54])
    by mail.bitfolk.com with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16)
    (Exim 4.72) (envelope-from <brendanpiater@???>)
    id 1Tgqkc-0000wV-90
    for users@???; Fri, 07 Dec 2012 05:45:30 +0000
Received: by mail-wg0-f54.google.com with SMTP id fg15so65007wgb.21
    for <users@???>; Thu, 06 Dec 2012 21:45:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
    h=mime-version:sender:in-reply-to:references:from:date
    :x-google-sender-auth:message-id:subject:cc:content-type;
    bh=w3KRvlrIoWaahVptt8muHdDynFaijnTi3U8pMOM+lJ8=;
    b=qP+Lzu/+8l6nBeXqzVeArfSubodoY0tM8JXQ7n7KDxxz76ryTeQbWHdfUgc0TyhPEc
    w6++wR3elJBYn68WD1bnEbBSR4o0dFC9QHuFZsgC61wWC2kJONXhQY3mcLtHlSP5Vm8Y
    hV0puH+5vCsk0xteFhTSJ5UkvBD7zBD9312bAGaNdrvTWV/t0b0c4tdxtqH4MmeFLSxg
    X9bRHOyXv9YPvWYsfGhDKs59dzq86vNmUe/HHdUgGW8TjzpuNoYHH7dX5h5lYiyTgzXL
    buhS/X3BezzVXv5s5QtL8MFGMyRpEwe62nyDqSEN6sapCQwrZITJiuQLnwL+KmSoPWqi
    UtSA==
Received: by 10.180.80.201 with SMTP id t9mr6434837wix.0.1354859124535; Thu,
    06 Dec 2012 21:45:24 -0800 (PST)
MIME-Version: 1.0
Sender: brendanpiater@???
Received: by 10.216.32.200 with HTTP; Thu, 6 Dec 2012 21:44:54 -0800 (PST)
In-Reply-To: <50C17579.6020503@???>
References: <20121207021942.GT3867@???>
    <50C17579.6020503@???>
From: Brendan <deep.diving.spero@???>
Date: Fri, 7 Dec 2012 07:44:54 +0200
X-Google-Sender-Auth: PtB4FQRm1jGk2LtKJ3XDN6UrrcA
Message-ID: <CACMJ=b+cxyEggs9g-fG5++f8mNoWDiyzF2zCP4pez