I never remember this happening. Unless the Kazon make a return in S6/S7 (as I haven’t finished those yet), the closest thing was the Silver Blood Harry™ (died with the rest of the duplicate ship) or the Deadlock Duplicate Harry™ that replaced the Harry that was killed when attempting to repair a hull breach.

Everyone knows the old rhyme, “Step in a cargo hold, break your back.”

I did a reverse image search, and I guess it’s by someone named Moosoppart.

They even have a page about the past tense written in the past tense.

Isn’t that a stylistic constraint of all Memory Alpha wiki submissions?

I’m just glad that I can resell microphone windscreens as Tribble plushies if I ever need another source of income.

I had no idea FOSS tax software was a thing. Huh. I’ll try and play around with it at some point and let you know.

I guess these guys are just plain old tools.

It’s fine, the plot of the next (and all subsequent) episodes forgot about that for him.

The little I’ve seen of Joe seems like this:

Some rich guy you’ve never heard of: “So, umm, yeah, I’ve been trying this new form of yoga.”

Joe: hits blunt and drinks something harmful “Oh yeah?”

Guy 1: burp “Yeah, and it’s really opened my eyes and shit, y’know?”

Joe: “Oh really?”

(This but for who knows how long).

I forgot: are Lemmy’s active and hot sorts chronological? They’re pretty decent, but I do find stale content does get stuck on one that isn’t there on the other.

Tbh, I haven’t really had this issue in a few weeks. I’m tempted to think it’s usage-related, and could possibly indicate that my memory allocation for the DB is still too high.

I had this issue in Firefox as well. Does Firefox automatically block embedded image links from Imgur? It goes without saying that Tor is based on Firefox.

The max_client_body_size setting in a few of the nginx config files needs increased. I don’t have the link handy, but it’s basically something you need to edit in both the /srv/lemmy internal config and several of the nginx external ones. The external ones are in a standard path for nginx installs, so a quick look for help on StackOverflow is how I got mine sorted.

You can if you want. Reply here with the link if you do (or mention me if that’s a thing on Lemmy).

Yeah, mine have technically happened after reboots, although things typically take a few days at least for the problem to creep up. This past time, I basically have a whole entire week in before things went to crap.

I did that a while ago, and unfortunately, it didn’t really help. I don’t think it’s an issue of RAM, but rather a daemon or something periodically going nuclear with resource utilization. A configuration issue, perhaps?

The problem is that an update will inherently involve a restart of everything, which tends to solve the problem anyway. Whether the update fixed things or restarting things temporarily did is only something you can find out in a few days.

I’ll save this to look at later, but I did use PGTune to set my total RAM allocation for PostgreSQL to be 1.5GB instead of 2. I thought this solved the problem initially, but the problem is back and my config is still at 1.5GB (set in MB to something like 1536 MB, to avoid confusion).

This issue occured a few weeks ago as well, even when we had very little traffic. We still have peanuts when compared with other instances.