u/ferriematthew

How do people deal with this crap? I live in an apartment complex where there are a lot of young families with very young children, and in the middle of summer especially, it's almost constant that they will be outside playing in the pool as kids do and being very loud. Now, that's their right and I'm happy kids are having fun, but there's something very specific about the sound of a child's voice when they're screaming and just being a child that makes me want to pull my hair out. How do you guys deal with this very specific kind of sensory emotional triggering?

At least now the pods are not crashing, but I can't seem to be able to sign in to my instance using the Tailscale app.

I just thought of something that I hope is kind of clever. Data centers take electrical power as input and use it to do math, but the input and the output are both in the form of electrical signals. the output electrical signals just go on to drive displays or whatever.

Any kind of electrical current traveling through anything but a superconductor loses some energy and dissipates it as heat. Heat has to go somewhere to avoid cooking the device, so at this scale it usually is disposed of through very complex thermal management systems that require additional power, and in doing so generate additional heat.

There's an old gamer meme about low quality pictures being rendered on a toaster. When somebody renders an image with AI, they are literally rendering their picture on a big toaster.

I created a GCP account years ago for some Coursera course, and I don't plan to ever use it for anything real. Lately, I keep getting annoying emails about my old card being expired, which doesn't matter since I'll never use any paid service anyway. How do I delete just my GCP account without touching my Google account?

As far as I can tell the DNS setup is at least approximately correct, but the one thing I have not checked yet is that netbird is actually using the internal Traefik proxy that k3s uses. I've shared my code at least a few times in previous posts so it would be redundant to share it again, but based on previous posts, can anyone help me find where I might have messed up in the reverse proxy? Of course I will be combing through the code myself as well, that way I'm not entirely relying on other people.

I was able to successfully slap together something that approximately looked vaguely like a rocket, even though I wasn't able to launch it or load any other examples. But at least parts didn't clip through each other!

The one thing I think is missing, unless I'm just being oblivious and not sure how to activate it, is scale snapping. For example, if I'm rescaling the diameter of a fuel tank I would like to be able to scale the X and Y dimensions in lock step so that it remains circular, and also for it to be able to optionally snap to the diameter of whatever it's attached to.

Since my last post, what I did was to modify my PiHole deployment to listen to all interfaces so that it would hypothetically be able to see the WireGuard interface that Netbird uses. I'm not sure what to configure or how inside the Netbird settings though in order to make Netbird use PiHole. I know that PiHole is accessible on my internal network on the 192.168.0.0/24 subnet, and that my particular Netbird network uses the 10.0.0.0/8 subnet (which is probably way too big). I think the question I need to ask is how do I make the two completely different networks communicate.

I almost have something that works... almost... based on an amalgamation of examples from a web search... When I go to start it though, k3s gives me an infinite loop of ErrImagePullBackoff.

My code (or what I synthesized from lots of searching):

Note: I remembered to encrypt the web password so that being out in the open is actually fine for security.

Am I trying to access an image that doesn't exist?

apiVersion: v1
kind: Namespace
metadata:
  name: pihole
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pihole-config
  namespace: pihole
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn-ssd
  resources:
    requests:
      storage: 1Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pihole-dnsmasq
  namespace: pihole
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn-ssd
  resources:
    requests:
      storage: 1Gi
---
apiVersion: bitnami.com/v1alpha1
kind: SealedSecret
metadata:
  name: pihole-webpassword
  namespace: pihole
spec:
  encryptedData:
    FTLCONF_webserver_api_password: AgBtuD3myKgNwDFyuPZFVGxQ44XrVo7zEtWS8/WlwLn4ny5lptpOBBk2+DfQ4MFILvn1CN072R1g8fBqlP3xG+ByWQQDE+NGpVwXKhcylvEBTC2lp+s/xiLfCOnt9r82jtBuFAAU8LzfVJgjVid4Rba8aEiJxg4bRCOSb5BOvzygZbvY1EUFejMIiUIHD9SSk6ZFghUTvR360mBzxj07dSJRkIFRbITXk7gpnB2sRjAAeWIHilorxqneztxbUsRJ9x9J/tChXhcnU3bAjqEM0BDyD6bu4l7mcoj6PTTg0lJYzQFTbHIhzYHDWcS35fxVgExR3/lDotQNxIJ6B0+UWTqvhvKlQ1MG6nPG7/F8YMddWsvV4PCZtipuVeNLwT54Ej2f/qYcWshGuyleTq+6VgQLiE9EUnDndCDkqWDNWNXCmWsiN1NG7SxXZOBd0RXWPuL44qn/7bOUhKPpmDtxqY2Gc3yZ+Bh/JPKRgbPo0J+o8z9zZxBbVT57CPDsNa/qjOcDixjPyXkziWINoSuNDEZ6vurVOpzdmFq6TjQX6uquIiiwBe+OEV5w0M35ePu77zNWen+VPBGs+eM4zc7/DgaR05eTlBk7DQqFW4BOCRbLxioOkPY5oPnh9cqw113Wv9NNRnnYT3R5dnzP75FMidt69et4hDggUYYHAfS6Tm50XcwkaOLoQ513c4o6XiJtvJp1V2j5E6vCj+KJ1w==
  template:
    metadata:
      name: pihole-webpassword
      namespace: pihole
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: pihole-unbound
  namespace: pihole
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pihole-unbound
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: pihole-unbound
    spec:
      containers:
        - name: pihole-unbound
          image: mpgirro/pihole-unbound:2026.06.0
          ports:
            - containerPort: 443
              protocol: TCP
            - containerPort: 53
              protocol: TCP
            - containerPort: 53
              protocol: UDP
            - containerPort: 80
              protocol: TCP
          env:
            - name: TZ
              value: America/Chicago
            - name: FTLCONF_webserver_api_password
              valueFrom:
                secretKeyRef:
                  name: pihole-webpassword
                  key: FTLCONF_webserver_api_password
            - name: FTLCONF_dns_upstreams
              value: 127.0.0.1#5335
            - name: FTLCONF_dns_listeningMode
              value: single
            - name: FTLCONF_dns_dnssec
              value: 'true'
            - name: FTLCONF_dns_revServers
              value: '1.1.1.1;1.0.0.1'
          volumeMounts:
            - mountPath: /etc/pihole
              name: pihole-config
            - mountPath: /etc/dnsmasq.d
              name: pihole-dnsmasq
          livenessProbe:
            httpGet:
              path: /admin
              port: 80
            initialDelaySeconds: 30
            periodSeconds: 30
            failureThreshold: 5
          readinessProbe:
            httpGet:
              path: /admin
              port: 80
            initialDelaySeconds: 15
            periodSeconds: 10
          resources:
            requests:
              memory: "128Mi"
              cpu: "100m"
            limits:
              memory: "512Mi"
              cpu: "500m"
      volumes:
        - name: pihole-config
          persistentVolumeClaim:
            claimName: pihole-config
        - name: pihole-dnsmasq
          persistentVolumeClaim:
            claimName: pihole-dnsmasq
---
apiVersion: v1
kind: Service
metadata:
  name: pihole-dns
  namespace: pihole
  annotations:
    metallb.io/loadBalancerIPs: 192.168.0.201
spec:
  type: LoadBalancer
  selector:
    app: pihole-unbound
  ports:
    - name: dns-tcp
      port: 53
      targetPort: 53
      protocol: TCP
    - name: dns-udp
      port: 53
      targetPort: 53
      protocol: UDP
---
apiVersion: v1
kind: Service
metadata:
  name: pihole-web
  namespace: pihole
spec:
  type: ClusterIP
  selector:
    app: pihole-unbound
  ports:
    - name: http
      port: 80
      targetPort: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: pihole-web
  namespace: pihole
  annotations:
    spec.ingressClassName: "traefik"
spec:
  rules:
  - host: pihole.lan
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: pihole-unbound
            port:
              number: 80apiVersion: v1
kind: Namespace
metadata:
  name: pihole
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pihole-config
  namespace: pihole
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn-ssd
  resources:
    requests:
      storage: 1Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pihole-dnsmasq
  namespace: pihole
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn-ssd
  resources:
    requests:
      storage: 1Gi
---
apiVersion: bitnami.com/v1alpha1
kind: SealedSecret
metadata:
  name: pihole-webpassword
  namespace: pihole
spec:
  encryptedData:
    FTLCONF_webserver_api_password: AgBtuD3myKgNwDFyuPZFVGxQ44XrVo7zEtWS8/WlwLn4ny5lptpOBBk2+DfQ4MFILvn1CN072R1g8fBqlP3xG+ByWQQDE+NGpVwXKhcylvEBTC2lp+s/xiLfCOnt9r82jtBuFAAU8LzfVJgjVid4Rba8aEiJxg4bRCOSb5BOvzygZbvY1EUFejMIiUIHD9SSk6ZFghUTvR360mBzxj07dSJRkIFRbITXk7gpnB2sRjAAeWIHilorxqneztxbUsRJ9x9J/tChXhcnU3bAjqEM0BDyD6bu4l7mcoj6PTTg0lJYzQFTbHIhzYHDWcS35fxVgExR3/lDotQNxIJ6B0+UWTqvhvKlQ1MG6nPG7/F8YMddWsvV4PCZtipuVeNLwT54Ej2f/qYcWshGuyleTq+6VgQLiE9EUnDndCDkqWDNWNXCmWsiN1NG7SxXZOBd0RXWPuL44qn/7bOUhKPpmDtxqY2Gc3yZ+Bh/JPKRgbPo0J+o8z9zZxBbVT57CPDsNa/qjOcDixjPyXkziWINoSuNDEZ6vurVOpzdmFq6TjQX6uquIiiwBe+OEV5w0M35ePu77zNWen+VPBGs+eM4zc7/DgaR05eTlBk7DQqFW4BOCRbLxioOkPY5oPnh9cqw113Wv9NNRnnYT3R5dnzP75FMidt69et4hDggUYYHAfS6Tm50XcwkaOLoQ513c4o6XiJtvJp1V2j5E6vCj+KJ1w==
  template:
    metadata:
      name: pihole-webpassword
      namespace: pihole
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: pihole-unbound
  namespace: pihole
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pihole-unbound
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: pihole-unbound
    spec:
      containers:
        - name: pihole-unbound
          image: mpgirro/pihole-unbound:2026.06.0
          ports:
            - containerPort: 443
              protocol: TCP
            - containerPort: 53
              protocol: TCP
            - containerPort: 53
              protocol: UDP
            - containerPort: 80
              protocol: TCP
          env:
            - name: TZ
              value: America/Chicago
            - name: FTLCONF_webserver_api_password
              valueFrom:
                secretKeyRef:
                  name: pihole-webpassword
                  key: FTLCONF_webserver_api_password
            - name: FTLCONF_dns_upstreams
              value: 127.0.0.1#5335
            - name: FTLCONF_dns_listeningMode
              value: single
            - name: FTLCONF_dns_dnssec
              value: 'true'
            - name: FTLCONF_dns_revServers
              value: '1.1.1.1;1.0.0.1'
          volumeMounts:
            - mountPath: /etc/pihole
              name: pihole-config
            - mountPath: /etc/dnsmasq.d
              name: pihole-dnsmasq
          livenessProbe:
            httpGet:
              path: /admin
              port: 80
            initialDelaySeconds: 30
            periodSeconds: 30
            failureThreshold: 5
          readinessProbe:
            httpGet:
              path: /admin
              port: 80
            initialDelaySeconds: 15
            periodSeconds: 10
          resources:
            requests:
              memory: "128Mi"
              cpu: "100m"
            limits:
              memory: "512Mi"
              cpu: "500m"
      volumes:
        - name: pihole-config
          persistentVolumeClaim:
            claimName: pihole-config
        - name: pihole-dnsmasq
          persistentVolumeClaim:
            claimName: pihole-dnsmasq
---
apiVersion: v1
kind: Service
metadata:
  name: pihole-dns
  namespace: pihole
  annotations:
    metallb.io/loadBalancerIPs: 192.168.0.201
spec:
  type: LoadBalancer
  selector:
    app: pihole-unbound
  ports:
    - name: dns-tcp
      port: 53
      targetPort: 53
      protocol: TCP
    - name: dns-udp
      port: 53
      targetPort: 53
      protocol: UDP
---
apiVersion: v1
kind: Service
metadata:
  name: pihole-web
  namespace: pihole
spec:
  type: ClusterIP
  selector:
    app: pihole-unbound
  ports:
    - name: http
      port: 80
      targetPort: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: pihole-web
  namespace: pihole
  annotations:
    spec.ingressClassName: "traefik"
spec:
  rules:
  - host: pihole.lan
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: pihole-unbound
            port:
              number: 80

He seems to really only care about people praising him and he doesn't really care what kind of praise he gets. As an example, recently some of the newly elected progressive leaders in New York state managed to butter them up by I think buying some tongue in cheek headlines with obvious flattery.

Would this actually work or would the voter base run away screaming?

I don't know how I did it but I tried to add the unbound container to my pihole deployment in k3s, and initially I didn't change anything else except adding that one container, but when I went to deploy it, I encountered cascading errors that every time I fixed one, two more would pop up and now I can no longer use my DNS server.

I can't even revert reliably because I had all 20 something of my services cnamed to the IP of pihole so everything was on the same IP address. This means that when I tried to revert, pihole was no longer able to bind to the IP address because everything else was on it all at once at the same time.

How do I recover from this?

The rest of the motherboard is perfectly functional, but I had to rebuild my entire PC a couple years ago based on a totally new one because of what I suspect is a dead RAM controller.

How do I test it to make sure that everything else is functional and to confirm that it is in fact the memory controller that is dead?

I want to add unbound to my DNS stack, on a k3s cluster that includes both ARM and x86 machines. I know that the normal unbound image does not work on ARM, but is the reverse true as well?

Title: BREAKING: EVERY ZOHRAN ENDORSED CANDIDATE WINS!!! CLEAN SWEEP FOR DEM SOCIALISTS!!! by Secular Talk on YouTube

Looks like democratic socialism as a whole and specifically the DSA are on a roll! I don't want to be too optimistic too early, but I feel like 2028 is going to be a great year for the left.

When I try to connect to my instance over ssh, the terminal complains that port 22 is unreachable in the pod. It does the same thing when I try explicitly using port 2222, which is the port that the service actually listens to.