Sounds like a tradeoff most users would gladly accept. Makes sense from a technical standpoint certainly. Thanks again for all your guys' work.
Comment has been collapsed.
Lastly, the notification count in the navigation bar has been reset for everyone, so if you had previous unread messages listed there, you'll notice it's been cleared.
Ahh, finally...thanks for that.
Comment has been collapsed.
Do I have to change anything to receive notification and it will be an auto function ?
Comment has been collapsed.
How about disabling message notifications for comments posted in your own giveaways? Or at least make it an option. Many people don't like it because of the 'thank you spam' that results. Prior to SG v2 it was not like that and I think it was better for it.
Comment has been collapsed.
7 Comments - Last post 6 minutes ago by Chris76de
68 Comments - Last post 1 hour ago by vinirockman
346 Comments - Last post 1 hour ago by MCAlex
36 Comments - Last post 2 hours ago by Chris76de
915 Comments - Last post 2 hours ago by InSpec
25 Comments - Last post 4 hours ago by GeekDoesStuff
727 Comments - Last post 6 hours ago by InSpec
0 Comments - Created 3 minutes ago by Lugum
111 Comments - Last post 4 minutes ago by pb1
26 Comments - Last post 5 minutes ago by coleypollockfilet
19 Comments - Last post 5 minutes ago by ErhanT
226 Comments - Last post 17 minutes ago by GeekDoesStuff
29 Comments - Last post 24 minutes ago by Vasharal
1,568 Comments - Last post 44 minutes ago by Vasharal
We just rolled out a simple update to the way notifications are calculated in the navigation bar. Previously they would be calculated on the fly, which would take about 0.06 seconds for each page view in order to count your new messages across the site. This was less than ideal, because it slows down load time, and if we need to calculate this number for 10, 20, or 50 users in a second, it's a lot of strain on the database server.
The new method is simply caching it, so it has no affect on load time. Instead, when you post a comment, the cache is incremented for the appropriate user. If you post a comment on a giveaway, then the giveaway creator has their new messages incremented by one, and if your reply is in response to someone else, their notifications increment. Of course when you visit the messages page, and Mark as Read, this number is reset to zero.
This works well, but it may be slightly inaccurate at times. For example, if someone responds to one of your comments in a giveaway, and that giveaway is then deleted, your message count will still show you have a new message. However, when you visit the messages page, you simple won't see the message, since it's no longer available. An alternative would be recalculating the cache for all users in a deleted giveaway or discussion, but doing so for thousands of users might not be the best route. I think it's an acceptable trade off though, and it remains accurate 99% of the time, and we get faster load times for every page view, and less load on the database server.
Lastly, the notification count in the navigation bar has been reset for everyone, so if you had previous unread messages listed there, you'll notice it's been cleared.
Comment has been collapsed.