Profile

RelationShipping Exchange

August 2026

S M T W T F S
       1
2345678
91011 12131415
16171819202122
23242526272829
3031     

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
[personal profile] rshipmod posting in [community profile] relationshipping
Hi everyone!

New management here. The 2026 schedule should be posted in the next 3-4 weeks, and you can expect mid or late July-Sept, potentially (but hopefully not!) stretching into early Oct for delays. 

But I'd like to talk about something else!

Nominations for this exchange are currently pretty complicated, and they always have been complicated, since mods used to have to confirm that characters were related before approving nominations. Sometimes that's straightforward, and sometimes the nomination is for a rare fandom without a wiki and no clues in the names that characters are related. This puts a lot of - I think unnecessary - stress on the mod, and the alternative used last year (marking every character by how they're related) seems to have made things more complicated or confusing for participants.

Since this exchange has always been so open and welcome to AUs (something that I've loved about it since its early days, thank you TDC!), I wonder if we might make things a little bit easier on everyone by removing the requirement to list how characters are related (unless of course there is an AU you'd like to bake into your nomination), and treat any unrelated ships without specific relationships baked in as an "Any type of relative" AU request, since we will always allow AUs. 

This removes the obligation of the mod to spend hours researching incest ships during nomination approvals, and also makes approval the default, which means participants don't have to keep as close an eye on the exchange dreamwidth for fear of their ship getting a query post without their noticing, and not ending up in the tagset. However, there's a caveat to this approach. If your fandom is very complex, ongoing, or the relationship is implied but not stated overtly, it's possible that a canonically related pair being canonically related might have slipped past your assigned creator, leading them to treat it as an "AU any" request, instead of researching the canon further or sending you a question through the mod. It's also possible you and your assigned creator have different opinions as to how a pair are related to begin with, potentially leading to disappointment.

If we (speaking collectively here - I want to work with you on the best solution for the exchange!) go forward with this approach, it would be very wise to state somewhere in your signup if you suspect that your ship might not be so obviously related to other people as it is to you (e.g., recently revealed to be related, the creator of the media said in an interview/on social media they're relatives, it's hidden in item flavor text in a video game canon, etc) a note that clarifies their canonical relationship. Basically what you'd have replied to a query post with here a few years ago! 

DNWing AU relationships other than the canonical relationship would be permissible. DNWing a particular kind of relationship on an unspecified AU relationship would NOT be permissible, but stating a positive preference (e.g., "I especially like brother/brother and brother/half-brother ships!") is always welcome. As always, DNWing incest would NOT be permissible. This is an incest exchange.

I'd love your feedback on this, and look forward to another year of Relationshipping!
Tags:
Date: 2026-04-27 11:17 pm (UTC)

anr: (Default)
From: [personal profile] anr
Anything that makes it easier for mods is good for the exchange! And I think not having to specify the familial relationship in the pairing nom is a good idea.

Suggestion:
What if there were predefined additional tags (being different familial relationship types) that you could choose from? With it being mandatory that at least one be selected in your offers and requests? Matching could then run on Fandom & Pairing & Relationship.

Relationship types could be:
- Brother/Sister
- Father/Daughter
- Sister/Sister
- Any Female Family Member/Any Male Family Member
etc.

This way, it doesn't matter so much whether the pairing is canonically familial, because the additional tag determines what type of relationship you want those characters to have in the story (whether it's canon or AU).
Date: 2026-04-28 12:18 pm (UTC)

From: (Anonymous)
'Ships containing any number of characters may be nominated, provided two or more characters involved are related', so it could be hard to set up clear relationship type tags for everything. E.g., 'Mother/daughter/husband/niece/clone' - whose husband, niece, and clone?
Date: 2026-04-28 01:12 pm (UTC)

anr: (Default)
From: [personal profile] anr
Optional details? There's never going to be a perfect solution that benefits every possible request type and the required mod-effort, but anything that helps simplify the majority is surely better than nothing.
Page generated Aug. 19th, 2026 02:19 am
Powered by Dreamwidth Studios