Just a recap - tags are case-sensitive. Let's make a rule for suggesting a tag - such that tags describing properties are always small-case ("red", "chrome", ...) and tags to artists begin (or contain - for specific callsigns) a capital letter ("Red", "Chrome", "mOdmate").

2300+ fonts, roughly 1 tag per font, 1/3 of them have external links (though not evenly distributed); every initial character has at least 15 fonts.

I agree that "chrome" could have its own tag.
It is a good Idea, actually, since many fonts evoke this feeling of highly polished metal (like "xenon2". for example, and many more).

On the other hand fonts like "056" (and "cd102menu" that started this discussion) simply transition between colors, in "cd102menu"'s case with a bit of 3D feel.

So what would you say about "083"? It is not exact science, but IMO it can fit to the polished chrome category no problem.
"089" is also a bit confusing, but looks shiny enough.
Sometimes it will be hard to decide, but as long as you find a trait that at least a few fonts share, you can have a category for it. Luckily your design enables each font to have multiple tags, so why not take advantage of it?

If you're concerned about explosion of the number of tags, thus limiting each font to as few as possible, I can relate to that. My preference however would be to be able to filter by any common characteristic that comes into mind. This approach already helped me to quickly locate fonts in the collection using the existing tags and a characteristic I remembered about them. The more tags we define, the more intuitive the filtering will become (IMHO).

@Zbeng: About the "gradient" tag - Gotta think this over. There's quite a lot of fonts like this, moreover, some have the 'chrome' effect (you know - that 90's look w/ reflection of (typically) blue sky and orange desert. Do you think distinguishing between those and add both "gradient" and "chrome"?

Keeping you busy... eh?
;-)

You're doing great!
There's no compendium for demo fonts like yours to be found.

2200+ fonts now (still some duplicate purge due, tho), each initial letter or digit has at least 14 fonts.
Soooo much fonts to convert ahead.

You can now see differences between two fonts by adding the "font2" argument in the URL.

Example: https://bmf.php5.cz/index.php?font=021&font2=022

note: the bitmap comparison is in color attributes, not RGB values.

2050 fonts (before the duplicate reduction), each letter or digit at least dozen fonts each.

Very Good idea. This will enable to keep better attributes from duplicates.
The hash function can be useful there (to apply on all characters instead of just 'A')
Consider also comparing palettes (may be ordered differently in duplicates)

I'm thinking of writing a page to compare two fonts (characters, their parameters, bitmaps) to address quite a few of potentially duplicate fonts.