Problem with creating new sections ?

[OmegaStarScream]

So once theymos created the new sections "Online wallets" and "exchanges" on the Service discussion section , I'm having this issue ...

No one is posting on the threads however ... they keep getting added when I click "Show new replies to your posts" , and even if I make them as "Mark as read" , I wait more minutes and they get  on that list once again  


EDIT : When I first made this thread I had nothing on the "Show new replies to your posts" , after (let's say 10-20mn) I refreshed the page and I have this :



As you can see , those threads are inactive since April so I'm not sure why they are listed there.


EDIT 2 : Once again :

[1713875653]

1713875653

[1713875653]

1713875653

[1713875653]

1713875653

[Lauda]

How you tried testing this from another account (in the case that you do have one)? I've tried to reproduce the results and have failed so far, this is what I see 10+ minutes after using 'mark read':


Have you tried to reproduce this in another section? I'll ping theymos just in case. Try reproducing it under different intervals and with different threads, that should help identify the cause quickly.

[OmegaStarScream]

I only tried it in this account honestly and the issue came only for threads that got moved to exchanges and online wallets (the new sections).
I'm not sure but it could have something to do with the server time or something like that, theymos should take a look at the algorithm that gives us that list on the Unread replies https://bitcointalk.org/index.php?action=unreadreplies


EDIT (See the two last are from October 2015):







Now It didn't happen after 10-20mn (It happened after hours) so as I said I guess it has something with the date of other threads on that section or something like that.


EDIT 2 :

[theymos]

I think that I fixed the bug. I think that any topic movement of a rather old topic could've done that, but you only saw it now because so many topics were moved.

[OmegaStarScream]

I think that I fixed the bug. I think that any topic movement of a rather old topic could've done that, but you only saw it now because so many topics were moved.

Alright , I guess it's fixed since I didn't get it till now. I will keep you updated ! thanks