tavina: (Default)
tavina ([personal profile] tavina) wrote in [community profile] au5k2026-04-12 09:58 pm
Entry tags:

2025/2026 Round Creators Revealed! & Feedback Post

Creators have now been revealed for the 2025/2026 round of AU5k! Thank you all so much for participating - this exchange is always one of my absolute favorites to run and I love seeing the love we have for AUs every year.

A few notes, and a few questions I’ve had for you guys regarding the event:

  1. Do you like the length of the creation period? Too long? Too short? Prefer a more formal check-in in the middle?
  2. Do you like the time of year that this event takes place? (mid November to March/April) Is it potentially conflicting too much with FFFX and HAex or are we okay with where we’re at in the event calendar?
  3. How do we feel about a commenting rule for next year? I think if I implement one, it’ll start on works submitted for the 2026/2027 round (meaning no one will be penalized for not commenting on gifts until 2027/2028 round signups) and be something close to FFFX’s “please comment on gifts before next year’s signups open, or otherwise contact me to discuss,” but I’m not entirely married to the idea and would like some input on whether we think that’s something you guys would prefer as a group.
  4. Any other feedback? Comment down below!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_maintenance2026-04-11 11:58 pm

The case of the missing notifications

I keep forgetting to post about this: we've been troubleshooting the "missing notifications" problem for the past few days. (Well, I say "we", really I mean Mark and Robby; I'm just the amanuensis.) It's been one of those annoying loops of "find a logical explanation for what could be causing the problem, fix that thing, observe that the problem gets better for some people but doesn't go away completely, go back to step one and start again", sigh.

Mark is hauling out the heavy debugging ordinance to try to find the root cause. Once he's done building all the extra logging tools he needs, he'll comment to this entry. After he does, if you find a comment that should have gone to your inbox and sent an email notification but didn't, leave him a link to the comment that should have sent the notification, as long as the comment itself was made after Mark says he's collecting them. (I'd wait and post this after he gets the debug code in but I need to go to sleep and he's not sure how long it will take!)

We're sorry about the hassle! Irregular/sporadic issues like this are really hard to troubleshoot because it's impossible to know if they're fixed or if they're just not happening while you're looking. With luck, this will give us enough information to figure out the root cause for real this time.