[ SECRET POST #3149 ]

[case]

⌈ Secret Post #3149 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.


__________________________________________________



09.


__________________________________________________



10.















Notes:

Secrets Left to Post: 03 pages, 071 secrets from Secret Submission Post #450.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[(Anonymous)]

But if the main part of the fandom's on tumblr and everybody who ships a pairing is used to searching for the portmanteau, doesn't it makes sense for people to put the portmanteau in the tags on AO3?

[(Anonymous)]

DA

No, because AO3 has guidelines for how to write relationship tags. And those are Alice/Bob, not "Alob". Portmanteau ship names on AO3 are obsolete because at most, the tag wranglers connect them to the actual ship tag so that in essence, every fic tagged "Alob" is also tagged Alice/Bob in the backend, making searches for "Alob" and Alice/Bob yield the exact same results, at worst they're just uselessly bloating the list of AO3 tags.

[(Anonymous)]

ayrt

But if people searching for that pairing are gonna search for Alob and not Alice/Bob, it makes sense to have an Alob tag, because Alice/Bob isn't gonna get tagged as Alob on the backend. Basically, it doesn't matter that they yield the same results, because if your readers are gonna be searching for one and not the other, you should tag for the one that isn't gonna be automatically tagged on the backend.