Aliasing st._bernard → saint_bernard
Link to alias

Reason:

Same.

Related:

Implication: saint_bernard -> dog

I think that now that you're a mod you can make aliases or implications without suggesting them...

...right?

Xch3l said:
I think that now that you're a mod you can make aliases or implications without suggesting them...

...right?

IIRC aliases/implications shall still be done this way.
Being a mod does not make a person right 100% of the time, aliases and implications still needs more than one viewpoint, there needs to be a discussion. Although not always for obvious aliases as this one.
+1 on the alias btw.

Xch3l said:
I think that now that you're a mod you can make aliases or implications without suggesting them...

...right?

Nopi dopi. Admin function.

Besides, as Peekaboo stated, except for the most obvious implications/aliases (e.g., misty_(pokémon) -> pokémon), it's a good idea to submit them this way to gives a chance for others to voice potential disputes (for example, if there was an artist called "st. bernard") and related suggestions (implication: saint_bernard -> dog).

Implicate saint_bernard -> drooling.

Approved aliasing both st._bernard and st_bernard to --> saint_bernard because both would occasionally get used. And approved the implication of saint_bernard to --> dog.

Also Parasprite is correct on both counts. Processing or deleting an alias/implication is Admin only. Mod status is like Admin-in-training, so there's still a few things mods can't do until they pass into the final circle, sacrifice a lower pokemon and sell their soul for the admin keys. Nah, just kidding. =P

Also, even though Admins do have the ability to make aliases/implications without going through the forum, still for things which seem significant in any way we usually tend to go through the forum anyways. It's because Admins aren't immune to the whole perils of aliases/implications where "this really sounded completely logical and obvious...until that one point was brought up and yeah, now we're going to delete it instead because that would make a terrible mess" which anyone who's read a few discussion threads knows can happen to even the best of users. They're tricky to get right and think of everything. So it's just a damn good idea to let more than one set of eyes look over it for potential issues before it goes through. It also keeps things more transparent and keeps the userbase in the loop of what's being changed and why. It's just better all around this way. Though I agree this particular one is basically a spelling redundancy, so it could have gone either method and probably been fine.