Weird behaviour in routing causes old messages to come back, sometimes after quite a while

[terminalvelocity23]

Somewhere around the introduction of 1.14.1 I've started to observe this odd behaviour of the network. I keep on seeing my and others old messages pop back into public, sometimes hours after the initial message has been sent.
My repeater has loop.detect set to moderate, but by default it's off, and maybe this has something to do with it.

Interestingly enough, there's apparently no loops in the path of the repeat messages. Here's an example:

[Magalex2x14]

There was a mention of this on discord not long ago. We have long noticed this in our network too. I can say for sure that it appeared before 1.13, maybe even before 1.12, I'm not sure. Rare messages from the past, 2 or more hours old, with the original timestamp. I didn’t raise this topic in public because we thought that someone was having fun like that (there were similar precedents), and until recently I had not heard of such issues.

https://discord.com/channels/1343693475589263471/1391673743453192242/1484712711437680843

[terminalvelocity23]

@Magalex2x14 maybe it's somebody having fun. It's a large mesh with over 350 repeaters, after all.

[Magalex2x14]

I'm starting to lean towards the bug...
If you and I are on "neighboring" networks, and the likelihood of someone’s "joke" is high, then Brian from Discord is obviously far away from us...
Maybe someone else will see this topic.