262:
203:
322:
will be reading this, but if you do, thanks for the unblock. Should you follow through and see what looks to you like me continuing to be insensitive, please don't hesitate to tell me so--I'm involved in an extremely uncomfortable discussion right now that I would rather not be in, and I don't know
60:
You can confirm that the IP address in
Brattleboro is my home by doing a DNS lookup on ksanti.fugue.com, and a whois on fugue.com, and looking at my user page, where I identify myself by name. Ksanti.fugue.com is my secondary name server, and is in the same /29 subnet as the address I do my editing
49:
At least one student, who probably also made edits from that netblock, was accused of sockpuppetry in the past, and didn't contest the accusation, so the accusation was upheld. It may have been correct--I don't know, because I don't know which student did it. What is clear though if you look back
103:
Even though I didn't sockpuppet, I realize that my actions did trigger the response--that it wasn't capricious. I didn't follow good wikipedia etiquette or even have the right attitude about what I was doing. Doing the research to figure out why I was blocked and what I should do about it has
100:. A person who is involved in the discussion should not be the person who chooses who participates in the discussion. I am not saying this was deliberate--the block occurred before YellowMonkey started participating in the debate. But in retrospect it seems kind of questionable.
42:. He is one of the principal teachers at Diamond Mountain, and I know that other students have edited his page while at Diamond Mountain, and their edits would have had the same goal: to correct the viewpoint pushing that's been going on that article for several years now.
143:
You said "I tried to correct this so that people wouldn't think I was sockpuppeting, but didn't get every instance." Could you point me to an example of you trying to correct it, as this would be quite strong evidence that you didn't intend to sock. — Martin
30:
I did some edits without being logged in before I figured out how not to get logged out when idle for a fairly brief period. I tried to correct this so that people wouldn't think I was sockpuppeting, but didn't get every
111:{{unblock|1=I didn't sockpuppet. I suspect evidence is weak, and that the underlying concern is viewpoint pushing (supporting detail on talk page). I was not viewpoint pushing--Jimmy Wales reviewed contested edit,
50:
at it is that I was not accused of sockpuppetry at the time, probably because I sound different than the students who were accused, and I was editing from my former home in Tucson, so from a different netblock.
104:
been instructive. I hope my improved understanding will mean that I will step on fewer toes in the future, and hopefully won't make anyone wonder whether or not I ought to be blocked.
53:
You can get some confirmation of where I've been editing from by doing a whois on the IP address I came from--it'll either be a comcast address--my home in
Brattleboro--or a
348:
Nice job. I personally don't have any objection to your marking the issue resolved. I guess we'll have to wait and see about the other editors.
323:
if I'm handling it appropriately (according to community norms) or not. If I'm not, I would very much like to hear that from you. It's on
108:
I tried to make this brief because it's boring, but if you are interested in more detail, visit the previous revisions of this page.
89:, the administrator who blocked me, asking what I did that led to the block and how I could correct it, and received no answer.
35:
302:
245:
332:
233:
189:
17:
131:
article: will try to be more low-key going forward. More on my talk page. Thanks for reading.}}
278:
134:
124:
97:
120:
93:
86:
219:
The blocking admin never bothered to even post a notice explaining the block. I'm willing to
57:
address. Valley
Telecom is the only ISP in Bowie, Arizona, and has a very small netblock.
353:
328:
315:
229:
185:
324:
169:
151:
357:
336:
193:
174:
156:
342:
319:
287:
220:
128:
71:
39:
261:
202:
349:
165:
147:
38:. The page I was editing that I am sure stimulated the controversy is
256:
197:
133:
127:, seems like COI. Nevertheless, I came on too strong with edits to
162:
I have asked the yellow monkey to comment on your request. — Martin
223:
as you claim and that you will be able to avoid it in the future.
27:
I didn't sockpuppet. It might have seemed that I did. Why?
96:, the administrator who blocked me, is participating in
181:
116:
112:
79:
75:
67:
54:
305:on this user after accepting the unblock request.
248:on this user after accepting the unblock request.
66:I wasn't pushing a viewpoint: today Jimmy Wales
8:
98:the debate that I think triggered the block
78:that I think triggered the block, and
85:No explanation of block: I contacted
7:
327:, under the Michael Roach heading.
24:
221:believe you that it was a mistake
260:
201:
1:
275:for the following reason(s):
216:for the following reason(s):
281:#1998472 lifted or expired.
269:Your request to be unblocked
210:Your request to be unblocked
70:I attempted to correct with
373:
259:
200:
358:23:44, 18 July 2010 (UTC)
337:04:22, 17 July 2010 (UTC)
194:17:26, 16 July 2010 (UTC)
175:12:40, 16 July 2010 (UTC)
157:12:08, 16 July 2010 (UTC)
298:Unblocking administrator
241:Unblocking administrator
136:File:Blnguyen banana.JPG
140:
121:Blocking administrator
92:Conflict of interest:
139:
72:my teacher's article
18:User talk:Abhayakara
300:: Please check for
285:Request handled by:
243:: Please check for
227:Request handled by:
68:noticed the problem
141:
125:involved in debate
312:
311:
307:
303:active autoblocks
255:
254:
250:
246:active autoblocks
173:
155:
115:the same problem
94:User:YellowMonkey
87:User:YellowMonkey
80:the reason I gave
40:my teacher's page
364:
314:I don't know if
306:
296:
292:
264:
257:
249:
239:
205:
198:
163:
145:
137:
36:Diamond Mountain
372:
371:
367:
366:
365:
363:
362:
361:
346:
316:User:Beeblebrox
301:
288:
244:
135:
76:the edit I made
22:
21:
20:
12:
11:
5:
370:
368:
345:
340:
310:
309:
277:
276:
265:
253:
252:
218:
217:
206:
178:
177:
106:
105:
101:
90:
83:
82:for making it.
63:
62:
58:
55:Valley Telecom
51:
46:
45:
44:
43:
32:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
369:
360:
359:
355:
351:
344:
343:Michael Roach
341:
339:
338:
334:
330:
326:
321:
320:User:Excirial
317:
308:
304:
299:
294:
293:
291:
286:
282:
280:
274:
270:
266:
263:
258:
251:
247:
242:
237:
235:
231:
228:
224:
222:
215:
211:
207:
204:
199:
196:
195:
191:
187:
183:
176:
171:
167:
161:
160:
159:
158:
153:
149:
138:
132:
130:
129:Michael Roach
126:
122:
118:
114:
109:
102:
99:
95:
91:
88:
84:
81:
77:
74:. Here is
73:
69:
65:
64:
59:
56:
52:
48:
47:
41:
37:
33:
29:
28:
26:
25:
19:
347:
313:
297:
295:
289:
284:
283:
272:
268:
267:
240:
238:
226:
225:
213:
209:
208:
180:Yes, here's
179:
142:
110:
107:
34:I study at
329:Abhayakara
230:Beeblebrox
186:Abhayakara
182:an example
279:Autoblock
271:has been
212:has been
31:instance.
290:Excirial
325:WP:BLPN
273:granted
214:granted
113:noticed
350:Yworo
123:also
117:I did
61:from.
16:<
354:talk
333:talk
234:talk
190:talk
170:talk
166:MSGJ
152:talk
148:MSGJ
119:.
318:or
356:)
335:)
236:)
192:)
184:.
168:·
150:·
352:(
331:(
232:(
188:(
172:)
164:(
154:)
146:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
