Basically, I had an idea that there could be a way to set up custom tag implications or aliasing. The way it would work is that you'd go into you account settings and there'd be a box where you could put tags to be aliased. Each line would be a set, with each set being included in any search with one of the contained tags, so searching for any one of those tags would function the same as an or search for all of them. for implications, the first tag on the line would be added into any search containing any of the other tags on the line. This would be on a per account basis, so it wouldn't affect other users. I wanted to see what others thought, or if this would even be possible on the backend.

It's a good idea. Does not need to be on the backend, can be added to the frontend via javascript.

My userscript has that functionality. It even has nesting and wildcard support.
For example, by defining a *_ftwings -> feathered_wings *_wings *_feathers alias, you can enter blue_ftwings, and it gets replaced with feathered_wings blue_wings blue_feathers.

It's very helpful when tagging.

bitwolfy said:
It's very helpful when tagging.

I could see it being easy to mess up and cause a bunch of invalid tags, though. Especially for lazy people that set up an alias to tag multiple things at once, and then use that alias even if only some of the tags apply because it's easier to remember.

watsit said:
I could see it being easy to mess up and cause a bunch of invalid tags, though. Especially for lazy people that set up an alias to tag multiple things at once, and then use that alias even if only some of the tags apply because it's easier to remember.

That's very much true.

For example, I have an equine_fullcock -> equine_penis medial_ring flared_penis alias, but I also equine_halfcock -> equine_penis medial_ring, since the flare isn't always there.
You just have to be careful, like with all automatic tagging tools.

bitwolfy said:
It's a good idea. Does not need to be on the backend, can be added to the frontend via javascript.

My userscript has that functionality. It even has nesting and wildcard support.
For example, by defining a *_ftwings -> feathered_wings *_wings *_feathers alias, you can enter blue_ftwings, and it gets replaced with feathered_wings blue_wings blue_feathers.

It's very helpful when tagging.

My idea was focused more on the searching/viewing side (i.e. if there's multiple tags you typically do an or search for together (ex. ~Flareon ~Jolteon ~Vaporeon), you could set a custom alias and just type the alias with the same result as or searching the tags manually). Though, I can also see the utility on the posting side. the feature could even be expanded to what would essentially be search presets where you set a name and a search query, and searching for that name would respond as if you'd entered the search query. For example you'd save name tag 1 tag 2 -exclude, etc. and then you could just type in name instead of the entire query. Of course, the names would have to be checked against the tag index (or whatever the central list of tags is called) to make sure another valid tag doesn't already use it; or have it require that you put in a prefix to indicate you're using a preset (ex. "#eevee" would run the search associated with the preset named "eevee", whereas "eevee" would behave as a normal tag) This also opens up the ability to mix normal tags and presets on the fly by preceding each preset with a # (or whatever prefix would be used) Like this: tag_1 tag_2 #preset_1