this post was submitted on 23 Jun 2023
16 points (100.0% liked)

Announcements

8 readers
1 users here now

Announcements/Changelogs go here.

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 years ago (5 children)

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.

[–] [email protected] 2 points 2 years ago (2 children)

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.

[–] [email protected] 3 points 2 years ago (1 children)

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].

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago)

I misunderstood the question. @[email protected] addressed it. Sorry for the confusion.

load more comments (2 replies)