[ SECRET POST #6077 ]

[case]

⌈ Secret Post #6077 ⌋

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


01.



__________________________________________________



02.



__________________________________________________



03.



__________________________________________________



04.



__________________________________________________



05.



__________________________________________________



06.



__________________________________________________



07.


























Notes:

Secrets Left to Post: 02 pages, 39 secrets from Secret Submission Post #869.
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)]

I wish AO3 would take FFN's tagging style, tbh. The tags on AO3 are a real shitshow.

[(Anonymous)]

DA but I am unable to comprehend how someone could think this

AO3 tags definitely have room for improvement but on a fundamental level they're brilliantly sueful

[(Anonymous)]

There are just too many of them to be useful. Condense them down to broad functional predefined categories would be more useful for searching.

[(Anonymous)]

But having tags exist as hierarchical trees pretty much solves that on a design level. You can have very specific tags that then fold up into broad functional pre-defined categories, so people can search however they like.

In practice, it doesn't work bc the design requires people to actively maintain the tag tree hierarchy. And for organizational reasons tag wranglers have apparently been unable to do any of that work for like a decade. But that's a problem with the organizational structure, not the underlying design.

[(Anonymous)]

Do you have examples of things you couldn't find because the tags weren't limited to predefined categories?

I don't think I've ever run into this issue. The only times AO3 tags weren't useful to me is when it comes to characters/relationships as not everyone makes it clear in the tags which characters/relationships are the focus. But an individual author can solve that by being clear in the tags they use, so this wouldn't even be an issue if authors put more thought into it.

[(Anonymous)]

????? Like, sure, authors gabbing away in the tags is annoying, but that's a user error. I love being able to find exactly what I'm in the mood for. Mafia!Au, petty!character, drowning, canon spiritual dildos, etc, etc. It's lovely.

[(Anonymous)]

(DA x2 combo) I can see the value of "you have to pick the four most important characters", since AO3's model makes it impossible to filter for the fics in which Glup Shitto is actually the focus as opposed to just showing up for half a sentence -- I don't think FFN's model is the better one overall, though. But the other tag types are pretty straightforwardly improvements, especially the additional tags (FFN's version is literally nothing lol)

[(Anonymous)]

Yeah, I think having a way to designate a pairing as the primary pairing would be a huge improvement to AO3 tagging (very much speaking as someone who ships the #2 most popular pairing in a juggernaut megafandom, lol). But everything else about AO3 tagging is so much better.

[(Anonymous)]

NA

I agree that a native function to designate the main pairing would be nice but at the same time, authors can also clarify in the tags when certain pairings are just in the background, which would also allow for easier searches.

The cynical part of me things that authors who don't do that just want the extra visibility of popping up in searches for both pairings. And I don't think that a main pairing option would make much of a difference to those authors.

[meadowphoenix]

yeah, I agree you'd have to force it, which is its own problem. but god is it annoying to search for a pairing and not get anything that focuses on it in the tags.