This isn't the sort of bug you can describe with reproduction steps (or very easily with words for that matter), and it just seems like a curious inconsistancy I noticed today with the Trending system. Instead, please observe the following Anecdote with a simplified Trending page that only shows the Top Five most Trendy Threads of a particular Forums. [b]Expected:[/b] If All Topics sorted by Trending Looks like this... 1) #Destiny Thread A 2) #Destiny Thread B 3) #Offtopic Thread A 4) #Destiny Thread C 5) #Offtopic Thread B Then #Destiny Sorted by Trending should look like this... 1) #Destiny Thread A 2) #Destiny Thread B 3) #Destiny Thread C 4) #Destiny Thread D 5) #Destiny Thread E And #Offtopic sorted by Trending should look like this... 1) #Offtopic Thread A 2) #Offtopic Thread B 3) #Offtopic Thread C 4) #Offtopic Thread D 5) #Offtopic Thread E [b]Actual:[/b] If All Topics sorted by Trending Looks like this... 1) #Destiny Thread A 2) #Destiny Thread B 3) #Offtopic Thread A 4) #Destiny Thread C 5) #Offtopic Thread B Then #Destiny Sorted by Trending looks like this... 1) #Destiny Thread D 2) #Destiny Thread H 3) #Destiny Thread E 4) #Destiny Thread Z 5) #Destiny Thread Q And #Offtopic sorted by Trending looks like this... 1) #Offtopic Thread L 2) #Offtopic Thread R 3) #Offtopic Thread W 4) #Offtopic Thread X 5) #Offtopic Thread M If #Destiny Thread A and #Destiny Thread B are the top two trending #Destiny topics when you look at Trending for All Topics, then you would expect #Destiny Thread A and #Destiny Thread B to be the top two trending threads when you are only looking at #Destiny Topics, but this is not currently the case on Bungie.net. It's like the subforums are using a different Trending Algorithm than All Topics, and looking through the current #Destiny Trending list, I'm seeing threads that I'm pretty sure don't belong, like this [url=http://www.bungie.net/7_We-need-to-coordinate-our-Twitch--Twitter-Question/en/Forum/Post?id=61228729#referred-Destiny]thread of mine[/url] from July. If someone from the Webteam could investigate this, I'm sure they could find the source of the problem :) Thanks!