127:. And an effectively infinite number of ways to work around a salting. Suppose you were tasked with guarding an infinite number of doors. If someone opens one of these doors, you can close it, and then you have two choices: You can put a lock on the door, or you can put a silent alarm on it. You look at the door's logs. It's been opened and closed four times now. The intruder is clearly interested in this one door. You look to your right and left and back and front and see, again, an effectively infinite number of doors that are nearly identical. Do you lock this door, pushing them toward all the others? Or do you set an alarm, quietly walk away from the door, and hope that they'll stick to just this door?
272:, especially if it is a URL or legal company name. Forcing them to use workarounds may well scare them off. There are also times that spambots for one reason or another lock on to a specific non-mainspace title; salting makes sense there too.However, spammers representing a person are among the most willing to try endless workarounds, to the extent that some people have made up new professional aliases just so they could use them as new salting workarounds.
24:
140:
is created. This has the added benefit of potentially getting ahead of attempts to bypass scrutiny (for instance, being notified on the creation of any page containing a particular substring). There is also the option of setting a log-only abuse filter to trip when a page matching either an exact
355:
has the most versatile set of options for preventing usage of a term in titles, and has the benefit of a "private" mode that can only be viewed by admins and a few other highly-trusted groups. If one is going to filter out a term, this is usually the best option, and this essay stops short of
415:
Some of the above can also be applied to protection of existing pages, particularly those outside of mainspace. In mainspace, the reader always comes first, but if an LTA has a fixation of vandalizing some low-visibilty projectspace page or spammy draft, and the vandalism is not particularly
343:
deter lower-skill LTAs. But, as with salting, there is an effectively infinite number of ways to bypass such filtering. Furthermore, the title blacklist is public, so, unlike some complex edit filters, this will not even be a difficult problem for the determined attacker to solve.
86:
There is a saying among criminals: "Locks keep an honest person honest." What they mean by this is that no lock will stop a sufficiently determined person from picking it... or, failing that, from taking an axe to the door or throwing a brick through the adjacent window.
135:
The obvious way to set a "silent alarm" is to watchlist a page. This works if you are very active and check your watchlist regularly. A more advanced approach is to set a "stalk bot" on IRC to notify you if a page matching a certain
122:
The logic for salting a page (or blacklisting a pattern) is often one of "super-deletion": Deleting the page hasn't been enough to deter a bad actor, thus we should make them unable to create it at all. The problem is that
278:
This one is a bit of a gamble, since if you guess wrong you may send the LTA scurrying for workarounds. But there definitely are cases where salting a page that an LTA is fixated on has deterred them, particularly with
192:
The key question is whether it seems more important to the repeat-creators to add their content at a specific title, or just anywhere they can. In the former case, salting may in fact be a good idea. Examples include:
331:
have been discussed together, but there are some differences with the blacklist. Most significantly, the blacklist matches regexes, meaning that you can counter specific workarounds (e.g.
94:
a page on
Knowledge (XXG) (restricting certain categories of user from creating it): Like a lock on one's front door, it will keep out curious good-faith parties and driveby vandals, but
234:. Sometimes someone might not notice the previous deletion, or might not realize its implications, and in these cases a salting may deter them.
43:
It contains the advice or opinions of one or more
Knowledge (XXG) contributors. This page is not an encyclopedia article, nor is it one of
215:
44:
432:
Source: A convicted armed robber who worked lighting for stage productions at the essayist's high school—said moments before he
36:
207:
Pages that are frequently created accidentally or due to a good-faith misunderstanding, such as generic file names (e.g.
481:
364:, it is often better to set filters to private log-only, and let attackers create pages and be instantly reported to
249:
458:
328:
99:
445:
310:
283:
LTAs, and particularly if title-blacklisting or edit-filtering is used rather than standard salting (see
253:
48:
377:
168:
111:
58:
107:
356:
condemning its use to the extent of salting and title blacklisting. However, as with the other two,
352:
103:
462:
292:
227:
209:
32:
433:
416:
obnoxious, it may often be better to leave the page unprotected and let it serve as a honeypot.
258:
436:
the lock to an off-limits area of the theater, using only a plastic plate he'd cut into thirds.
91:
365:
280:
244:
223:
149:
296:
154:
Salting actively makes LTAs harder to catch, without meaningfully hindering their abuse.
276:
Cases where an LTA does seem to have a fixation on a particular page and nothing else.
96:
salting will not keep out a determined attacker. It will only make them harder to find
475:
291:
Egregiously inappropriate titles, of the sort where creation and deletion need to be
256:), this is needed less often, but may occasionally come up in other namespaces (e.g.
51:. Some essays represent widespread norms; others only represent minority viewpoints.
268:. Corporate spammers often care about their spam subject's name being represented
306:
142:
269:
313:, even if you log-delete the protection, so there is some downside to this.
242:
A page that attracts vandalism from unrelated low-effort vandals, such as
248:, makes sense to salt. Since the restriction of article creation to
309:
with an LTA. However, note that all protected titles are listed at
137:
18:
125:
there is an effectively infinite number of potential titles
98:. The same is true, in most cases, for adding terms to the
358:
a sufficiently determined attacker will still always win
114:
that might be used if the original target is protected.
406:
399:
392:
385:
183:
176:
73:
66:
216:
Knowledge (XXG):Sockpuppet investigations/SOCKMASTER
361:
148:All of the "alarms" above stop working when an
141:title or a regex is created, and then setting
8:
284:
252:accounts (effectively semi-salting all of
110:page that tends to attract bad edits than
106:. It is easier to watch a specific known
102:, and in many cases for adding terms to
45:Knowledge (XXG)'s policies or guidelines
425:
202:want to keep an honest person honest.
7:
213:) or titles used as examples (e.g.
230:deletion but repeatedly recreated
145:to report to AIV if this happens.
49:thoroughly vetted by the community
14:
459:testwiki:User:Tamzin/salting test
37:Knowledge (XXG):Protection policy
360:. For this reason, as discussed
335:for an LTA creating variants of
222:Pages that have been deleted at
22:
16:Essay on editing Knowledge (XXG)
131:Silent alarms instead of locks
1:
301:Sometimes in these cases it
204:This applies to two cases:
118:Salting as "super-deletion"
498:
375:
166:
152:'s target page is salted.
56:
372:Other forms of protection
463:testwiki ProtectedTitles
311:Special:ProtectedTitles
482:Knowledge (XXG) essays
318:Further considerations
448:, to be more precise.
47:, as it has not been
305:be worth it to play
90:The same is true of
327:Above, salting and
329:title-blacklisting
323:Title blacklisting
240:Driveby vandalism.
457:See inclusion of
184:WP:ACTUALLYDOSALT
84:
83:
489:
466:
455:
449:
443:
437:
430:
409:
402:
395:
388:
338:
334:
198:When you really
186:
179:
76:
69:
26:
25:
19:
497:
496:
492:
491:
490:
488:
487:
486:
472:
471:
470:
469:
456:
452:
444:
440:
431:
427:
422:
413:
412:
405:
398:
391:
384:
380:
374:
353:The edit filter
350:
336:
332:
325:
320:
190:
189:
182:
175:
171:
165:
133:
120:
112:all other pages
104:the edit filter
100:title blacklist
80:
79:
72:
65:
61:
53:
52:
23:
17:
12:
11:
5:
495:
493:
485:
484:
474:
473:
468:
467:
450:
438:
424:
423:
421:
418:
411:
410:
407:WP:DONTPROTECT
403:
396:
389:
381:
376:
373:
370:
359:
349:
348:Edit-filtering
346:
342:
324:
321:
319:
316:
315:
314:
288:
273:
266:Corporate spam
263:
237:
236:
235:
220:
201:
188:
187:
180:
172:
167:
164:
157:
132:
129:
119:
116:
82:
81:
78:
77:
70:
62:
57:
54:
42:
41:
29:
27:
15:
13:
10:
9:
6:
4:
3:
2:
494:
483:
480:
479:
477:
464:
460:
454:
451:
447:
442:
439:
435:
434:latch-slipped
429:
426:
419:
417:
408:
404:
401:
397:
394:
390:
387:
383:
382:
379:
371:
369:
367:
363:
357:
354:
347:
345:
340:
330:
322:
317:
312:
308:
304:
300:
298:
294:
289:
286:
282:
277:
274:
271:
267:
264:
261:
260:
255:
251:
250:autoconfirmed
247:
246:
241:
238:
233:
232:in good faith
229:
225:
221:
218:
217:
212:
211:
206:
205:
203:
199:
196:
195:
194:
185:
181:
178:
174:
173:
170:
162:
159:When salting
158:
156:
155:
151:
146:
144:
139:
130:
128:
126:
117:
115:
113:
109:
105:
101:
97:
93:
88:
75:
71:
68:
64:
63:
60:
55:
50:
46:
40:
38:
34:
28:
21:
20:
453:
446:~2.7612 × 10
441:
428:
414:
393:WP:NOPROTECT
351:
326:
302:
290:
275:
265:
257:
243:
239:
231:
214:
210:File:pic.jpg
208:
197:
191:
177:WP:NOSALTYES
160:
153:
147:
134:
124:
121:
95:
89:
85:
30:
400:WP:DONTSEMI
307:Whac-a-Mole
293:log-deleted
163:a good idea
74:WP:DONTSALT
31:This is an
297:suppressed
281:competence
259:Draft:Poop
386:WP:NOSEMI
378:Shortcuts
270:literatim
254:mainspace
169:Shortcuts
67:WP:NOSALT
59:Shortcuts
476:Category
339:). This
108:honeypot
333:(f|ph)+
92:salting
35:on the
228:CSD A7
226:or by
143:DatBot
420:Notes
362:above
285:below
245:Pooop
138:regex
33:essay
279:low-
461:at
366:AIV
341:may
337:foo
303:may
295:or
224:AfD
150:LTA
478::
368:.
287:).
262:).
219:).
200:do
161:is
465:.
299:.
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.