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.
realcaseyrollins@kbin.projectsegfau.lt 2 years ago
Not my instance but thanks for the heads up
@Midou @arya apparently the timestamps are off here
Midou@kbin.projectsegfau.lt 2 years ago
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.
freamon@endlesstalk.org 2 years ago
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.
arya@kbin.projectsegfau.lt 2 years ago
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