I’m not sure what’s going on, but I’m noticing on the latest beta, that some posts (haven’t found a pattern) will open to a completely unrelated post.
Actually… usually it’s related to !TenForward, I’m not sure why (I could be wrong too). It’s something I’ve noticed maybe 5-6 times in the last couple of weeks?
I’ve linked to a screen recording, hopefully it’s obvious to you @CreatureSurvive
This is a peculiar one that I have not seen before. Had you noticed this at all before the latest beta release? I cannot think of anything that changed in that build that would have affected this.
I see some odd issues here where the post you clicked is showing mixed data. The post content and community name is that of the c/technology post, but then the community icon is for c/tenforward.
I see the post was created by a mbin user, perhaps it is due to a federation issue, or maybe the mbin api has changed and I need to update support.
Next time you encounter this, would you mind checking some of these details such a as post creator instance, post content all matches, etc.
I’ll start looking into this, thank you for informing me!
It’s happened on a previous beta, I can’t remember if it was the last one or the one before that.
I had it happen again yesterday. Not related to those two communities. Same issues, the feed showed one thing, but with mixed data (I think the community thumbnail was displaying the post that actually loads). I’ll make another video when I see it again 🙏
I spent all day trying to reproduce this issue without any luck. However I was finally able to track down where the mismatched data is being applied, and prevent it from happening, I’ll need to do a little more digging to find the root issue and properly fix it.
I might have time to finish this up tomorrow morning, if not I’ll definitely have a patch released sometime on Friday. Thank you for bringing this to my attention, it’s probably been hiding there in plain sight for a while now without being noticed.
Looking into it further, I’m not sure if I found the actual issue or not. However I did add some checks to try and ensure the prefetched data is not inserted in the wrong location. I’ll be releasing an update today, and it should hopefully resolve this issue.
Add comment