288:
reasons. This seems only to be a good thing to do if you really want to make people stop contributing to
Knowledge. Use of proxy/vpn is globally increasing and you can't really expect people to disable a proxy or vpn for every little contribution, or them to make a appeal every time they get blocked for no reason. Legitimate users are not the intended targets, but it sure feels that way when it happens repeatedly. Some ain't even in any control of what vpn/proxy software that is run on the router their devices connects to. Sooner or later, legitimate users will just stop contributing instead. This applies to any use of shared IP. The risk of blocking legitimate users and the unnecessary difficulties it causes for them would be a lot less of a issue if you for example only blocked unregistered users and new accounts with less than X amount of accepted content. Most spammers etc. are not both logged in and have a record of good behavior, there's even a lesser chance of them making any appeals, and they could still be blocked at a per case basis if needed. Please unblock again, thank you. Plommespiser (talk) 13:59, 29 December 2017 (UTC)
315:: You appear to be suggesting we change our policy around VPNs and proxies. That's a reasonable position to take, but not one I, as the reviewing administrator, am able to accomplish alone. You'll need to suggest this as a policy change. All I can do is review your block and lift it, if you are not editing from a proxy or from a VPN. Unfortunately, you didn't make that claim (and in any case, didn't tell me what IP address you were using). As such, I'm afraid there's nothing more I can do for you here. You may wish to check out
31:
67:
134:
352:
the next time I receive a new shared IP? This have happened in the past and it seems that every time a VPN customer connects to a new server (a new server will likely be outside a earlier whitelisted IP range on
Knowledge) or by changing VPN provider he or she will get blocked again, despite being a
287:
While it's easy to understand why unregistered users behind a proxy/vpn/tor is blocked from making edits, it's not as easy to understand why you by default are still autoblocking long-term contributors, that are logged in, and that even have been unblocked earlier after making appeals for similar
358:
therefore can only make edits to my own talk page. I guess I rather leave it with this and stop contributing till someone (hopefully) understands that the current policy needs to be modernized to better meet a world where people are increasingly using a VPN or other types of shared IP addresses.
357:
I've been contributing to
Knowledge, mainly Norwegian, since before 2009 when I registered this account and I'm not much interested in repeatedly proving that I'm not a vandal. Even if I wanted to suggest a policy change I would not be able to because I'm blocked for simply using a shared IP and
340:
must have lost their head when they thought it was in
Wikipedias best interest to autoblock any accounts for simply using a shared IP, or to cite from the block message: "Since the web host acts like a proxy, because it hides your IP address, it has been blocked." and then additionally expecting
79:
is now open until 23.59 on Sunday, 10 December. All users who registered an account before
Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
344:
I appreciate your answer, but I understand that you're not able to lift a block of a VPN anyway and that I instead will have to submit a new appeal by using the "unblock ticket request system" and then answer a set of questions as if I had done something wrong. Then
107:
91:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose
341:
those users to read long guides or fill out tickets to appeal the totally unreasonable blocking. This will push users away, both from contributing content and making monetary donations.
182:
177:
240:
196:
121:
234:
355:
What's the point of spending so much time on whitelisting specific IP addresses instead of just whitelisting contributing accounts?
117:
100:
112:
156:
264:
38:
246:
141:
252:
367:
363:
328:
298:
228:
125:
47:
17:
88:
145:
353:
logged in long-time contributor. How can someone think this is in the best interest of
Knowledge?
359:
293:
75:
173:
84:
99:, editing restrictions, and other measures needed to maintain our editing environment. The
324:
316:
96:
92:
66:
46:
If you wish to start a new discussion or revive an old one, please do so on the
320:
149:
103:
describes the
Committee's roles and responsibilities in greater detail.
152:
lifted has been reviewed by an administrator, who declined the request.
222:
106:
If you wish to participate in the 2017 election, please review
25:
132:
348:
If the appeal is approved, will I risk getting autoblocked
302:
270:
258:
210:
206:
200:
191:
187:
169:
165:
161:
87:
is the panel of editors responsible for conducting the
336:
This is of course not your fault, but I must say that
8:
44:Do not edit the contents of this page.
7:
76:2017 Arbitration Committee elections
73:Hello, Plommespiser. Voting in the
60:ArbCom 2017 election voter message
24:
65:
29:
110:and submit your choices on the
1:
368:03:14, 30 December 2017 (UTC)
329:14:07, 29 December 2017 (UTC)
89:Knowledge arbitration process
126:18:42, 3 December 2017 (UTC)
388:
157:Plommespiser/Archives/2017
118:MediaWiki message delivery
292:Blocking administrator:
137:
18:User talk:Plommespiser
197:change block settings
136:
85:Arbitration Committee
42:of past discussions.
144:'s request to have
138:
101:arbitration policy
54:
53:
48:current talk page
379:
305:
276:
275:
274:
241:deleted contribs
225:
216:
214:
203:
185:
183:deleted contribs
135:
69:
33:
32:
26:
387:
386:
382:
381:
380:
378:
377:
376:
375:
374:
297:
226:
221:
220:
219:
204:
194:
180:
159:
133:
130:
129:
70:
62:
30:
22:
21:
20:
12:
11:
5:
385:
383:
373:
372:
371:
370:
346:
342:
313:Decline reason
310:
309:
308:
307:
279:
278:
277:
217:
131:
108:the candidates
71:
64:
63:
61:
58:
56:
52:
51:
34:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
384:
369:
365:
361:
356:
351:
347:
343:
339:
335:
334:
333:
332:
331:
330:
326:
322:
318:
314:
304:
300:
295:
291:
290:
289:
285:
283:
282:Block message
272:
269:
266:
263:
260:
257:
254:
251:
248:
247:nuke contribs
245:
242:
239:
236:
233:
230:
224:
218:
212:
208:
202:
198:
193:
189:
184:
179:
175:
171:
170:global blocks
167:
166:active blocks
163:
158:
155:
154:
153:
151:
147:
143:
128:
127:
123:
119:
115:
114:
109:
104:
102:
98:
94:
90:
86:
81:
78:
77:
68:
59:
57:
49:
45:
41:
40:
35:
28:
27:
19:
360:Plommespiser
354:
349:
337:
312:
311:
294:not provided
286:
281:
280:
267:
261:
255:
249:
243:
237:
231:
223:Plommespiser
192:creation log
142:blocked user
139:
111:
105:
82:
74:
72:
55:
43:
37:
113:voting page
36:This is an
265:block user
259:filter log
188:filter log
174:autoblocks
150:IP address
97:topic bans
271:block log
207:checkuser
162:block log
148:on their
146:autoblock
93:site bans
235:contribs
178:contribs
338:someone
317:WP:IPBE
201:unblock
39:archive
303:blocks
350:again
345:what?
321:Yamla
140:This
16:<
364:talk
325:talk
299:talk
253:logs
229:talk
122:talk
83:The
211:log
366:)
327:)
319:.
301:•
284::
205:•
199:•
195:•
190:•
186:•
181:•
176:•
172:•
168:•
164:•
124:)
116:.
95:,
362:(
323:(
306:)
296:(
273:)
268:·
262:·
256:·
250:·
244:·
238:·
232:·
227:(
215:)
213:)
209:(
160:(
120:(
50:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
