I know that sometimes in the 30 minutes or so after we hit a "new day" on the UMD clock, there are some weird discrepancies in the various displays of WOTD. That seems like it's just a matter of not everything updating at the same time. But the screenshots below were just taken a few minutes ago, at 2:30pm EST, which is almost 15 hours after the daily changeover.
On one page, Jayce is somehow both Wammer of the Day AND the #1 runner-up. In the other, we've got Greenslimeme as WOTD and Jayce as runner-up #1.
Another very notable fact: Neither of these folks was the WOTD for the previous day, that was MessyFoxPup (at least according to the UMD's WOTD history), so this isn't an issue of one of the two pages "hanging up" and retaining yesterday's winner.
Click on the link below to see the screenshots I took that illustrate this problem. I put the URLs of both pages at the top of the screenshot for reference.
Pie Romaine-y Yak said: I know that sometimes in the 30 minutes or so after we hit a "new day" on the UMD clock, there are some weird discrepancies in the various displays of WOTD. That seems like it's just a matter of not everything updating at the same time. But the screenshots below were just taken a few minutes ago, at 2:30pm EST, which is almost 15 hours after the daily changeover.
On one page, Jayce is somehow both Wammer of the Day AND the #1 runner-up. In the other, we've got Greenslimeme as WOTD and Jayce as runner-up #1.
Click on the link below to see the screenshots I took.
I have noticed some strange things as well during the daily transition but that transition can take a few hours to complete - which is rather odd. Mainly things on the home page and the updates of the day are not updating along with the other daily turnover which is midnight East Coast USA time. I really didnt think too much into it but it is interesting if it can be resolved.
More than likely your browser is just caching the previous version--once the timeout expires your browser should just automatically fetch the newer version. Or you can try manually clearing the cache entry containing that page (can usually just google how to do this)
vladmesy said: More than likely your browser is just caching the previous version--once the timeout expires your browser should just automatically fetch the newer version. Or you can try manually clearing the cache entry containing that page (can usually just google how to do this)
With all due respect, I don't see how that can possibly be the issue here. As I mentioned in my first post, neither Jayce nor Greenslimeme were the WOTD for yesterday...nor in the past several weeks (I've just gone back through the WOTD history to check on this.) Greenslimeme hasn't even been a #1 runner-up in the past two weeks, and Jayce was the #1 runner up just once in this period, about a week ago.
I mention the top runner up positions because MM has said that past WOTDs are always dynamically updating -- they're actually re-calculated daily. That is, if a previous WOTD winner deletes a bunch of their older pics, they lose the votes garnered by those pics for that past day's count. So although you might've been WOTD on January 14th, say, if you delete all of your photos that got heart-clicks on January 14 and then scroll that far back in the WOTD history, the original #1 Runner-Up on that day will now very likely be listed as WOTD for Jan. 14th (unless they deleted their pics that got votes that day too.) So you CAN change the past, haha. Kind of blows my fragile eggshell mind.
It's quite possible it is a legit bug. I just know from experience 99% of the time issues like these are related to caching issues and can *usually* be confirmed as a caching issue or resolved by either clearing cache or opening up a private browser
I also know from experience that combining caching with dynamically changing data can produce some VERY strange/unpredictable behavior, which might be part of what you're seeing
It's partially a caching issue. Both Jayce and greenslimeme ended up with the exact same internal score yesterday, so when calculating top user the database ordering is sorta undefined between the two. Upon a page request, it'll pull either one pretty much at random and then cache it like that. Something I'll have to work on....
maybe next time we have a tie? we can have the pic and whatnot ready for two spaces. like a photoshopped pic of the two people and spaces for the two names! ties happen! thanks for wotd and congrats greenslime!