Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Fri, Jun 24, 2005 01:45 AM UTC:
The broken links are caused by the wrong number of '../' in some relative
links. My problem with this page is a general problem I have with most of
Gilman's pages. It is that he tries to use the authority of this website
to give authority to his own naming of pieces. For example, this piece was
previously known as the 'Flying Dragon' by someone who used it before
Gilman, yet he goes ahead and calls it by another name. Furthermore, he
describes his reasons for this name in the passive voice, as though this
is the standard name for the piece, without taking responsibility for
creating the name himself. While I know that the name Caliph is his own
doing, the average reader here would think that the editors here have come
to a consensus on this name. That has not happened, and I think that any
page that Gilman writes should come with the disclaimer that he does not
represent anyone but himself.

I am supposed to be the Piececlopedia editor, and if these pages passed
through me, I would hold them to higher standards. But Gilman has never
passed any of his pages through me. Unfortunately, I don't have the time
to catch his submissions before other editors get to them.

Edit Form

Comment on the page Caliph

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.