Admin Log

Same. I prefer ggoreo’s theme because of the stripes/accents, but it’s not worth the effort if it’s going to break with updates. I’ll always look back fondly at the ggoreo-themed days, though.

2 Likes

ggoreo for admin!

I’m super confused now, though - your theme wasn’t working before, right? There’s a reason why I switched away from Dark mode, right? I don’t need to see my doctor for dementia, right?

2 Likes

Grey works perfectly as far as I can tell. :+1:

widescreen theme 4lyfe, but if u don’t want to touch this shit anymore I 100% understand

no whatever i was using still looks perfect

Dark Theme with wide screen, dunno if you fixed something while i wasn’t on the site but nothing ever broke for me

Ppl on desktop not using this masterpiece of a theme are missing out. I use light on mobile for variety.

1 Like

Meh applying every beta release? Really?

Believe me I agree, but it is what they recommend

Beta here doesn’t really mean beta in the classical sense. Their beta branch is the latest most tested release branch.

1 Like

I tried it and yeah, that blue is hideous.

Switch to the Grey? It’s beautiful…

Dark theme looks really good @anon46587892. I’m really torn about what we should do about future updates.

What do you guys think? We can freeze here for a while - and only update on a new minor version (rather than going from 2.7.0beta(n) to 2.7.0beta(n+1) like we are doing now. But bigger leaps in updates makes it more likely for big breaking changes. Either way I’ll continue reading all the patch notes and updates.

Also keep in mind, I’m not sure that these updates are easily reversible. I have to take an afternoon and look into this stuff more deeply, before I apply the next update, whenever that is.

1 Like

We also should have a discussion as a forum on what to do when a user requests to have certain posts deleted, for whatever reason - trainwreck concerns, etc. I think it should only be done in circumstances that definitely warrant it - I’d hate a situation where a poster just threatens to nuke their account because they are pissy or whatever.

This came up last night and feel that there needs to be some policy here. @MrWookie if I want to start a straw poll to gauge interest on this, where do I do it? Open to any ideas here as well.

Start an RFC in About Unstuck on the subject. If opinion looks like it’s worth codifying something as a rule, then that process would have been started.

1 Like

So, the more we update the more likely we are to get bugs like this.

Unless they’re security fixes or offer some needed functionality why upgrade so often? Seems a lot of work for not much benefit.

It’s not a lot of work. It’s like 5 mins of my time, and I could even automate it.

They recommend updating often, that was the reason we are doing it. I’m leaning towards staying put until their next minor version and then staying at that minor version. I’m not gonna update these small beta releases anymore.

That doesn’t leave me much to do really, although I have a laundry list of small things and wish lists. In several months we will have to resize disk, that’s the major thing coming up.

Honestly though I’ve been very very busy so this works out this way for now.

Changed a username for a user with < 500 posts. Don’t see a big deal with it, we’ve done it before. The reason was because of doxxing concerns and the screenname being traced back to their real name. Because of that, I’m not gonna disclose who it is, they can do that themselves - but it seems like they mostly lurk so I doubt anyone will care. The new username is similar to the old one.

In other news, we are still sitting around ~45% disk usage which is what it was the last time I checked about a ~month ago. That’s really the only thing to monitor right now. Everything else looks fine.

Discourse notified me we can upgrade to a new beta version, which I’m not doing, because of what happened last time. We can upgrade when they hit a new minor version.

2 Likes

Yeah, unless a new beta version is set to fix a serious security flaw or other big time bug, I don’t see a great argument for always upgrading with every beta release. Minor versions seem fine.

Was messing around looking at site settings. I can set the number of hours mods will be notified if a flag is not dealt with. Would it be helpful to @moderators if this time limit was set to something like 4 hours? or would that just be annoying? Currently it’s 48 hours. Just asking because I saw the setting and considered changing it but want some feedback first.

noticing disk usage spikes up to 80% disk about once per week. I’m guessing these are the backups. This concerns me a little, but it’s not anything to worry about for a while. Leaving this here as a note to myself. I should resize disk sooner rather than waiting til it’s a real problem. full disk = really bad things start to happen

I think all I need to do is power off the forum, power off the VM, resize the droplet, power back on, redeploy discourse. Should be easy peasy. This will raise our bill though most likely.

I don’t think this really is all that helpful. There are sometimes instances where I’m not sure I have the context (or at least not the immediate time or will) to investigate something, but I want to make the notification go away. Ignoring on the flag makes it go away for all mods, though, and I don’t think we want to make it go away for all of us. Timing out is a similar issue.