208:
26:
476:
looked at the generated HTML of one of our articles, you know that there are tons of elements you don't see in the wikicode, nor would we want to. That would be the right way to handle section redirects, imho, and then it wouldn't be so distracting having them at the top of a section. That's just my take; maybe I'll add something about it at
419:
Hi, BG (is that an okay moniker for you?). Good point about redirects; I support your addition to the explanatory note at MOS, and the revert is fine. I played around a bit to see if one could search for redirects from advanced search, and I'm not completely convinced one can't, but haven't found it
283:
When there are no inlinks to it, an anchor is unnecessary, and when there are just a couple, it's best to just adjust the wikilinks with the old section name to the new one, rather than embed an anchor in the target article, which makes a more complex section heading that many editors don't know how
475:
There's no reason the mediawiki software couldn't be enhanced to handle this in a clean way, with some new element, maybe #REDIRECTSECTION, that would be designed to follow a section header in the wikicode, and be interpreted into HTML with the requisite anchor in the right place; if you've ever
472:), but embedding it in a section header is very klugey imho and I don't favor doing that just because somebody somewhere on the internet might have a bookmark to it in their browser. Let them get redirected to the top of the page and then find their content on the page, and fix the bookmark.
52:
with credible content. Academics like to sneer at those characteristics, even as more and more of us acknowledge
Knowledge (XXG), support it, and use it in teaching. And why should we not warm to it? The rules of Knowledge (XXG) discourse are modeled after an ideal academy's.
375:. I think it is reasonable to retain anchors for old section names that existed for a long time and could be linked from off-wiki (especially in a page like this one that is the best reference source on its subject on the Web), so I will restore those anchors in
274:. I noticed that among other things, you added a couple of embedded anchors to section headings. Please note that embedded section anchors can be useful so that incoming links will still work after a heading name change, but they are best used when "
379:
but in substituted form. (If there is a guideline that explicitly contradicts my reasoning here, please point it out to me.) I agree with you that anchors shouldn't be added willy-nilly, but this isn't such a case.
451:(permanently moved; i.e., redirect) has been available on the internet for ages, I'm sure you've had the annoying experience of trying to visit a web page that you know exists, only to get a
328:.) While embedded section anchors have their uses, please don't add them willy-nilly, and most of all, please avoid adding them when there are no incoming links to the anchor at all. Thanks,
157:
120:. ... The main criticism against Knowledge (XXG) is that it is a free-for-all domain without any professional standards. Yet even if Knowledge (XXG) has to be used with caution,
428:
response (or any of the 30x responses) does not support a redirect from a URI + fragment, only from a URI (which may target a fragment, but not come from one). Neither does the
58:
149:
49:
306:
In the BibTeX case, anchors in two section headers were involved: one of them had no inlinks so wasn't needed, and the other had three: from
48:"Knowledge (XXG) may be the largest collaborative initiative in history and influences what people the world over know or think they know.
125:
101:
358:. That guideline must have changed, because the last time I read the guideline some years ago it didn't explicitly say to substitute the
57:. ... Why, then, does Knowledge (XXG) work? In theory, it should not. In practice, it seems to be a new paradigm of organization, whose
148:
in nature: make an edit, then wait for the next change, and if there is opposition, seek a compromise. A variant of this policy is the
221:
284:
to handle. Finally, when there are so many incoming links that it would be too time-consuming to fix them all, then please use the {{
141:
405:
because that anchor is the target of a couple of redirects. Perhaps you forgot to check whether the anchor was a redirect target?
373:
Knowledge (XXG) is on the World Wide Web, and there could be inlinks from anywhere on the Web, or in people's browser bookmarks
455:
error back from the site after they have done some internal re-org; we have all been there. Knowledge (XXG) handles that with
371:
However, I disagree with you that we can determine that there are no inlinks simply by searching
Knowledge (XXG), because
480:. Once again, thanks for your contributions to the discussion, and your improvements to the explanatory note. Cheers,
251:
121:
464:
230:
467:
or other codes; there never has been a way to do this server-side via an HTTP response or a HTML <head: -->
133:
402:
267:
50:
Its distinctive feature is the nonexpert, nonprofessional, noncertified, nonformal production of knowledge
460:
420:
at first blush. On the other hand, I don't agree with the part of having to deal with offline links with
129:
105:
54:
463:. However, the ability to find an internal section on a page (via #fragment) has never been part of the
153:
506:
406:
381:
109:
485:
333:
236:
145:
140:, 2014). ... Knowledge (XXG) encourages contributors to edit articles, and to reach consensus by
137:
355:
315:
290:
275:
116:, its aim is to propose a synthesis of existing knowledge and conflicting interpretations of
311:
303:
format, which causes the "undesirable behavior" that you can read about at the guideline.
232:
207:
183:
84:
477:
171:
59:
breezy anticredentialism tosses traditional hierarchies of knowledge production to the wind
362:
351:
285:
32:
456:
496:
481:
396:
345:
329:
433:
421:
36:
276:
164:, growing continuously, adapting to its environment and answering its critics."
468:
element, afaik. Yes, you can add a destination anchor (the <span id=...: -->
234:
514:
489:
414:
389:
337:
187:
161:
156:
in the policies, as it leads to discussion, which helps make articles better.
25:
318:. I adjusted the links in those three, and removed the embedded anchors from
88:
452:
448:
437:
425:
307:
117:
113:
68:
502:
459:, so that people off-wiki can still find our articles that have been
376:
319:
271:
126:
a consistent set of principles, rules, policies, and guidelines
124:. On the contrary, the Knowledge (XXG) community has developed
441:
237:
201:
158:
This collaborative culture, which is unique to
Knowledge (XXG)
354:}} a few days ago before you commented here, when I re-read
15:
505:, so I'll revert my re-addition of the anchor tags there.
55:
Arguments, not personal attacks or status, carry the day
324:
470:
tag can also do it; we don't have access to <a: -->
144:
in case of a disagreement. The process is typically
108:, Knowledge (XXG) has already become a piece of the
71:
Common
Knowledge?: An Ethnography of Knowledge (XXG)
322:. (To find inlinks, you can do an advanced search:
501:OK, you've convinced me at least for the case of
172:"Knowledge (XXG) and the ecosystem of knowledge"
350:Thanks for the message. I just learned about {{
98:
46:
403:I reverted another removal of an anchor by you
35:, and considers the distinction irrelevant on
245:This page has archives. Sections older than
102:a few core principles, plus detailed policies
8:
471:in the wikicode, as we do for <span: -->
444:spec for HTML but never accepted, afaik).
142:engaging in discussion on the "talk page"
100:"Thanks to a vibrant community united by
134:a community of thousands of contributors
170:Vandendorpe, Christian (October 2015).
277:there are many links to the old title
31:This user might or might not have an
7:
255:when more than 1 section is present.
176:Scholarly and Research Communication
20:
436:support for redirect-from has been
266:Hi, Biogeographist, and thanks for
14:
249:may be automatically archived by
154:bold editing is openly encouraged
206:
24:
1:
67:Allen, Barry (January 2017).
262:Embedded anchors in headings
368:. So now I know to do that.
162:community a living organism
150:BOLD, revert, discuss cycle
535:
288:}} or <span id=...: -->
515:12:49, 29 June 2024 (UTC)
490:02:10, 29 June 2024 (UTC)
469:technique; the <a: -->
415:15:19, 28 June 2024 (UTC)
390:15:10, 28 June 2024 (UTC)
338:21:56, 26 June 2024 (UTC)
188:10.22230/src.2015v6n3a201
510:
410:
385:
122:it is not a free-for-all
89:10.1215/0961754X-3692492
447:Although response code
424:from the internet. The
128:that have helped build
104:and safeguards against
252:Lowercase sigmabot III
166:
73:by Dariusz Jemielniak"
63:
289:style recommended at
106:trolls and vandalism
110:knowledge ecosystem
430:<link rel: -->
356:MOS:SECTIONANCHOR
316:RIS (file format)
291:MOS:SECTIONANCHOR
259:
258:
198:
197:
43:
42:
526:
500:
432:title element (
431:
400:
367:
361:
349:
327:
312:Refer (software)
302:
300:
299:
278:
268:your style fixes
254:
238:
210:
202:
192:
191:
93:
92:
77:Common Knowledge
28:
21:
16:
534:
533:
529:
528:
527:
525:
524:
523:
494:
440:as part of the
429:
394:
365:
359:
343:
323:
297:
296:
294:
264:
250:
239:
233:
215:
194:
169:
168:
95:
66:
65:
44:
37:Knowledge (XXG)
33:academic degree
12:
11:
5:
532:
530:
522:
521:
520:
519:
518:
517:
507:Biogeographist
473:
445:
407:Biogeographist
392:
382:Biogeographist
369:
298:{{anchor|Foo}}
263:
260:
257:
256:
244:
241:
240:
235:
231:
229:
226:
225:
217:
216:
211:
205:
196:
195:
97:
96:
45:
41:
40:
29:
19:
13:
10:
9:
6:
4:
3:
2:
531:
516:
512:
508:
504:
498:
493:
492:
491:
487:
483:
479:
474:
466:
462:
458:
454:
453:404 Not found
450:
446:
443:
439:
435:
427:
423:
418:
417:
416:
412:
408:
404:
398:
393:
391:
387:
383:
378:
374:
370:
364:
357:
353:
347:
342:
341:
340:
339:
335:
331:
326:
321:
317:
313:
309:
304:
292:
287:
281:
279:
273:
269:
261:
253:
248:
243:
242:
228:
227:
224:
223:
219:
218:
214:
209:
204:
203:
200:
193:
189:
185:
181:
177:
173:
165:
163:
159:
155:
151:
147:
143:
139:
135:
131:
127:
123:
119:
115:
111:
107:
103:
94:
90:
86:
82:
78:
74:
72:
62:
60:
56:
51:
38:
34:
30:
27:
23:
22:
18:
17:
422:fragment ids
372:
352:subst:anchor
305:
286:subst:anchor
282:
265:
246:
220:
212:
199:
179:
175:
167:
160:, makes the
99:
80:
76:
70:
64:
47:
182:(3): 1–10.
69:"Review of
293:, and not
138:Jemielniak
83:(1): 104.
457:redirects
325:like this
130:consensus
497:Mathglot
482:Mathglot
465:HTTP 30x
449:HTTP 301
438:proposed
434:link rel
426:HTTP 301
397:Mathglot
346:Mathglot
330:Mathglot
213:Archives
146:Hegelian
308:EndNote
118:reality
114:science
112:. Like
503:BibTeX
478:WP:VPI
377:BibTeX
363:anchor
320:BibTeX
314:, and
272:BibTeX
247:7 days
132:among
461:moved
511:talk
486:talk
411:talk
401:And
386:talk
334:talk
280:".
442:W3C
270:at
184:doi
85:doi
61:."
513:)
488:)
413:)
388:)
366:}}
360:{{
336:)
310:,
178:.
174:.
152::
81:23
79:.
75:.
509:(
499::
495:@
484:(
409:(
399::
395:@
384:(
348::
344:@
332:(
301:"
295:"
222:1
190:.
186::
180:6
136:(
91:.
87::
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
