Let's say a visitor comes to Danbooru searching for pics of Saber, and discovers her real name is Artoria Pendragon. What is their reaction, and what happens to our website?
Let's say a different visitor makes an account to upload pics of various Fate characters, and runs into a spaghetti mess of Fate tags. What is their reaction, and what happens to our website?
I would bet the second person is much more likely to quit Danbooru or harbor negative feelings or cause trouble on our website than the first person is.
The catchall + variant tagging system makes at least as much sense as the way we've tagged fate characters for years. Has people getting angry and causing trouble over Fate tags been a problem before?
So, just a random thing to prove the point about how confusing this class name-only tagging system is, Robin Hood's tag is archer (fate/extra) but post #2890999 and post #2891041 seems to be confused over what that tag is used for. Mind you, this happened three days ago; people are still making mistakes over this convoluted, archaic tagging system. This needs to change.
I mean really, "gorgon" was added to "rider" who is Medusa.. And now it's automatically implicated with "rider". This lazy way of tagging Fate characters must stop before we get another Saber dilemma.
I'm not sure if this should be an alias request instead, but now that the Shimosa chapter's been released in FGO, should "limited/zero_over" be renamed or otherwise aliased to "senji_muramasa" or something? Also, on spoiler concerns regarding change of old tags, I think it's much less of a problem than the "spaghetti tags" now that Grand Order's been out for over two years: everyone's called by their real name there. And Apocrypha anime too, they just reveal their true names right off the bat.
I'm not sure if this should be an alias request instead, but now that the Shimosa chapter's been released in FGO, should "limited/zero_over" be renamed or otherwise aliased to "senji_muramasa" or something? Also, on spoiler concerns regarding change of old tags, I think it's much less of a problem than the "spaghetti tags" now that Grand Order's been out for over two years: everyone's called by their real name there. And Apocrypha anime too, they just reveal their true names right off the bat.
If the spoiler policy sticks, then logically we'd have to change all the EoR servants, so Moriarty will become Archer of Shinjuku, Chiyome will become Assassin Paradiso, etc.
Then we'll see how many people remember the stupid code names.
As for the other topic, that's pretty tricky. So far, LZO's appearance has been used to refer to LZO-as-Shirou, especially in things like manga or Emiya family pics. Muramasa may be visually the same, but he's still a different personality. They'd be, like, dunno, twins?
I'm impressed Nasu and co. manage to find ever new ways to make tagging even more complicated.
Honestly, though some arguments remain as "spoiler is still spoiler regardless of time", using (Star Wars spoiler) Darth Vader is Luke's father) as example, at this point everyone who is not even into Star Wars (or at the topic, Fate series) are already spoiled, with the franchise being over a decade old. And a lot of people actually play FGO first before getting into the original series, so they all already know who's who.
KyteM said: If the spoiler policy sticks, then logically we'd have to change all the EoR servants, so Moriarty will become Archer of Shinjuku, Chiyome will become Assassin Paradiso, etc.
Exactly this. One argument says that "spoilers have no expiration date", and yet the servants from EoR chapter got revealed blatantly in this site, with their code name immediately aliased to true name.
Now that the survey has been taken off from the header, does it actually answer something or should this tagging system stay convoluted as it is now?
I noticed this specific example because F/GO is running a Halloween event that heavily features Berserker Tamamo Cat. I see @KyteM covered this about 4 months ago, but wanted to be specific on this, especially since anyone coming here looking for pics (that fabulous new user that keeps coming up in this thread who can be traumatized by a single tag) because of the event is going to find our tags are just wrong.
We're tagging all the Berserker tamamo_cat_(fate/grand_order) with caster_(fate/extra), which is incorrect - story-wise, Berserker Tamamo Cat is one of original Tamamo's cut off tails, but is now an independent heroic spirit. As seen here: URL:http://typemoon.wikia.com/wiki/Berserker_(Fate/Grand_Order_-_Tamamo) if she's got the red outfit, pawgloves, big bell, more hair and earfur and thicker build it's Tamamo Cat (Berserker) and the thin build, blue outfit, thin b/w choker is Tamamo-No-Mae (Caster). The bell and pawgloves are the big thing in case of nekkid or alternate outfits.
To further complicate things we've got tamamo_no_mae_(swimsuit_lancer)_(fate) which is still tagged caster too - but that's more reasonable since it's just the same character in a swimsuit.
To further complicate things we've got tamamo_no_mae_(swimsuit_lancer)_(fate) which is still tagged caster too - but that's more reasonable since it's just the same character in a swimsuit.
There are some lines during the summer events (can't quote them but I know I've seen them) that imply that Lancer Tamamo is also one of those severed tails, as she later decides to call herself "Tamamo Shark" and become part of the Tamamo Nine. This is yet another example of how the class-based naming is a snarl of insanity that FGO has completely destroyed, and was seemingly intended to destroy.
Also, "spoilers are forever" is not a valid policy due to the "It Was His Sled" effect, as denoted on TV Tropes. Fate Stay/Night has been out for years at this point, and with Grand Order handing us everyone's true names (even EMIYA's) on a platter, spoilers are guaranteed. The policy does not work, not for an image site where the majority of people who use the tag search probably already know who they're looking for and don't care about spoilers.
In fact, by the "spoilers are forever" logic, we should be tagging Touhou's Extra Stage bosses as spoilers, possibly even all bosses not featured in the demos (which is everyone past stage 3) and bosses for the fighting games, since their demos don't normally reveal them. Given Touhou is one of our big breadwinners here and almost everyone knows who most of the big-name characters are (even non-fans), that doesn't make sense, and it shouldn't. The policy for Fate is outdated, and we should change with the times, as Grand Order is subtly encouraging us to do.
Considering majority opinion, multiple advantages of true names, and the lack of good arguments supporting the old system, the site should go with true names.
Follow up of the previous bulk update. As mentioned in forum #137039, the BUR form wouldn't allow me to request those implications when indirect ones existed.
I noticed that a few tags in the system have _(fate) at the end of the name to imply that the character comes from that franchise, and I kind of understand that. These are historical/mythological characters that exist beyond the nasuverse lore, so tagging them as specifically a part of the nasuverse is a pretty good idea. I'm not very sure about the idea of referencing which fate (series) work they originate from, because I think that would cause confusion due to fate/grand order not directly stating their origins in-game. Karna is tagged as karna (fate) and not karna (fate/apocrypha) or karna (fate/extra ccc) while Gilgamesh is tagged as just gilgamesh and not gilgamesh (fate). However, there are some clones such as Cu Chulainn and I would recommend keeping originating works on those particular tags. Names such as Artoria Pendragon, Nero Claudius Bride, and Hassan of Serenity are so unique that I wouldn't worry about putting a _(fate) at the end, but that does screw with the consistency. So keep that in mind.
Artoria Pendragon is not a public domain name, unlike Arthur Pendragon, so she doesn't need _(fate) at the end. Everyone else needs, I think. I'll address anything else tomorrow, if I find anything to address.