freenode_logs/testimonies/01/email-log

Subject: [freenode.net #228714] AutoReply: Kline Error
From: "Freenode Support via RT" <kline@freenode.net>
Reply-To: kline@freenode.net
In-Reply-To: <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
References: <RT-Ticket-228714@Freenode>
 <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
Message-Id: <rt-4.2.8-27085-1608413289-1452.228714-16-0@Freenode>
Auto-Submitted: auto-replied
To: REDACTED
Content-Type: multipart/mixed;boundary=---------------------4672efbb68dc23aed4e28d391227b20c
Precedence: bulk
Date: Sat, 19 Dec 2020 21:28:09 +0000
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

-----------------------4672efbb68dc23aed4e28d391227b20c
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Greetings,

This message has been automatically generated in response to the
creation of a trouble ticket regarding:

       "Kline Error",

a summary of which appears at bottom of this message.

PLEASE READ CAREFULLY: We need your internet-routable IP address
to service all network ban (also known as  k-line or d-line)
issues. If you did not include this information in your original
request (quoted below), please take a moment now to point your
browser at http://myip.dk/ ... then reply to this email
with your IP address and hostname.
It's also helpful if you let us know what nick you were using at the
time.

If your request did not concern a network ban, there is no need to reply a=
t
this time.

Your ticket has been assigned an ID of [freenode.net #228714].

Please include the string:

         [freenode.net #228714]

in the subject line of all future correspondence about this issue.
To do so, you may reply to this message.

                        Thank you,
                        kline@freenode.net

------ Your request said -----------------------------------------
Hello,

My name is REDACTED. I maintain registrations to the nicks REDACTED=
 and REDACTED. I don't use Freenode much, however I have just been kli=
ned after registering the channel ##headpats. I believe I have been mistak=
en for an alt of Jacob Hrbek https://github.com/Kreyren.

I am indeed an acquaintance of this person, but once again I believe this =
kline has simply been made in error. For reference, I am currently staying=
 in a bed & breakfast in Horley however I did connect to freenode via the =
Washington DC server of Private Internet Access which will be commonplace =
given that I am a US expat on public wifi.

Thank you for your time; I am hopeful that this can be resolved promptly.

Sincerely,
REDACTED
REDACTED


-----------------------4672efbb68dc23aed4e28d391227b20c--
Return-Path: <bounces+rt@freenode.net>
X-Original-To: REDACTED
Delivered-To: REDACTED
Received: from mail.freenode.net (mail.freenode.net [163.172.127.19]) (using TLSv1.2 with
 cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by
 mailin014.protonmail.ch (Postfix) with ESMTPS id 8AF1C3000256 for
 <REDACTED>; Fri, 25 Dec 2020 15:40:38 +0000 (UTC)
Authentication-Results: mailin014.protonmail.ch; dmarc=pass (p=none dis=none)
 header.from=freenode.net
Authentication-Results: mailin014.protonmail.ch; spf=pass
 smtp.mailfrom=bounces+rt@freenode.net
Authentication-Results: mailin014.protonmail.ch; dkim=pass (1024-bit key)
 header.d=freenode.net header.i=@freenode.net header.b="GZGZalZE"
Dkim-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freenode.net; s=mail; t=1608910837;
 bh=TkqpC54jeam6q3v3pBaZBvYp/O3nxYTvA/rYmvAK97E=;
 h=Subject:From:Reply-To:In-Reply-To:References:To:CC:Date:From;
 b=GZGZalZEAtBxXZ7VFlNHP+ekyU/APz7YSeTlIyrgA8b+4lOswpTixXfnUJq5YfcUs
  UzMzOfpR/BJU++MDyarEGZY3zAcZrB2dKhu+s4gVIR6s9LpBi/10lFfZ6QHMRA/GdZ
  equ1qpuNOPE4nfN2FKhOeGl8Mr080oWU1J5iKdTo=
Subject: [freenode.net #228714] Kline Error
From: "Christian via RT" <kline@freenode.net>
Reply-To: kline@freenode.net
In-Reply-To: <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
References: <RT-Ticket-228714@Freenode>
 <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
Message-Id: <rt-4.2.8-27085-1608910837-530.228714-6-0@Freenode>
X-Rt-Loop-Prevention: freenode.net
X-Rt-Ticket: freenode.net #228714
X-Managed-By: RT 4.2.8 (http://www.bestpractical.com/rt/)
X-Rt-Originator: fuchs@freenode.net
To: REDACTED
Cc: tickets@support.freenode.net
Content-Type: multipart/mixed;boundary=---------------------e06232cb4e939a73db6559358baaf4d2
X-Rt-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 25 Dec 2020 15:40:37 +0000
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Pm-Spam: [snip hash]
X-Pm-Origin: external
X-Pm-Transfer-Encryption: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
X-Pm-Content-Encryption: on-delivery
X-Pm-Spamscore: 0
X-Pm-Spam-Action: dunno

-----------------------e06232cb4e939a73db6559358baaf4d2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Hi,

as per the discussion on IRC, the freeze will stay in place.
Have a nice day.

--
Kind regards,

Christian  (Fuchs on freenode)

-----------------------e06232cb4e939a73db6559358baaf4d2--
X-Pm-Origin: internal
X-Pm-Content-Encryption: on-compose
Subject: Re: [freenode.net #228714] [freenode.net #228715] Kline/Permanent Nickname
 Freeze Error
To: kline@freenode.net <kline@freenode.net>
From: REDACTED <REDACTED>
Date: Sat, 26 Dec 2020 01:15:16 +0000
Mime-Version: 1.0
Content-Type: multipart/mixed;boundary=---------------------e98c0e509373f23c644b3c41330d5226
X-Attached: anime channel 1.jpg
X-Attached: anime channel 2.jpg
X-Attached: anime channel 3.jpg
X-Attached: private messages between me and the person I was mistaken for.png
X-Attached: channel i registered before being erroneously klined.jpg
X-Attached: freenode channel conversation.jpg
X-Attached: query conversation.jpg
X-Attached: Discord conversation.jpg
Message-Id: <Recieg3EBaG3S4JENhn-6ipq5gd7xiKH8E5E5LIg0_zZnKe6jjr59rTJeJunmH9vZz7sXxj8Hn0XqDlcwwG3_Xqbij0Yaf2Yf8mNX8g5r9E=@protonmail.com>
X-Pm-Recipient-Authentication: kline%40freenode.net=none
X-Pm-Recipient-Encryption: kline%40freenode.net=none

-----------------------e98c0e509373f23c644b3c41330d5226
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Hello Christian,

I didn't understand my conversation with MerryFoxmas on IRC but I did not =
agree to anything nor did I consent to being treated that way. I have atta=
ched logs of that conversation to this email. I would prefer communication=
 via email in the future as I'm disabled and it takes me a while to gather=
 my thoughts.

I was made very uncomfortable by my conversation with MerryFoxmas. It is d=
ownright abusive to decline a request to be polite and refrain from gaslig=
hting. I was left shaking. [snip - invades kreyren's personal life]

Now, can we please just be respectful and focus on the matter at hand?

Despite my displeasure with the rude nature of my earlier conversation wit=
h MerryFoxmas, I would like to supplement that conversation with the fact =
that myself (REDACTED) and the person who had been initially klined (kreyren=
) are not quite in all of the same channels. We are both former members of=
 the Free Software Foundation and we both use linux/emacs, but I have join=
ed some channels related to MacOS and I can safely assume kreyren has not.=
 I'd also like to join #freebsd, but I was banned before I had much of an =
opportunity to explore Freenode. I understand how the overlap in our chann=
els (and interests) may have caused confusion, but please be patient with =
me in getting to the bottom of this misunderstanding.

Please take a look at our message history in the freenode channel #anime, =
where on December 5th I was sexually harassed by kreyren (KREYREEN) and th=
ey were banned but I (REDACTED) was not. I have attached screenshots of that=
 public conversation for your easier reference. I can provide more extensi=
ve logs if necessary.

I repeat that my main freenode nickname, REDACTED, was frozen in error. I ha=
ve attached even more proof to this email. Some of this proof includes sen=
sitive data. Please be respectful of me.

I'm trans and REDACTED is what I am planning to change my name to after I fi=
nish my honeymoon, so maintaining access to the nickname "REDACTED" is impor=
tant for me. REDACTED is my main nickname and is not an alt.

If you are still not satisfied, I could show some photo ID?

Kind regards,
REDACTED (REDACTED on freenode)
REDACTED

P.S. I can see that kreyren did not have his nickname frozen but I am the =
one getting the short end of the stick even though I am the one acting mor=
e like a normal human being, what's up with that...?

P.S.S. What is going to happen to the ##headpats channel that I registered=
 at right before I was erroneously klined?
=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original M=
essage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Friday, December 25, 2020 4:40 PM, Christian via RT <kline@freenode.net=
> wrote:

> Hi,
>
> as per the discussion on IRC, the freeze will stay in place.
> Have a nice day.
>
> ------------------------------------------------------------------------=
-----------
>
> Kind regards,
>
> Christian (Fuchs on freenode)


-----------------------e98c0e509373f23c644b3c41330d5226
Content-Type: image/jpeg; filename="anime channel 1.jpg"; name="anime channel 1.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="anime channel 1.jpg"; name="anime channel 1.jpg"

[snip 60K lines of hash]
-----------------------e98c0e509373f23c644b3c41330d5226--
Return-Path: <bounces+rt@freenode.net>
X-Original-To: REDACTED
Delivered-To: REDACTED
Received: from mail.freenode.net (mail.freenode.net [163.172.127.19]) (using TLSv1.2 with
 cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by
 mailin007.protonmail.ch (Postfix) with ESMTPS id A5E333000266 for
 <REDACTED>; Sat, 26 Dec 2020 15:27:02 +0000 (UTC)
Authentication-Results: mailin007.protonmail.ch; dmarc=pass (p=none dis=none)
 header.from=freenode.net
Authentication-Results: mailin007.protonmail.ch; spf=pass
 smtp.mailfrom=bounces+rt@freenode.net
Authentication-Results: mailin007.protonmail.ch; dkim=pass (1024-bit key)
 header.d=freenode.net header.i=@freenode.net header.b="JUfk8lp7"
Dkim-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freenode.net; s=mail; t=1608996422;
 bh=BwN0Qi9BcFAt9gCLHw3bHSnjzCBTe+g+NAoz/jMTMw0=;
 h=Subject:From:Reply-To:In-Reply-To:References:To:CC:Date:From;
 b=JUfk8lp7NZR7+vmyzIP/pJamGT1T18ktsB2b+R4938FzjYldnD+0qRYg8++Ha6lsB
  SwdI80tOoPsCFUAkauF5wTh8EyLEXfvqPjwYknMr6WMC1UB81Q664t3qD1tuIc26Sd
  kiRxar6uC+rBVleOzlI9IXDQp960jhKYE6bxAps4=
Subject: [freenode.net #228714] Kline Error
From: "Christian via RT" <kline@freenode.net>
Reply-To: kline@freenode.net
In-Reply-To: <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
References: <RT-Ticket-228714@Freenode>
 <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
Message-Id: <rt-4.2.8-27085-1608996421-830.228714-6-0@Freenode>
X-Rt-Loop-Prevention: freenode.net
X-Rt-Ticket: freenode.net #228714
X-Managed-By: RT 4.2.8 (http://www.bestpractical.com/rt/)
X-Rt-Originator: fuchs@freenode.net
To: REDACTED
Cc: tickets@support.freenode.net
Content-Type: multipart/mixed;boundary=---------------------260053adedcb68d6e4fca6460ceeb575
X-Rt-Original-Encoding: utf-8
Precedence: bulk
Date: Sat, 26 Dec 2020 15:27:02 +0000
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Pm-Spam: [snip hash]
X-Pm-Origin: external
X-Pm-Transfer-Encryption: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
X-Pm-Content-Encryption: on-delivery
X-Pm-Spamscore: 0
X-Pm-Spam-Action: dunno

-----------------------260053adedcb68d6e4fca6460ceeb575
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Hello REDACTED,

freenode staff can't and won't act on third party provided logs, as these =
can easily be forged or manipulated. Therefore we have to rely on what we =
saw and think. As per that, and as per the channel list and behaviour, plu=
s the information available to you, we decided that the account was used f=
or ban evasion and froze it, and will keep it frozen.

As for the channel: please note that freenode is a network for free / open=
 source software and peer directed projects (https://freenode.net/philosop=
hy). None of the channels you mentioned, including the one you created, se=
em to be terribly on topic (https://freenode.net/policies#on-topic-use) fo=
r our network. Per that, and as you unfortunately don't seem to feel welco=
me on our network, I suggest you open the channel on a network which is mo=
re appropriate for that kind of channel.  https://www.netsplit.de has a go=
od overview over various networks and their content / purpose.


Kind regards,

Christian  (Fuchs on freenode)

-----------------------260053adedcb68d6e4fca6460ceeb575--
In-Reply-To: <rt-4.2.8-27085-1608996421-830.228714-6-0@Freenode>
References: <RT-Ticket-228714@Freenode>
 <n3JIe9_g4mJOIzWs97vRxLtcIrRuQkTygUqXgGkY1ry1pYzli2VxaqZ0Yq11RHmItxdZRwXuV3zVpTuo5Voihoo7f7RfsuRmskcLu65ouSs=@protonmail.com>
 <rt-4.2.8-27085-1608996421-830.228714-6-0@Freenode>
X-Pm-Origin: internal
X-Pm-Content-Encryption: on-compose
Subject: Re: [freenode.net #228714] Kline Error
To: kline@freenode.net <kline@freenode.net>
From: REDACTED <REDACTED>
Date: Sat, 26 Dec 2020 16:11:45 +0000
Mime-Version: 1.0
Content-Type: multipart/mixed;boundary=---------------------b7c0a9c600f7d76b5f00a75e4e1e343a
Message-Id: <Q9U9UyrIygm1XDOxSAc5mTASCR7pnJOSN7xLqjm501ng1d-QRZ6i6bqkeW0XInbMw17uj8qHvZFjYurcwi3-TA_SAAPMqJrQ-zizvmSLkqI=@protonmail.com>
X-Pm-Recipient-Authentication: kline%40freenode.net=none
X-Pm-Recipient-Encryption: kline%40freenode.net=none

-----------------------b7c0a9c600f7d76b5f00a75e4e1e343a
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Hello Christian,

Thank you for your detailed reply and thank you for being respectful.

You mention that freenode staff previously decided that my main nickname w=
as used for ban evasion. Is that still the consensus? Or is there simply a=
 policy on freenode to keep permanent nickname freezes in place even when =
they were made in error?

Some of the channels I talked about were #fsf, #linux, #emacs, and #freebs=
d. Are those not on topic projects?

It is understandable that I currently feel unwelcome on freenode, given th=
at my experience so far has consisted of being sexually harassed and then =
permanently banned within mere days of innocent use. However, the freenode=
 server currently functions as crucial infrastructure for projects such as=
 the ones I mentioned, and I care about those projects.

I personally believe that it would behoove the growth of such projects if =
those responsible for managing said infrastructure were to adhere to a cer=
tain standard of intellectual honesty and accountability, rather than perm=
anently exclude hopeful participants in open source projects over regretta=
ble situations like mine. What do you think?

Kind regards,
REDACTED
REDACTED

P.S. Thank you for the link; it has educated me somewhat on the way IRC wo=
rks.

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original M=
essage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Saturday, December 26, 2020 4:27 PM, Christian via RT <kline@freenode.n=
et> wrote:

> Hello REDACTED,
>
> freenode staff can't and won't act on third party provided logs, as thes=
e can easily be forged or manipulated. Therefore we have to rely on what w=
e saw and think. As per that, and as per the channel list and behaviour, p=
lus the information available to you, we decided that the account was used=
 for ban evasion and froze it, and will keep it frozen.
>
> As for the channel: please note that freenode is a network for free / op=
en source software and peer directed projects (https://freenode.net/philos=
ophy). None of the channels you mentioned, including the one you created, =
seem to be terribly on topic (https://freenode.net/policies#on-topic-use) =
for our network. Per that, and as you unfortunately don't seem to feel wel=
come on our network, I suggest you open the channel on a network which is =
more appropriate for that kind of channel. https://www.netsplit.de has a g=
ood overview over various networks and their content / purpose.
>
> Kind regards,
>
> Christian (Fuchs on freenode)


-----------------------b7c0a9c600f7d76b5f00a75e4e1e343a--
In-Reply-To: <rt-4.2.8-27085-1608413452-396.228715-16-0@Freenode>
References: <RT-Ticket-228715@Freenode>
 <oGZZLxlUw-h7S99aPgwfIBDsLRI-nOwgWxQkNJ8XxGMDcE7bUfUtmSqTQtaGvZmhqiKfNnf-SDTQ--tKFDyc7LgD-WhcuwUXP0TTitAIVSA=@protonmail.com>
 <rt-4.2.8-27085-1608413452-396.228715-16-0@Freenode>
X-Pm-Origin: internal
X-Pm-Content-Encryption: on-compose
Subject: Re: [freenode.net #228715] AutoReply: Kline Error
To: kline@freenode.net <kline@freenode.net>
From: REDACTED <REDACTED>
Date: Fri, 25 Dec 2020 15:12:56 +0000
Mime-Version: 1.0
Content-Type: multipart/mixed;boundary=---------------------879fe01ed3e11230df9c35fd7390d3e3
Message-Id: <kj3EBKJpNWgNdKV4s8ia7puypR4dKcHfYCNEjOzzxQ-aEN5jRiqh_iCFj2LPYw2ltNLtZorVKHjlYyxuTztpFP27c5HyIGakGLGiEz6xtsE=@protonmail.com>
X-Pm-Recipient-Authentication: kline%40freenode.net=none
X-Pm-Recipient-Encryption: kline%40freenode.net=none

-----------------------879fe01ed3e11230df9c35fd7390d3e3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Greetings,

I still have not received a response. However it seems that I am no longer=
 klined and my nick is frozen. What is going on?

Sincerely,
REDACTED
REDACTED

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original M=
essage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Saturday, December 19, 2020 10:30 PM, Freenode Support via RT <kline@fr=
eenode.net> wrote:

> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
>
> "Kline Error",
>
> a summary of which appears at bottom of this message.
>
> PLEASE READ CAREFULLY: We need your internet-routable IP address
> to service all network ban (also known as k-line or d-line)
> issues. If you did not include this information in your original
> request (quoted below), please take a moment now to point your
> browser at http://myip.dk/ ... then reply to this email
> with your IP address and hostname.
> It's also helpful if you let us know what nick you were using at the
> time.
>
> If your request did not concern a network ban, there is no need to reply=
 at
> this time.
>
> Your ticket has been assigned an ID of [freenode.net #228715].
>
> Please include the string:
>
> [freenode.net #228715]
>
> in the subject line of all future correspondence about this issue.
> To do so, you may reply to this message.
>
> Thank you,
> kline@freenode.net
>
> ------ Your request said -----------------------------------------
> Hello,
>
> My name is REDACTED. I maintain registrations to the nicks =
REDACTED and REDACTED. I don't use Freenode much, however I have just been k=
lined after registering the channel ##headpats. I believe I have been mist=
aken for an alt of Jacob Hrbek https://github.com/Kreyren.
>
> I am indeed an acquaintance of this person, but once again I believe thi=
s kline has simply been made in error. For reference, I am currently stayi=
ng in a bed & breakfast in Horley however I did connect to freenode via th=
e Washington DC server of Private Internet Access which will be commonplac=
e given that I am a US expat on public wifi.
>
> Thank you for your time; I am hopeful that this can be resolved promptly=
.
>
> Sincerely,
> REDACTED
> REDACTED

>
> Addendum: Sending this to klines@freenode.net after initially emailing k=
line@freenode.net as it seems like I may have emailed the incorrect addres=
s [freenode.net #228714]


-----------------------879fe01ed3e11230df9c35fd7390d3e3--