The tag implication #45469 … -> ... has been rejected.

Reason: my device will automatically change three periods in a row to a one-character ellipses symbol. i can’t turn it off.

EDIT: The tag implication … -> ... (forum #340433) has been rejected by @bitWolfy.

forget an implication, we need a full on alias for this i'd say

The tag implication … -> ... (forum #340433) has been rejected by @bitWolfy.

The tag alias … -> ... has been approved by @bitWolfy.

Thanks, bit.

Rembmer: An implication adds a second tag while keeping the first. To replace a tag, you want an alias.

furrin_gok said:
Thanks, bit.

Rembmer: An implication adds a second tag while keeping the first. To replace a tag, you want an alias.

that’s… what i meant to do

cheshire3rd said:
that’s… what i meant to do

I know that feeling. It's one reason why I stick with BURs now, even for just one alias and implication. They're editable.

We really, really need an explainer on both the alias and implication request pages so people can learn the difference.

scaliespe said:
We really, really need an explainer on both the alias and implication request pages so people can learn the difference.

Early on I had to think really hard to not confuse which way I'm aliasing or implicating.
Something like this would be really helpful:

Tag Alias Request
From
$tag1
To
$tag2
When tagging, $tag1 will be corrected to $tag2.

Tag Implication Request
From
$tag1
To
$tag2
When tagging, $tag2 will be added alongside $tag1.

If this isn't proposed already, I'll make a feature request.

waydence said:
Early on I had to think really hard to not confuse which way I'm aliasing or implicating.
Something like this would be really helpful:

If this isn't proposed already, I'll make a feature request.

I mean, if you know what the words “alias” and “implication” actually mean, the distinction should be obvious. Unfortunately, neither word is extremely common in English.