For some time now, it's seemed to me like all_the_way_through, given its sister tags like in_one_ear_and_out_the_other, snake_impalement, double_threading, mismatched_threading, in_one_ear_and_out_the_other and so on, is starting to be due for some cleanup, as well as a new definition fit to include proper subtags.

I've already started tagging with some proof-of-concept tag names to get a good feel of what works and what doesn't and by now I'm about a third of the way through all_the_way_through order:id_asc. I've settled upon threading as the root of the tag group because, being a single word, it's more easily composable (so we don't get more mouthfuls like urethral_all_the_way_through).

With that out of the way, here's what I have so far.

*_threading (by entry point, matches *_penetration)

• anal_threading
• oral_threading
• vaginal_threading
• urethral_threading (superset of urethral_all_the_way_through)
• ear_threading (superset of in_one_ear_and_out_the_other)

And the special ones

• mismatched_threading (when the exit orifice isn't one that "makes sense" given the entry point, but it's not impalement)
• unusual_threading (orifices too niche to warrant their own tag)
• ambiguous_threading (see below, this one is complicated)

threaded_by_* (by penetrating object)

(I know the names for these are somewhat clumsy, I mainly didn't want to overload the *_threading pattern further while in the draft phase)

• threaded_by_penis
• threaded_by_tentacle
• threaded_by_tongue
• threaded_by_body (mainly for snake_impalement, but also a number of goo cases)
• threaded_by_sex_toy
• threaded_by_beads (would likely imply threaded_by_rope as well)
• threaded_by_dildo
• threaded_by_tail
• threaded_by_rope
• threaded_by_tubing

*_impalement (mirrors *_threading for the more violent stuff)

• anal_impalement
• oral_impalement
• vaginal_impalement
• fully_impaled (since regular impalement may not require an exit point, all_the_way_through on impalement images would be replaced with this)

Miscellanious tags

• double_threading (the tentacle or whatever keeps going past threading and at least enters another person)
• ass_kebab (same as above but 3 or more characters)
• u-turn_penetration (tentacle re-enters a character it already came out of, either through the same orifice or a new one)
• threading_plushie (the odd one out, because I couldn't figure out how to tag orifices on plushies)

Keep in mind all these tag names are working titles and one of the reasons for this discussion thread is to discuss alternate naming conventions.

Current model

So the *_threading I'm using is based on the orifice of entry, which has the obvious benefit of making each of those tags map neatly to *_penetration such that an implication could be made. All types of threading are implicitly matched with a natural exit point (oral -> anus, anal -> mouth, urethral -> urethra, ear -> ear) and any other case is considered to be mismatched_threading and should be tagged as such.

Most obviously violent examples would be recategorized as impalement (I doubt people who sift though ATWT usually want to see the gore-kind), with a similar entry orifice scheme and fully_impaled to distinguish these from more... "normal" impalement?

However, the "per orifice of entry" rule raises some interesting problems. Among other things, it makes the proposed tags less strict than the current definitions for in_one_ear_and_out_the_other and urethral_threading, these two explicitly state the exit orifice. in_one_ear_and_out_the_other also would apply for some form of cum_through during ear_penetration, which wouldn't actually be threading.

The much thornier issue with that, though is that it means a lot more things are now considered ambiguous_threading.

Indeed, ambiguous_threading needs to cover:

• Cases where both ends of the tentacle/rope/etc. are off-screen or detached, such that it's unclear what orifice is the entrance and which is the exit.

post #9095 post #573733

• Cases where the "logical" entry orifice can't be seen and no indirect evidence of it being penetrated can be observed, which would be a problem with aliases to *_penetration as well as the possibility of mismatched_threading

post #661811 post #506919

• Cases where it's unclear if there even are orifices serving at entry points at all

post #485117 post #541697 post #921409

There might be ways to change the definition somewhat to resolve a few of these cases, but right now it means ambiguous is pulling triple-duty, which I'm not entirely confortable with.

So, then, does that proposed model hold any water? Are there any obvious changes that could/should be made to it that I'm missing before pushing it further? Is *_threading the right root for this and should it lead to all_the_way_through being eventually aliased to that, or should other names be found for all of these?

I think this is a great idea!

Well, I was hoping to get some discussion going and gather some feedback, but given it's been two weeks, I'll assume I'm clear to keep going with the current model.

fifteen said:
Well, I was hoping to get some discussion going and gather some feedback, but given it's been two weeks, I'll assume I'm clear to keep going with the current model.

Not many people have a strong opinion one way or another about this, or enough knowledge to weigh in. More organization/standardization is good imo.

Ok, I guess I should make a little status report at some point.

• For now, I've mostly been removing the cases of creature_inside from all_the_way_through because the creature is coming out of both end, so it's not penetration in the usual sense. Is this a correct interpretation? Would a new tag be needed, like "emerging from both ends" or something of the sort? EDIT: I'm going to tentatively start tagging these emerging_from_both_ends, see where that goes.

post #1426410 post #1024970 post #631996 post #1465805 post #1672568 post #1831143 post #2111840 post #2172749

• I've been running into a few posts that don't actually fit the definition of ATWT, but don't really have a proper tag at the moment, like post #1782296. It's similar to, say, cum_through, but it's a solid object that passes through the character from ass to mouth (and then back). I've seen similar things done with eggs as well, like post #1672572, or post #1801109, so clearly there's content there, and I understand why "all the way through" seems to fit what is going on in these images from the tag name alone, so I'm really starting to wonder if there shouldn't be a broader tag for various *_through stuff. Using goo_through, object_through and the like so far.

post #1857915 post #1782296 post #3170489

• Regarding the above, I've been pondering the possibility of having all_the_way_through remain as a supertag for both threading and cum_through, possibly. Re-using the name might prove a bad idea, but I believe theree's potential in having a supertag for both.

• At least one image shows mixed threading (here: arm+dildo), and I'm not sure how I want to tag that:

post #2309672

• Basically all the way through, but not actually emerging from the other end:

post #2356932 post #2239355 post #2372250

• The line between threading and impalement isn't always as clear-cut as I'd like.
• "gore-less impalement": post #1704297 post #2383403 post #2937798
• "maybe threading or impalement but death ensues": post #1807655 post #1807657 post #2109754 post #2507488
• "internal bleeding caused by barbs, not impalement": post #1707692
• "stake all-the-way through": post #763974
• "hole was already there": post #2525606
• "gorey in_one_ear_and_out_the_other": post #2660707

• From a discussion I've had on the e6 Discord server a few months ago, the line should be either drawn at either "impalement is when the act causes or assists in the character's presumed death" or "impalement is when the penetrating object forces its way through by piercing some internal organs, usually observed by the presence of blood on either end". Both of the definitions cover mutually exclusive subsets of the 3 troublesome areas listed above. Having mulled over these to the point of having been stopped dead in my tracks with the tagging, I'll just leave these edge-cases alone for now and keep a list here of the more annoying cases I come across.

• Goo creatures really make this difficult when we're not clearly dealing with threaded_by_body or goo tentacle.

post #2971899 post #3001862

With all that said, the *_threading/threaded_by_* model I've been using (and expecting to have to replace after figuring out that it sucked) has proven surprisingly robust, speaking with the experience of now being more than halfway through all_the_way_through.