Because there's not a bounds check in place when the admin enters a ban length. If you exceed those bounds then it won't render the mod log stating there's an invalid time value when checking the backend logs because some admin entered 100000000000000 for the ban length, and it can't display that length.
this post was submitted on 30 Aug 2023
5 points (100.0% liked)
Ask Burggit!
173 readers
3 users here now
Ask Burggit!
Ever had a question you wanted to ask? Get an opinion on something?
Well, here's the place to do it! Ask the community pretty much anything.
Rules:
- Follow the rules of Burggit.moe
- Not intended for tech support or questions for Burggit staff.
founded 1 year ago
MODERATORS
Thats idiotic.
Yeah, I was ranting about it in the Matrix server when I discovered that after banning a spammer for such an incomprehensible huge length of time. I'm not 100% positive this is the cause of it, but it immediately prints the error when you visit the modlog page. I really wish they had a shortform for permabanning. Like setting the time value to -1 means it doesn't expire or something of the sort.
Just doing something like 99 year bans would be sufficiently permanent as far as human lifespans and internet forums go, no?
Very true. But you can't specify units for how long a ban lasts. IE 1D, 1M, 1Y, etc. The default unit is in days. It's easier just to type 1000000000 because I just want the stupid bot/CP posting asshat gone for good.
That's... Stupid. I figured from modlogs I've seen that years were allowed since I've seen a lot of 27 year bans from various communities
Hey, btw how do i report a account to the admins? There is a account that spams around BS in my community.
Its @PixelKaya for reference.
You just use the same report link from within the community you're browsing. Admins get notified of reports regardless if it's a community matter or sitewide matter.
Ah ok 👌
Hm my mod log just doesn't load at all, only the local mod logs from my community do.
Hope there will be a fix for that in the next update. This is pretty idiotic and avoidable.
What do you mean?
How so? I haven't had any issues with it, but I also wasn't really looking for any
I've only seen it break when checking the global modlogs, but that's been already broken for a while. I don't know whether the update to 0.18.4 broke it, its growing size broke it or some malicious federated action broke it. Have you checked any local-only instances?
Hm, seems like the mod logs for individual communitys work. Hope they fix this soon.