There are over 3500 results for tempest shadow, -broken horn — some of which legitimately feature only intact horns or no horn at all (eg. humanized) and also some of which are just, IMO, inadequately tagged.

Of course, even though the character's official design has a broken horn, it wouldn't be appropriate to make her character tag imply it. But, is it also generally regarded as unnecessary?

Is there any faster way to go about mass-tagging and also avoid looking like a tag crusade? At an optimistic 5 to 10 seconds to view, confirm, and tag a post, that's a mathematically-convenient 5 to 10 hours of straight, unrelenting tagging.

@971384265If you see images where their real name is exposed, please report those images for Rule #8, because nothing's changed in their indication to us that they want to remain anonymous.

Noted; but I suppose I wasn't clear, that unless I'm remembering a dream or mis-remembering a site other than Derpibooru, their works as a whole turned up in a search for artist:(their name) (not just a specific image or two) when at another time some weeks before, and again some weeks after, they only turn up for artist:(php).

Sorry that I can't be more specific or definite; I just wanted to mention it in case the people who know how the site works behind the scenes might be able to make sense of it.

Either I'm going crazy, or I've seen a PHP (artist:php27) revert back and forth between being a PHP and using their original artist tag(s) over the past, I dunno, month or two. Now, maybe the artist really is flip-flopping on this decision or maybe I really am going crazy, but it seems possible there's a bug (or maybe some kind of outdated server cache).

It's not like I continually lurk their tag so unfortunately I can't give a better idea of the time frame; their art has just come up in searches I've done now and then and I've noticed at times they're a PHP and at times it used their name.

OK, just to get it out of the way, the obvious suggestion then is an option or "field selector" to search only images' literal tags (or if the back end works the opposite way: search only unaliased tags).

But, what caused my original confusion is a relative lack of clarity. This leads me to several feature suggestions:

For example, when you search for a specific tag which is aliased to another, it says so and shows what it is on the search page. How about, an expandable section (like is already used for "Implied by") which gives a list of all tags matched by a nonliteral search (eg. wildcard or fuzzy)? For bonus points, it could incorporate small explanations like "X because it is aliased from Y (which matches)" or "Y which aliases to X".

Furthermore, on the image page itself, nothing indicates why it was a search result. Admittedly, it's pretty self-evident for non-aliased tag matches and most if not all field searches, but still, a feature which highlights which tag(s) and/or field(s) matched the search would be cool. In particular, if an aliased tag is part of the match, it ought to be represented in the image's list of tags (perhaps in the same way mentioned above, "X because it is aliased from Y [which matches]). This might be unfeasible since I know you can view an image and simultaneously have an irrelevant search parameter specified in the URL, ie. the search and the display of an image are not presently tied together on Derpibooru.

Finding what aliases direct to a tag is a little awkward, especially when starting from an image. I can click each tag on an image, and see what aliases for it are listed — which sounds like I'm just being lazy, and maybe so. 20 tags later and I've already somehow overlooked which one had the alias in my search, though… So, feature: you know the drop-down that has "Watch" and "Filter"? What about a sub-menu that has "Aliases"? And while I'm dreaming, how about "Implied by (on this image)"?

Even the Tags page makes things a bit obtuse. Like it says, "A wildcard is added at the beginning and the end" — so if I tried to use that page to accomplish suggestion #1, there are lots of cases where it will throw in unrelated tags since its search works differently. I understand why that was intended, and I'm not confident what to suggest otherwise: Omit the starting and ending wildcards if any wildcards are present in the search term? (That's unintuitive.) Add a checkbox for "strict search"? (Interface clutter, although, not much.)

And to top it all off, the Aliases list is not itself actually searchable, or even alphabetically indexed. How about it?

@mjangelvortexThat was me, it was an implied tag from "immobile" which I didn't expect. I let it be because I think the "immobile" tag is relevant but I did find it unfortunate because of the cute/cartoony nature.

One more tag for which I seek clarification: should I really like her mane be limited to clear references to that line ( SFW example ), or can it include depictions of characters liking manes without that line being closely referenced ( SFW example, NSFW example, or can it furthermore be used as a tag of appreciation on images with especially fancy or interesting hair ( SFW example, SFW example, SFW example )?

When something could be both part of a set and alternate version do you use both or is one preferred over the other? Also, is there a minimum quantity to qualify as a "set" or could I get some other guidance for when that is appropriate?

What I think is happening, is I'll be tagging an image, then maybe scroll back up to zoom in and inspect some detail, or in some other way make the text box lose focus without noticing. When I resume typing tags, I'll trigger a shortcut instead.

Of particular concern is that I've been voting and favoriting images without realizing it. It's been a few times that I'll look at my profile and find images voted and faved that I have no recollection of doing so. It might be fair to tell me to "get gud" but, like stairs, it keeps happening…

With that in mind, I'd like to propose that keyboard shortcuts be deactivated when the tag editing interface is shown, and when there is text entered in the comment field, even if these elements don't have focus. It seems reasonable to me that these conditions indicate user intention to be typing rather than navigating or curating.

Default search

If you do not specify a field to search over, the search engine will search for posts with a body that is similar to the query's word stems. For example, posts containing the words winged humanization, wings, and spread wings would all be found by a search for wing, but sewing would not be.

Allowed fields

Field Selector

Type

Description

Example

author

Literal

Matches the author of this post. Anonymous authors will never match this term.