We recently updated to 0.18.0 and I haven’t really had a chance to fully test it. I took a snapshot before the upgrade, so we have a working state to roll back to if need be.
Please do not hesitate to post here. Rolling back snapshots will cause us to lose new posts that took place after I took the snapshot.
Checking mod-removed posts on the modlog returns a couldnt_find_post error instead of allowing them to be seen. Not sure if this is intentional but that was a tool whose accountability aspect i liked.
Checking on multiple accounts on this and other instances, the modlog loads for us, though we can only click through to the removed posts on an admin account. Is your issue specifically with trying to click through to see a removed post, or is it when trying to load the modlog at all?
Here’s how the modlog currently looks when loading it on a test account (hidden under a spoiler for those who don’t want to see.)
click to expand.
Then when actually trying to click through to see a removed post I get the following error on the test account:
This is the same across multiple instances, which are on the latest version of lemmy. Which tells us this might be an intentional change specifically to prevent regular users from seeing offending content. There doesn’t seem like there’s any easy way to remove this restriction on our end as it seems to just be part of the lemmy software.
There does seem to be a new setting which is ticked automatically in the new update to hide mod names (probably to further reduce their accountability.) This, fortunately, is a setting, and we have unchecked it, so the names of the actual mods who did the actions should show up now.
Hope this helps!~
Doing a quick check on changes from 0.17.4 to 0.18, seems like the most probable culpirit are these lines from this commit.
It doesn’t look like these changes were intentional either. Seems like the intent was on making deleted/removed posts not visible to non-mods/admins/creators on community post listings, rather than not visible at all.
I’ve got zero experience with asynchronous rust (or rust, for that matter), but this doesn’t seem too hard to change (other than a potential distinction between removed and deleted posts). i’ll still need to figure out how to make sure the changes don’t break something else in the process, though.
Absolutely not. We don’t want to be opaque about anything when it comes to running this instance.
It seems to be working for me both when logged in and logged out. Tried clearing your cache? The UI was updated since the recent update.
tried on desktop edge (114.0.1823.58, amd64-windows, never ran outside InPrivate) and on a fresh install of firefox for android (114.2.0) and the error message is returned both when logged out and logged in on both browsers - either as a toast on a blank page when accessing from a hyperlink or as a full error page when trying to access removed posts directly.
testing was done on https://burggit.moe/modlog/30 -> https://burggit.moe/post/2475 and https://burggit.moe/modlog/123 -> https://burggit.moe/post/28404 [nsfw].
I misunderstood the question. @Disabled@burggit.moe addressed it. Sorry for the confusion.