File: <20220124-Email-Wizards-Agris-Re-Suspension>

  1. Return-Path: <austin@spindizzy.org>
  2. Delivered-To: agris@nuegia.net
  3. X-Spamd-Result: default: False [-4.10 / 15.00];  RCVD_VIA_SMTP_AUTH(0.00)[];
  4.   ARC_NA(0.00)[];  MID_RHS_MATCH_FROM(0.00)[];  FROM_HAS_DN(0.00)[];
  5.   RWL_MAILSPIKE_GOOD(0.00)[166.84.1.89:from];  MV_CASE(0.50)[];
  6.   MIME_GOOD(-0.10)[text/plain];
  7.   PREVIOUSLY_DELIVERED(0.00)[agris@nuegia.net];  REPLY(-4.00)[];
  8.   AUTH_NA(1.00)[];  TO_DN_NONE(0.00)[];  TO_MATCH_ENVRCPT_SOME(0.00)[];
  9.   RCPT_COUNT_TWO(0.00)[2];  DMARC_NA(0.00)[spindizzy.org];  R_SPF_NA(0.00)[no
  10.  SPF record];  FROM_EQ_ENVFROM(0.00)[];  R_DKIM_NA(0.00)[];
  11.   MIME_TRACE(0.00)[0:+];  ASN(0.00)[asn:2033, ipnet:166.84.0.0/16,
  12.  country:US];  RCVD_COUNT_TWO(0.00)[2];  RCVD_TLS_ALL(0.00)[];
  13.   RCVD_IN_DNSWL_HI(-1.50)[38.131.232.202:received,166.84.1.89:from,166.84.1.89:received]
  14. X-Rspamd-Queue-Id: 90536d4b
  15. X-Rspamd-Server: mail2
  16. X-SenderScore: 99
  17. Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by
  18.  mail2 (OpenSMTPD) with ESMTPS id 90536d4b
  19.  (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <agris@nuegia.net>; Mon, 24 Jan
  20.  2022 15:36:05 +0000 (UTC)
  21. Received: from [192.168.1.2] (unknown [38.131.232.202]) by
  22.  mailbackend.panix.com (Postfix) with ESMTPSA id 4JjDbQ6GmFz14kd; Mon, 24 Jan
  23.  2022 10:36:02 -0500 (EST)
  24. Subject: Re: Appeal
  25. From: Austin Dern <austin@spindizzy.org>
  26. In-Reply-To: <20220123190202.289d21b0@viridi.lan>
  27. Date: Mon, 24 Jan 2022 10:36:01 -0500
  28. Cc: wizzes@spindizzy.org
  29. Message-Id: <BB978969-C157-403A-9F8F-B1D3D1AFFA39@spindizzy.org>
  30. References: <890054E0-90AE-4BA6-8FBF-FC85AA79CCF0@spindizzy.org>
  31.  <20220123190202.289d21b0@viridi.lan>
  32. To: agris@nuegia.net
  33. X-Mailer: Apple Mail (2.3445.104.21)
  34. MIME-Version: 1.0
  35. Content-Transfer-Encoding: 8bit
  36. Content-Type: text/plain; charset=utf-8
  37. Hello, 
  38. 	We have received this and will read and consider it. This should not be taken as a promise to change any decisions; it is only a declaration that we will give it thought.
  39. 		Austin Dern
  40. > On Jan 23, 2022, at 10:02 PM, agris@nuegia.net wrote:
  41. > 
  42. > On Mon, 10 Jan 2022 23:50:26 -0500
  43. > Austin Dern <austin@spindizzy.org> wrote:
  44. > 
  45. >> Agris, 
  46. >> 
  47. >>        There are rooms on SpinDizzy that are accessible only to a
  48. >> few people on a short, specific list.  This is normal on SpinDizzy.
  49. >> Not everything is public.  People have and should have private rooms.
  50. >> Your specific interest in Voksa's rooms coincides with a conflict
  51. >> with Voksa that began outside SpinDizzy.  That conflict has no
  52. >> bearing on whether Voksa can decide who can enter his rooms.
  53. >> Further, you have shown no concern over any of the large number of
  54. >> *other* rooms you don't have access to.  To focus only on Voksa's
  55. >> establishes beyond doubt that the real problem is your relationship
  56. >> with Voksa, and not access to his rooms. Your pagemails to Patashu
  57. >> and Ping, and several hours of conversation with Ping, make clear you
  58. >> believe you can pester people into getting your way.  Further that
  59. >> you believe you can distract from the fundamental issue by focusing
  60. >> on access to Voksa's rooms.  In this light, your repeated insistence
  61. >> on forcing entry into Voksa's personal rooms constitutes ongoing
  62. >> harassment of him. You are banned from SpinDizzy.  Because you have
  63. >> already repeatedly attempted to circumvent this suspension by
  64. >> attempting to regain access without permission, it is not temporary.
  65. >> The Wizards, SpinDizzy
  66. >> 
  67. >> 
  68. > 
  69. > Thank you for explaining your reasoning and how you came to that
  70. > conclusion. I would like to appeal this judgement under the grounds
  71. > that this judgement was done improperly. This was done behind closed
  72. > doors, without the opportunity for me to defend myself or contest
  73. > untrue statements. There is also a lack of evidence supporting the
  74. > claims against and a poor understanding of events and the whole
  75. > situation really.
  76. > 
  77. > Firstly I want to ask if you actually read the pagemail you are
  78. > referring to because I feel that if you had, it would undermine a lot
  79. > of the conclusions that you have jumped to. I will quote it here:
  80. > 
  81. > 
  82. >> To Patashu: I am willing to say "I am sorry if I did anything to make
  83. >> you feel uncomfortable or to make you feel that I am harassing you" to
  84. >> Voksa
  85. >> 
  86. >> I want to make the following points:
  87. >> 
  88. >> 1. Make clear I am not here to ruin anybody's day. If it ruins
  89. >> anybody's day me simply being here that is unfair.
  90. >> 
  91. >> 2. make clear I am not here to Harass Voksa
  92. >> 
  93. >> 3. whatever the problem is on the other platform, I am not bringing it
  94. >> to SpinDizzy
  95. >> 
  96. >> 4. I have not done anthing on SpinDizzy to complement these claims
  97. >> against me.
  98. >> 
  99. >> 5. This issue was only brough to forefront when I couldn't enter spaces
  100. >> on SpinDizzy when all I ever did was say "hello".
  101. >> 
  102. >> 6. What happens ON SpinDizzy is the issue
  103. >> 
  104. >> 7. Whatever the staff want to suggest to resolve the issue I am ears
  105. >> open to.
  106. >> 
  107. >> 
  108. >> 
  109. >> additionally, my friend wrote the following questions they wanted me to
  110. >> relay:
  111. >> 
  112. >> 1 ) Not a threat
  113. >> - Agris is not here to ruin anyone's day.
  114. >> - He's not here or planning to break anyone's rules.
  115. >> 
  116. >> 2 ) Wants to enjoy the space
  117. >> - Agris wants to enjoy Spindizzy the same as he's done for as long as
  118. >> he's been here.
  119. >> - He doesn't want drama. It's the last thing he wants.
  120. >> 
  121. >> 3 ) Nature of the claim
  122. >> - Voksa is claiming Agris will harass them as the basis of their
  123. >> actions. He won't. If he has, he will not further.
  124. >> 
  125. >> 4 ) Nature of the actions
  126. >> - Agris was, from my understanding, a neutral party in SpinDizzy at the
  127. >> time of the event.
  128. >> - The ban on him is therefore an action on a neutral party (no
  129. >> provocation).
  130. >> - It must, then, be okay (not in the legal sense but netiquette) to do
  131. >> any administrative action up to banning without provocation.
  132. >> - New accounts do not have prior provocation. These actions can be
  133. >> taken, therefore, on any person based on name or whim.
  134. >> 
  135. >> 5 ) Question of time
  136. >> - Given (4), is this an indefinitely permissible action? Can it be
  137. >> repeated multiple times?
  138. >> - How long will Agris have to wait (none, week, year, indefinite) as a
  139. >> neutral party to gain the access a new account has?
  140. >> 
  141. >> I was encouraged to join your MUCK by Agris shortly before these events
  142. >> and was excited to. Given (4), I am not willing to join a MUCK that
  143. >> could potentially do this sort of thing to a brand spanking new user,
  144. >> without provocation.
  145. >> 
  146. >> I don't mind whatever else might happen or what judgments take place.
  147. >> 
  148. >> The way this was done has serious implications.
  149. >> 
  150. >> This isn't an isolated case, Agris is not special. That's entirely the
  151. >> problem and why it could so recklessly apply. Replace his name with
  152. >> anybody in the MUCK.
  153. >> 
  154. >> Kohrokho, Friend of Agris
  155. > 
  156. > I don't understand how this can be construed as so.
  157. > 
  158. > I want to be specific about the room being referred to. It was
  159. > not a private room. The room I am referring to "The Observatory". The
  160. > Observatory has no such whitelist/allowlist that you seem to be
  161. > insinuating on. It is a blacklist/denylist. It is also listed in the
  162. > 'whereare' command which from my understanding lists public
  163. > congregation locations. The Observatory is also listed in public
  164. > bulletin boards using the 'rpread' command as a location for public
  165. > gathering events, such the following log states:
  166. > 
  167. > 
  168. >> From: Voksa
  169. >> On: 2021-12-31 11:07:26
  170. >> This post will expire on: 2022-01-30 11:07:26 -- 20 days and 21 hours
  171. >> from now. Subject: Cosmic New Years
  172. >> 
  173. >> In an event of profound astronomical unlikelihood, the new years of
  174. >> planetary calendars across the galaxy have aligned! You may have other
  175. >> festivities to attend to, but if not, please join me in the
  176. >> observatory's telescope dome to celebrate the turning of the worlds.
  177. >> Surely there won't be any TEN THOUSAND YEAR CURSES unsealed.
  178. >> 
  179. >> There will be snacks.
  180. >> 
  181. >> Don't worry, I didn't choose the snacks myself.
  182. >> 
  183. >> Telescope dome: luge n10 w3, In, T
  184. >> Vaguely around server midnight on new years, and maybe a few hours
  185. >> before and after.
  186. >> 
  187. >> Done.
  188. > 
  189. > 
  190. > I was even invited by several people to attend. In addition to that,
  191. > The Observatory being a primary map location (N10 W3) on the main map.
  192. > We aren't talking about some obscure hidden location behind a bunch of
  193. > doors. This is something with primary coordinates. It is also pinned to
  194. > the wa list along side all the other public meeting places.
  195. > 
  196. > 
  197. >> Further, you have shown no concern over any of the large number of
  198. >> *other* rooms you don't have access to.
  199. > I was not aware of any other "rooms" during my exploration from which I
  200. > did not have access to. What rooms are you referring to?
  201. > 
  202. > I sent that earlier quoted email to Ping and Patashu. I connected and
  203. > messaged Ping if their stuff in storage was ok, because they had
  204. > explained in the previous night there was a fire.
  205. > 
  206. > Ping responded by telling me they just got back from dinner and "You
  207. > are no longer welcome on SpinDizzy". And that I would be imminently
  208. > disconnected while they look for the command, which they did.
  209. > 
  210. > Ping did not explain a reason for the ban and their language gave me
  211. > the understanding it was permanent. I did reconnect as a guest a
  212. > few times however the purpose of that was to exchange contact
  213. > information with acquaintances and people whom I was starting to build
  214. > friendships with. Also, to explain what was going on to them. I made
  215. > that clear. It is unfair to hold that against me, I am only human. The
  216. > way in which Ping did that was unreasonable. What would you do if you
  217. > were in that situation? Not try to re-establish contact with and reach
  218. > out to your friends? People are not robots. Other people's relationships
  219. > are not something you can just destroy like that.
  220. > 
  221. > I believe and this is just one of many reasons that Ping has it out for
  222. > me.
  223. > 
  224. > Not only that but Ping's actions and false statements to others during
  225. > this time destroyed my reputation and ostracized me. To the point some
  226. > people whom I previously talked to refused to exchange contact
  227. > information with me because they "trust Ping". Ping abusing their
  228. > community status and trust.
  229. > 
  230. > I connected one day, asked Ping if they got my letter, and the only
  231. > thing I was told was:
  232. > 
  233. >> Ping pages, "Hi. I just got back from dinner, or I'd have already taken
  234. >> care of this, but I got your pagemail from earlier, and also spoke with
  235. >> Patashu about the situation." to you.
  236. > 
  237. >> Ping pages, "You are no longer welcome on Spindizzy." to you.
  238. > 
  239. >> You page, "what?" to Ping.
  240. > 
  241. >> Ping pages, "Just what I said. I'll send you an email once I've written
  242. >> it, and you're welcome to disconnect now or wait until I figure out the
  243. >> appropriate commands to do it myself, but you are no longer welcome
  244. >> here." to you.
  245. > 
  246. > I was not given a reasoning for the ban. I was not given a duration of
  247. > the ban. I was not given a 'fair shake'. That was it. Zero to one
  248. > hundred.
  249. > 
  250. > I was never told there was a 'suspension' of any sort until much later
  251. > talking to Austin. Now your telling me i'm banned for reconnecting? You
  252. > can't just retroactively make up new rules now and have them apply to
  253. > the past. That's called a Ex post facto judgement. How is that fair?
  254. > Not only that but then you go and ban my friends from the muck too when
  255. > they get curious? What's up with that? Why? What did they do?
  256. > 
  257. > Anyways, when Ping did they were already spreading untrue rumors about
  258. > me and when that happened, well, that was all the assurance they
  259. > needed. Ping is a wizard; surely if they booted Agris that must mean
  260. > something is going on right? You'd think anyways. =(
  261. > 
  262. > I never did anything to Voksa. I never harassed them. Not on spindizzy.
  263. > Not off spindizzy. The only thing I did is walk in and say
  264. > "Hello!". And I've got logs of that too.
  265. > 
  266. > Speaking of logs, it was very difficult for me to write this letter and
  267. > begin to even address the accusations that were made against me,
  268. > non sequiturs, and the way they were. The lack of communication and the
  269. > lack of information which was withheld from me. I'm willing to go over
  270. > this but can you please at least give me a fair shake and show me the
  271. > logs, what your reasoning was, and actual evidence or proof of something
  272. > I did wrong so I can talk about that? Otherwise you asking me to prove
  273. > my innocence, rather than proving guilty. That's not fair and
  274. > demonstrates a clear bias against me.
  275. > 
  276. > Look, I'm not trying to put anyone on blast here. All I want, all I
  277. > ever wanted was to be given a fair shake. It says so right in your AUP.
  278. > I'm not here to get Voksa in trouble. I'm not here to throw Ping under
  279. > the bus. It's to resolve conflict. I just want to be treated fairly. If
  280. > someone doesn't want to talk to me that's fine but you need to figure
  281. > out a way to do it without dragging me through the mud.
  282. > 
  283. > When you ostracize people like that it has a social effect. Your you
  284. > outright banish people from events or boot them our of community
  285. > servers it gives people bad stigmas of that person.
  286. > 
  287. > If there's any doubt about that effect, not just on me, but on any of
  288. > my friends who might stop by, sign in as a guest and talk to anyone in
  289. > the server about Agris. You might even get banned by Ping, even just
  290. > off the bat, for being related to me. I'm sure that you'll see at least
  291. > one not-so-nice remark. This is the power administration has over social
  292. > relationships and it's not to be overlooked. It's a frightening power.
  293. > 
  294. > You have something really special here. I really liked the community
  295. > here and loved the kind of people I met. I go on
  296. > http://www.spindizzy.org/nwp/art/ and I see all that fantastic
  297. > close-knit community art and I think, wow. I want to be a part of that.
  298. > 
  299. > I still do want to be a part of that, but you've given me a hell of a
  300. > welcome =(. It's really a shame that people in such a niche have to be
  301. > terrible to each other.
  302. > 
  303. > Agris
  304. > 
  305. > 
  306. > Please reply to this message so I know it was received.