Receiving notifications for stale new threads

[osaerisxero]

Describe the bug
I have notifications set to 'loud' for /m/@networking@sh.itjust.works. A few minutes ago, I receieved a notification of a 'new' thread which was actually over 8 months old.

On which Mbin instance did you find the bug?
kbin.melroy.org

Which Mbin version was running on the instance?
1.9.0-rc1

To Reproduce
unknown

Expected behavior
Notifications to pop for new items only.

Screenshots
Thread: https://kbin.melroy.org/m/networking@sh.itjust.works/t/1346971/New-home-need-direction
Notifications pane:
https://files.catbox.moe/wi8ofw.png

Desktop (please complete the following information):
Arch w/ KDE Plasma
Firefox

[osaerisxero]

Happened again just a few minutes ago lol

https://files.catbox.moe/vcsypr.png

https://kbin.melroy.org/m/networking@sh.itjust.works/t/1346993/Options-for-under-performing-Cat6-cable

@melroy89 may need to take a peek under the hood to find out more, but it doesn't seem like it was a one-off

[melroy89]

I can't access those pngs. Upload your images directly on github plz.

[osaerisxero]

Ah, my bad.

[BentiGorlich]

Makes sense to prevent that. My guess is that these threads are new for your server but not new on the other end. That could happen because someone upvoted a thread your instance did not knew about and fetched afterwards. So the thread got newly created on your instance because of that, but it was initially created a year ago (just as an example).

[blued-gear]

Is this solvable by simply preventing firing the notification if the subject is older than -lets say- 2 days?