rs5th

If anyone else has made it this far and are thinking “ah balls, I’m using ingress-nginx”, here’s the ingress annotation for you!

nginx.ingress.kubernetes.io/configuration-snippet: |
            if ($http_accept = "application/activity+json") {
              set $proxy_upstream_name "lemmy-lemmy-8536";
            }
            if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"") {
              set $proxy_upstream_name "lemmy-lemmy-8536";
            }
            if ($request_method = POST) {
              set $proxy_upstream_name "lemmy-lemmy-8536";
            }

Here’s a cronjob to clean up the useless activity table every day:

apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: postgresql-cleanup
  namespace: lemmy
spec:
  schedule: "0 0 * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: postgres-cleanup
            image: postgres:alpine
            command: ["psql", "--host=postgresql", "--dbname=postgres", "--username=postgres", "--command=DELETE FROM activity WHERE published < NOW() - INTERVAL '1 day';"]
            env:
            - name: PGPASSWORD
              valueFrom:
                secretKeyRef:
                  name: postgresql
                  key: postgres-password
          backoffLimit: 0
          ttlSecondsAfterFinished: 3600

You did a Kubernete! Congrats!

Edit to add: one Kubernetes instance talking to another!

And then you’ll need to convince every instance admin to swap to this fork.

It uses Elon Musk’s Starlink satellite technology to communicate, though it is unclear if it was the cause of the loss of contact.

Surely this is the surface vessel and not the sub. Starlink communications are around 11 GHz, which can only propagate a couple meters in salt water.

The BBC live stream said “one pilot and four mission operators” about 15 min ago.

I believe the M900 has both a SATA port and a M.2 slot, so some options for internal storage.

You could also plug in a big spinning drive via USB 3. USB 3 can move data faster than a magnetic drive can pull it off the platters.

I think the question about “being on Beehaw” is because you’ve been commenting on a post in a Beehaw community.

Oh nice, that’s better than my solution. Less risky than downgrading.

This update, specifically how funding is happening, helped me understand some of the reasoning behind the narrow focus of the Lemmy developers. I appreciate them foregoing their regular paychecks to work on stability. Hopefully things settle down soon to the point that the extra eyes and hands on the project are more helpful than they are distracting.

This is a change with 0.17.4. You cannot have both federation enabled and the private instance box checked. You might try downgrading to the 0.17.3 image (so that you can get into the UI) and unchecking either the private or federation boxes (whichever way you wanna go). I’d also suggest pinning the docker image versions, as I bet you’ve got latest set (or nothing set, which I believe also grabs latest), and the vm reboot prompted docker to go grab the latest image on startup. Surprise upgrades probably aren’t what you want.

There’s no function in lemmy to track reasons in the admin interface, it’s a text box where you pass in a list of blocked instances. The Beehaw admins may maintain a list separately.