Something with how the ui handles ban lengths that arn't permanent but are still far far in the future.
If you're an instance owner you can fix it by making those bans permanent by editing the database
Something with how the ui handles ban lengths that arn't permanent but are still far far in the future.
If you're an instance owner you can fix it by making those bans permanent by editing the database
I'm unsure how the whole cross-posting thing works, so I'm copying my comment from a cross-post here too, let me know if this is bad and how to approach cross-post comments correctly.
I had the same problem. Yesterday I could access the modlog from the lemmy.ml instance but it had a lot of repeated entries. Like a lot.
So yeah, something's weird. On the lemmy-ui issue tracker there's this: issue#1905 but I haven't had the time to read it, I only skimmed it.
It was broken quite some time ago but upon checking again it seems to be fine again. Good to know I wasn't the only one.
There was a bug going on (no limit on banned days) I think it may be a part of that.
It doesn't work from my own instance too.
Hackers broke it
What happened?
Theyve been sending federation events with times far into the future. So far that it breaks the lemmy frontend. Theyre federated, so obviously it breaks it on every instance
Support / questions about Lemmy.