It doesn’t happen with posts from kbin.social, which suggests it’s a fixable issue at Project Segfault.
I know it’s a bigger problem that needs to be addressed at KBIN & Lemmy codebase level, but - until it’s resolved there - maybe there are solutions within this thread that could be implemented at your end.
It doesn’t happen with all KBIN->Lemmy interactions. I tested it with a KBIN site that I think is located in roughly the same geographical area as Project Segfault (UTC+2) but it didn’t have the same problem: https://lemmy.world/post/2336003 https://kbin-u3.vm.elestio.app/u/upstream
It’s the latest post for the KBIN test account (dunno why I can’t link to it, but the point is the timestamps are the same)
Our VMs are properly synced, it’s a known kbin bug but i haven’t seen if they solved it already. Once they do fix it i’ll update it.
It doesn’t happen with posts from kbin.social, which suggests it’s a fixable issue at Project Segfault.
I know it’s a bigger problem that needs to be addressed at KBIN & Lemmy codebase level, but - until it’s resolved there - maybe there are solutions within this thread that could be implemented at your end.
I set it to UTC around a week ago, are you still experiencing the same issue?
https://codeberg.org/Kbin/kbin-core/issues/799#issuecomment-994033
Yes. Compare:
https://lemmy.film/post/365555 (“posted 13 hours ago”)
https://kbin.projectsegfau.lt/m/[email protected]/t/18721/When-Will-the-Strikes-End-Lessons-From-1960 (“posted 15 hours ago”)
It doesn’t happen with all KBIN->Lemmy interactions. I tested it with a KBIN site that I think is located in roughly the same geographical area as Project Segfault (UTC+2) but it didn’t have the same problem:
https://lemmy.world/post/2336003
https://kbin-u3.vm.elestio.app/u/upstream
It’s the latest post for the KBIN test account (dunno why I can’t link to it, but the point is the timestamps are the same)