It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
We have a fix incoming :) for transparency: we exceeded 32bit integer...

Good news is that you'll get all of your unread notifications - probably today. (your notification bell should be flickering if you have any)
avatar
Johny.: for transparency: we exceeded 32bit integer...
That makes about 100 million notifications a day when it exceeds 32 bit within 6 weeks? Sounds a bit much...
At least we'll have a bit more time until it exceeds 64 bit. :)
avatar
Johny.: for transparency: we exceeded 32bit integer...
avatar
eiii: That makes about 100 million notifications a day when it exceeds 32 bit within 6 weeks? Sounds a bit much...
At least we'll have a bit more time until it exceeds 64 bit. :)
It's milliseconds until the notification expiration time.
avatar
Johny.: We have a fix incoming :) for transparency: we exceeded 32bit integer...

Good news is that you'll get all of your unread notifications - probably today. (your notification bell should be flickering if you have any)
Oh, I got them alright, but only on the "My posts" page, not in the bell - that's still flashing and not showing the number of pending notifications, and new (and older) pending notifications are still missing.

So the fix was implemented but there's a time delay in correcting the bell bug, or are we still waiting for the fix?
avatar
Johny.: It's milliseconds until the notification expiration time.
Oh, I thought it was some kind of a counter or index... But for a milliseconds timer 64 bit will help too. :)

avatar
HypersomniacLive: So the fix was implemented but there's a time delay in correcting the bell bug, or are we still waiting for the fix?
For me the notification bell worked again with Johny.'s reply.
Post edited October 18, 2017 by eiii
avatar
HypersomniacLive: So the fix was implemented but there's a time delay in correcting the bell bug, or are we still waiting for the fix?
avatar
eiii: For me the notification bell worked again with Johny.'s reply.
Yeah, it seems to be working just fine now. Thanks Johny. :)
Post edited October 18, 2017 by Lemon_Curry
avatar
eiii: [...] For me the notification bell worked again with Johny.'s reply.
I got the tab-titles flickering for your reply, but when I clicked on the bell to stop it, it showed the incorrect count increased by 1 and the "New reply in: The "what did just break" thread 2.0", but only for a split second before clearing it, i.e. it cleared before I opened this thread to read your reply.

Given this, and everything else I described above, I'd say that if it's fixed then it's not working for me, but good that it is for you.
I was just about to write that I spoke too soon and that it's not working again when, lo and behold, the correct number appeared next to the bell once I opened the 'Add new post' window – and only then (the bell had stopped moving and flashing long before that).

And once I posted the above message the number went back to 0 even though I still haven't checked the forum replies.
Post edited October 18, 2017 by Lemon_Curry
avatar
HypersomniacLive: So the fix was implemented but there's a time delay in correcting the bell bug, or are we still waiting for the fix?
avatar
eiii: For me the notification bell worked again with Johny.'s reply.
avatar
Lemon_Curry: Yeah, it seems to be working just fine now. Thanks Johny. :)
LOL :) The fix is not out yet! ;) And I'm not the one doing it, so I'll pass your thanks once it's out. :P

edit: fix is out.
Post edited October 19, 2017 by Johny.
avatar
Johny.: LOL :) The fix is not out yet! ;) And I'm not the one doing it, so I'll pass your thanks once it's out. :P

edit: fix is out.
And the notification again did not work for this reply! :P
(Maybe because you've quoted 2 posts?)
avatar
eiii: (Maybe because you've quoted 2 posts?)
Once more, quoting does not create notifications. Pressing reply does, even if no quote is in the text.
You should have gotten a notification for this reply though.
avatar
JMich: Once more, quoting does not create notifications. Pressing reply does, even if no quote is in the text.
Of course you can craft the quoting text also manually. But at least I usually press reply to get the text to quote. :)

Edit: I somehow doubt that pressing reply already generates a notification. I've pressed reply on every post on this page now. Let's see how many people get a notification... :P

Edit 2: Do you mean I have to post my answer with the same window which I have opened with the reply button and only then the forum software generates a notification (when the message gets posted)?
Post edited October 19, 2017 by eiii
avatar
eiii: Of course you can craft the quoting text also manually. But at least I usually press reply to get the text to quote. :)

Edit: I somehow doubt that pressing reply already generates a notification. I've pressed reply on every post on this page now. Let's see how many people get a notification... :P
Only the first one gets a notification, so if you actually used the reply button for this post of yours, only JMich will.
avatar
HypersomniacLive: Only the first one gets a notification, so if you actually used the reply button for this post of yours, only JMich will.
So you got a notification for Johny.'s answer in post 1194 because you were the first in the quote and I did not get one because I only was the second?

And did Lemon_Curry get a notification for that post because he was quoted separately?

Edit: Oops, sorry, I probably misunderstood you. Do you mean with "Only the first one gets a notification" the first pressed reply button?
Post edited October 19, 2017 by eiii
avatar
Johny.: edit: fix is out.
Did the fix involve reducing the maximum number of characters in a post? I've been trying for a while to post a 9k-something character post to no avail, and it only worked when I split it in two. :(