377:. Incidentally, this system was created because (long, long ago) it was difficult to line up an editor in the right country and speaking the right language to communicate with law enforcement in a way that would be taken seriously. We knew it was important, but these kinds of contacts are best made by someone with an official role that can be verified by the agency, and ways to reach out to law enforcement in other jurisdictions is pretty important, too. Trust & Safety has developed a remarkably effective system over the ensuing years, far better than anything that volunteers could develop and maintain.
71:
21:
337:
141:
135:
As of June 2023, it has come to our attention that some messages sent to emergency@ wound up in our spam folder. This seems to be a backend issue with our email provider and we are currently reviewing the problem. If you do not receive a response to your message within 1 hour, please send a note to
358:
Thanks, I didn't realize that their response was that quick. FWIW, I was addressing prudence rather than obligation; if the threat is carried out, it is the perpetrator who is at fault, even if the victim failed to report it. I agree that if there is a rapid and effective procedure for getting the
301:
From a legal perspective a threat to kill or otherwise injure somebody, with rare exceptions, is assault, a criminal act and a serious matter, so there is no reason to wait until you are actually attacked before reporting it. Let the police sort out his intentions, and play safe.
343:
will be seen within minutes. They are the ones that know how and what to do, and have systems in place to deal with involving the authorities. We should not encourage our volunteers to get in the middle of that system and potentially cause confusion.
359:
details to the relevant authorities then a direct report is unnecessary. It might be helpful to note the timeframe in which T&S handles reports and that they will contact the relevant authorities when appropriate --
252:
but something like "however, very occasionally, technical issues happen - if you have not heard back with in one hour forward your email to ca@..." would I think minimise the confidence issues.
87:
34:
298:
I believe that the recommendations should include involving authorities when feasible. In the few cases where the poster intends to follow through, inaction would be dangerous.
49:
218:
has some solid advice in case this situation persists. Let me check in on this issue to see if it's been resolved. I'll let you know once I know more. Best,
196:
The answer will be yes, regardless. If the system is working then you will get a response within one hour, if it isn't then they will want to know that.
165:: Hello, have the technical issues on emergency@ been resolved? Do we still need to forward emails to ca@ if we don't hear back within 1 hour? Thanks.
53:
39:
57:
180:
120:
305:
The above applies to actual threats, not maledictions. Statements like "May you be struck by lightning" may violate
232:
Well, should we permanently change the instructions to include this "1-hour" rule? It's not confidence-inspiring.
99:
223:
151:
103:
386:
368:
353:
318:
287:
261:
243:
227:
205:
187:
155:
28:
283:
275:
257:
250:
This address is monitored around the clock. Staff will typically acknowledge your email immediately
219:
201:
162:
147:
349:
173:
105:
306:
325:
32:
for
Knowledge (XXG)'s procedural policy on the creation of new guidelines and policies. See
382:
364:
314:
101:
70:
279:
253:
238:
215:
197:
345:
211:
193:
166:
378:
374:
360:
310:
20:
233:
106:
64:
15:
38:
for recommendations regarding the creation and updating of
50:Knowledge (XXG):Responding to suicidal individuals
309:, but they should not be treated as threats. --
114:This page has archives. Sections older than
35:how to contribute to Knowledge (XXG) guidance
8:
54:Knowledge (XXG):Helping suicidal individuals
361:Shmuel (Seymour J.) Metz Username:Chatul
311:Shmuel (Seymour J.) Metz Username:Chatul
48:For similar proposals in the past, see:
249:
7:
324:That is not our job as volunteers.
58:Knowledge (XXG):Threats of violence
14:
331:paid to do that, and an email to
118:may be automatically archived by
335:
146:wikimedia.org. Thank you. Best,
139:
69:
19:
278:, is this still a problem? --
131:Note from WMF Trust and Safety
1:
387:01:54, 16 December 2023 (UTC)
369:16:31, 15 December 2023 (UTC)
354:16:07, 15 December 2023 (UTC)
319:14:27, 15 December 2023 (UTC)
294:Prudence: involve authorities
288:22:54, 23 August 2024 (UTC)
262:09:34, 23 August 2023 (UTC)
244:06:44, 23 August 2023 (UTC)
228:21:28, 22 August 2023 (UTC)
206:08:38, 21 August 2023 (UTC)
188:04:08, 21 August 2023 (UTC)
405:
373:That may be a good idea,
47:
336:
140:
156:15:57, 7 June 2023 (UTC)
121:Lowercase sigmabot III
40:policy and guideline
128:
127:
93:
92:
46:
45:
396:
342:
340:
339:
338:
326:Trust and Safety
248:It already says
185:
178:
171:
145:
144:
143:
142:
123:
107:
84:
83:
73:
65:
23:
16:
404:
403:
399:
398:
397:
395:
394:
393:
334:
332:
296:
181:
174:
167:
138:
137:
133:
119:
108:
102:
78:
61:
12:
11:
5:
402:
400:
392:
391:
390:
389:
371:
295:
292:
291:
290:
276:JKoerner (WMF)
272:
271:
270:
269:
268:
267:
266:
265:
264:
220:JKoerner (WMF)
163:JKoerner (WMF)
148:JKoerner (WMF)
132:
129:
126:
125:
113:
110:
109:
104:
100:
98:
95:
94:
91:
90:
80:
79:
74:
68:
44:
43:
24:
13:
10:
9:
6:
4:
3:
2:
401:
388:
384:
380:
376:
372:
370:
366:
362:
357:
356:
355:
351:
347:
341:wikimedia.org
330:
327:
323:
322:
321:
320:
316:
312:
308:
303:
299:
293:
289:
285:
281:
277:
273:
263:
259:
255:
251:
247:
246:
245:
242:
241:
237:
236:
231:
230:
229:
225:
221:
217:
213:
209:
208:
207:
203:
199:
195:
191:
190:
189:
186:
184:
179:
177:
172:
170:
164:
160:
159:
158:
157:
153:
149:
130:
122:
117:
112:
111:
97:
96:
89:
86:
85:
82:
81:
77:
72:
67:
66:
63:
59:
55:
51:
41:
37:
36:
31:
30:
25:
22:
18:
17:
328:
304:
300:
297:
239:
234:
182:
175:
168:
134:
115:
75:
62:
33:
27:
210:Hey there,
29:WP:PROPOSAL
280:asilvering
214:! I think
333:emergency
254:Thryduulf
216:Thryduulf
198:Thryduulf
88:Archive 1
346:Primefac
307:WP:CIVIL
212:SCP-2000
194:SCP-2000
116:400 days
76:Archives
379:Risker
375:Chatul
56:, and
42:pages.
383:talk
365:talk
350:talk
315:talk
284:talk
258:talk
224:talk
202:talk
152:talk
26:See
240:Eng
176:-20
169:SCP
385:)
367:)
352:)
329:is
317:)
286:)
260:)
226:)
204:)
183:00
154:)
136:ca
52:,
381:(
363:(
348:(
313:(
282:(
274:@
256:(
235:E
222:(
200:(
192:@
161:@
150:(
124:.
60:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
