| Revision as of 13:37, 1 January 2009 view sourceDravecky (talk | contribs)104,715 edits →Q4?: interleaving text for full conversation← Previous edit | Revision as of 01:31, 2 January 2009 view source John254 (talk | contribs)42,562 edits added commentNext edit → | ||
| Line 18: | Line 18: | ||
| ::::No worries. Just wanted to be sure. Thanks again for all your hard work. - ] (]) 12:52, 1 January 2009 (UTC) | ::::No worries. Just wanted to be sure. Thanks again for all your hard work. - ] (]) 12:52, 1 January 2009 (UTC) | ||
| :::::Anyhow, all fixed now. Thanks for pointing that out :) ] (]) 12:52, 1 January 2009 (UTC) | :::::Anyhow, all fixed now. Thanks for pointing that out :) ] (]) 12:52, 1 January 2009 (UTC) | ||
| ==Please ensure that images are correctly protected before placing them on the main page== | |||
| Thank you for updating ]. However, when placing images such as ] on the main page , it is necessary to ensure that they are either uploaded locally or protected at the commons, as instructed in the edit window for ]. Otherwise, vandals can replace the images with disgusting shock-site fare while they are displayed on the main page itself. Thanks. ] 01:31, 2 January 2009 (UTC) | |||
Revision as of 01:31, 2 January 2009
|
- For older discussion and other notes, please see the appropriate archive page.
My primary mission at the moment: Missing U.S. radio station articles
WTDR
Get ready for a change on WTDR. They have announced what is being speculated to be a format flip for January 5. They are currently running a promo saying they are about to become a "thing of the past." More details to you as they become available. Arob22 (talk) 03:25, 28 December 2008 (UTC)
- More information for you. From their website: "January 5, 2009, 7 AM, this station becomes a thing of the past". —Preceding unsigned comment added by Arob22 (talk • contribs) 02:33, 29 December 2008 (UTC)
- Wacky fun. Thanks for keeping track of this situation. - Dravecky (talk) 02:36, 29 December 2008 (UTC)
KUZZ History
I put the old history in my sandbox, or copied it in there, if that's O.K., so I can rewrite it up. The new history section for KUZZ will be more about 107.9 than AM 55, if that's o.k. The other one, if you agree was too long also. I've been wanting that off anyway to rewrite.--JoeCool950 (talk) 00:49, 1 January 2009 (UTC)
DYK rotation / Q4?
I know you've had a busy day and I'm so glad you were able to keep DYK running while so many folks, myself included, were very much out of pocket. There's no rush since it won't come up in rotation for about 10 hours from now but was there a specific reason you moved the Next Update hooks to queue 1 instead of queue 4? I appears that queue 4 should have been the next one filled. Oh, and happy new year! - Dravecky (talk) 12:15, 1 January 2009 (UTC)
- Don't know how you worked that out. The next two updates in line are for queues 2 and 3, which both have the last remaining New Year's Eve hooks. There are no updates at all ready in 4 and 5. Gatoclass (talk) 12:26, 1 January 2009 (UTC)
- Right, the current set on the main page was in queue 1 so the next set will load from queue 2. Then it'll load from queue 3, then 4, then 5, then 1 again so I would have expected that with 2 and 3 full and 4, 5, and 1 empty that you would have moved the latest set of hooks assembled in Next Update to queue 4 so they'd come up right after queue 3. - Dravecky (talk) 12:31, 1 January 2009 (UTC)
- Oh, okay, I see what you mean. What happened is that I manually bumped past queue #1 because the bot stopped working. Then I guess I copied the next update hooks into queue 1 instead of queue 4. Not sure why I did that, but I'd swear queue 1 was the only available slot at the time, perhaps I was getting confused with another time, because the queue has been chock full for the last few days. But yes, you are right, that update should have gone to queue 4 :) Gatoclass (talk) 12:48, 1 January 2009 (UTC)
- No worries. Just wanted to be sure. Thanks again for all your hard work. - Dravecky (talk) 12:52, 1 January 2009 (UTC)
- Anyhow, all fixed now. Thanks for pointing that out :) Gatoclass (talk) 12:52, 1 January 2009 (UTC)
- No worries. Just wanted to be sure. Thanks again for all your hard work. - Dravecky (talk) 12:52, 1 January 2009 (UTC)
- Oh, okay, I see what you mean. What happened is that I manually bumped past queue #1 because the bot stopped working. Then I guess I copied the next update hooks into queue 1 instead of queue 4. Not sure why I did that, but I'd swear queue 1 was the only available slot at the time, perhaps I was getting confused with another time, because the queue has been chock full for the last few days. But yes, you are right, that update should have gone to queue 4 :) Gatoclass (talk) 12:48, 1 January 2009 (UTC)
- Right, the current set on the main page was in queue 1 so the next set will load from queue 2. Then it'll load from queue 3, then 4, then 5, then 1 again so I would have expected that with 2 and 3 full and 4, 5, and 1 empty that you would have moved the latest set of hooks assembled in Next Update to queue 4 so they'd come up right after queue 3. - Dravecky (talk) 12:31, 1 January 2009 (UTC)
Please ensure that images are correctly protected before placing them on the main page
Thank you for updating template:did you know. However, when placing images such as File:Moet and glass.jpg on the main page , it is necessary to ensure that they are either uploaded locally or protected at the commons, as instructed in the edit window for Template:Did you know/Next update. Otherwise, vandals can replace the images with disgusting shock-site fare while they are displayed on the main page itself. Thanks. John254 01:31, 2 January 2009 (UTC)
