All-Purpose Policy and Meta discussion: Administrivia.Trope Repair Shop

I also thought it was odd that the Bile Fascination crowner had options for both "unlock if made IUEO" and "unlock regardless of which other options are chosen (if any)".

As did I. We probably shouldn't have included it.

EDIT: Removed inaccurate info

Edited by themayorofsimpleton on Feb 23rd 2021 at 5:44:44 AM

The Author Existence Failure thread doesn't have a full wick check- only 22 wicks.

Declined that one. There's a little more than 2.6k, so the amount the OP should have checked would be the square root of that: rounds up to 52.

A new thread was made with a wick check that has the right amount of wicks (it actually has slightly more than the number you gave). Is that one sufficient?

Edited by GastonRabbit on Feb 24th 2021 at 9:43:23 AM

More is always fine.

I agree that this wick check is much more robust but...why do new threads keep being opened ahead of older ones? What's the metric here for when a thread can be open immediately versus several weeks/months later?

Agreed. It feels kinda disrespectful when people who still have their threads stuck in limbo are forced to wait while the new ones get opened immediately.

(Okay, real talk here. I'm kinda biased in favor of my Bee Afraid thread. Call me salty and impatient, I will not deny it if I come off as such, but it really irks me that my thread is still stuck in the limbo. I understand that mods may have their reasons, and am willing to wait if I have to, but the fact that new threads get insta-opened while my Bee Afraid thread gets stuck in the limbo rubs me in the wrong way.)

Sorry about that. If it makes you feel any better, next one I'll open will be an older thread.

Edit: Bee Afraid is now open!

Edited by Berrenta on Feb 24th 2021 at 10:39:43 AM

Granted, when it's something like "Oh, this page made in 2012 has 2 wicks and is based on a stock phrase", then yeah, that's an easy thread that'll take only like 3 days to finish, so I get opening up those really soon. It's just weird when we have threads that have about the same amount of wicks and similar problems to newer ones, and the newer ones are the ones that get opened. I've been saying this for a long time, but I really think the threads at the bottom of the queue should be opened first in most cases- it just makes the most sense.

I've thought for a while that threads closer to the bottom of the page should be looked at sooner than ones closer to the top (regardless of whether it means opening or rejecting them), though maybe exceptions could be made if the thread merits more attention.

Edited by GastonRabbit on Feb 24th 2021 at 12:17:25 PM

Two considerations are that a) if you start from the top, you are not cycling through each thread and thus will miss the old ones and b) the troper who opened the thread might lose interest if the wait is too long. I think that a) is more an issue, myself.

I could see b) happening if the thread went months before being opened.

Edit: The oldest locked thread (which is also the oldest non-Morgued thread) was only posted on the 5th of this month, so I guess the increase in TRS activity since I became active has sped things up to prevent the scenario I originally mentioned (considering some threads have gone a few years between being opened and being Morgued).

Edited by GastonRabbit on Feb 25th 2021 at 3:40:19 AM

A) and B) are both definitely concerns, though B) is more dependent on how long the wait is. A) does seem to be a concern though; the more we open newer threads, the easier it is for older ones to just get missed entirely because they fall too far to the bottom where nobody scrolls. So you end up with threads made recently being opened while older ones remain sitting for ages before they're finally noticed or acknowledged, and that just doesn't seem right.

I think the main consideration should be "how is the backlog doing?". If there's some threads we can get through very quickly, sure, open those first while we continue closing bigger threads. But if there's space and we can start opening bigger-issue threads, if all else is equal, the ones on the bottom should open first. In general, I think the backlog is the biggest priority and issue, but then the second priority should be "when was the thread made?". Even then, older threads with quick issues should be opened before newer threads with similar issues.

That said, I remain skeptical that the Always Identical Twins thread is actually ready to be opened, because it still concerns me that there was no acknowledgement of or accounting for the fact that it's a Trope in Aggregate.

Edited by WarJay77 on Feb 25th 2021 at 2:00:53 PM

Only Point Two Percent Different doesn’t sound like it would be too difficult to respond as the trope isn’t thriving to begin with. So that’s an older thread that isn’t complex.

As far as the backlog is concerned, we have been under 100 for a while now which is great. But yeah we should be focus on opening older threads first.

Edited by MacronNotes on Feb 25th 2021 at 1:15:11 AM

Anyway, finally made my Memetic Mutation thread. I mostly made it now so that I wouldn't forget all the details later. Obviously I don't want it to be opened until it's necessary- please tackle some older projects first. This is a big boy and it can wait in the queue behind other big projects we still have yet to finish or even start.

What do you think of this as a potential template for crowner announcements:

• There is currently [[(link to thread) a TRS thread]] for (X Trope) with an active crowner. If you wish to vote on the crowner or otherwise participate, now would be a good time to do so. We only ask that you read through the thread before voting, and vote based on what you think would be best. And if you would like to suggest new options or discuss the ones already on the table, we would certainly welcome that too.

I'm on board until the "discuss new options" part. In my experience adding things to crowners after they're already up only leads to confusion and things being unnecessarily complicated; it's rare that people will go back to check something they already voted on, so early voters don't know the crowner even changed to begin with.

So, uh... the thread for Never Send An X To Do A Ys Job was locked as being finished, but the thread was never starred and the page was never cut (which was the consensus on the thread).

Edited by Serac on Feb 28th 2021 at 12:00:13 PM

It's cut now.

I think it would be clearer if we cut some words,

There is currently [[(link to thread) a TRS thread]] for (X Trope) with an active crowner. If you wish to vote on the crowner or otherwise participate, please read through the thread before voting. If you would like to discuss the trope, we welcome that too.

I prefer your wording due to its brevity.

Since the Animal Tropes cleanup is still open, I may take Turtle Power there. Will do a wick check when I get home.

There's an animal tropes cleanup?

Yeah. I started it and...left it in the dust. I haven't touched it in a while. Courtesy link

Pardon the Early-Installment Weirdness you may find. Once I get home, I'll polish it up so it can be a bit more proper.

Edit: And looking through the Tropes Needing TRS list, I think we can deal with Alluring Anglerfish as well. Added to the cleanup queue, and linked Unicorndance's wick check. That could might as well go first.

Edited by Berrenta on Mar 2nd 2021 at 4:21:32 AM