coalcube: (coaltide)
coalie ([personal profile] coalcube) wrote in [community profile] coaltide2025-09-13 02:19 pm
Entry tags:

*Notices Yuletide*

OwO What's This?

Monday 15 to Friday 26 September: Nominations (end 9pm UTC 26 September) | Evidence Post | RPF Coordination | Promo Post
Tuesday 14 to Friday 24 October: Sign-ups (end 9pm UTC 24 October)
Sunday 26 October: Assignments out (may be earlier)
Wednesday 10 December: Default deadline (9pm UTC)
Wednesday 17 December: Assignment deadline (9pm UTC)
Wednesday 24 December: Main collection works reveals (9pm UTC)
Thursday 25 December: Madness collection works reveals (9pm UTC)
Thursday 1 January: Author reveals, end of event (9pm UTC)

Mini-Challenges:

Crueltide | Femslash Festivus | Yulebuilding | Three Turtle Doves | Two for One | Yuleporn  
Family Matters | Queering the Tide | Yuletide Madness Drabble Invitational | TransTide 
Chromatic Yuletide | Unconventionyule | Wrapping Paper | Babytide | MultiLingYule 

Yuletide Discord for Hippos & Exchanges After Dark Discords for Namespace drama 18+ discussion. Google Group for PHs.


Flat / Recent | Top-Level (Last) | FAQ | Search
 

(Anonymous) 2025-09-24 02:24 pm (UTC)(link)
The same way I would any complaint email: with evidence that they're paying attention and respect my concerns and feelings.

Like for a marginal DNW violation they decided didn't qualify, I'd want to hear something like, "We're so sorry! We can see why that aspect of your gift was a problem for you. Unfortunately we've reread our guidelines and we don't think it's an actual rule violation that we'd be willing to penalize the writer for, because (understandable reason). We're going to look over our rules before next year to make sure those lines are clear enough."

That said as a customer service worker who has to answer dumbass IT tickets in namespace sometimes, sometimes the customer is actually a POS whose concerns you have 0 respect for. But since this is a silly fandom exchange and not wage labor, you aren't actually obligated to keep them coming back or continue working with them. So I wouldn't break your back trying to fake respect for someone who is obviously in the wrong and you don't even want in your exchange anyway. Like maybe don't cuss them out but if you replied, "We don't give out EPHs just because they didn't name the OC kitten what you put in your prompt, deal with it," or "You DNW'd gen, ship, and porn, so I think your writer did the best they could with what they got", well, the recip would hopefully know better than to do your exchange again so it's win for both of you.

And if you're going to be catty about my email in a 100+ person mod discord that will obviously be leaked, just be catty in your communications to me too.

(Anonymous) 2025-09-24 10:33 pm (UTC)(link)
"You DNW'd gen, ship, and porn, so I think your writer did the best they could with what they got"

Y'know, this one's on the recip. The mod shares blame in not shutting that down during signups.

(Anonymous) 2025-09-25 09:30 am (UTC)(link)
The mod shares blame in not shutting that down during signups.

I really don't think it's on the mod to go through every single participant's DNWs and "shut down" things like that.

It's dozens, potentially hundreds of sign-ups, all with different formatting and DNW phrasings that may or may not be nonsensical depending on the fandom in question. I don't think the mod owes anyone more than putting clear rules about DNWs in the exchange rules and enforcing them if a violating DNW is brought to their attention (such as a DNW that kink-shames).

It's nice when mods go the extra mile in anticipation of problems, but it's not at all mandatory (and, as seen with FIAB, pre-emptively reaching out over little things can also cause undue stress).