Christopher

I should elaborate, the blocklists are for Mastodon. I’ve not applied anything like this for Lemmy. I kind of just count on other server administrators and mods. 😬

https://gardenfence.github.io/

I administer my own instance of Lemmy and Mastodon. The CSAM issue was something I learned about real quick, unfortunately. I was able to implement community maintained blocklists. It’s not perfect, by any means, but I’ve not seen any more harmful content.

The idea of a centralized judicial system does not seem compatible with the spirit of federation. The safety we expect from centralized platforms is something we gave up for our freedom. With that, we do have to be diligent and deal with the bad actors. It’s the worst trade off in the whole deal.

It’s also impossible to enforce, I think. The Rage Against the Machine “f you, I won’t do what you tell me” spirit lives in all small server admins (by virtue of rebelling in the first place).

I’ve been putting it off, because it took me more than a year to migrate away from Gmail. But this is hard to ignore. I’m tired, fam.

Not a bad recommendation, but I disagree.

Rocket chat is just as heavy (in fact, it federates to Matrix), uses MongoDB, and has steadily pulled features behind a paywall for years. To me, if I’m hosting the service on my own machines and I’m not using their live support, the idea of paying for the privilege of using it is absurd.

Matrix has come a long way, including integrated voice and video chats.

Yes indeed. It’s now failing. 😞

Man, this kind of sucks.

I wrote a nifty script a few years ago that pulls the popularity metric of a song, converts that to a star rating, and writes that to a tag with Mutagen. At a glance I can see the hits. If I like the track, I’ll “love” it (side stepping the need for a personal rating). It’s a system that’s been serving me well for a long time.

Locking down APIs does seem to be the trend. I’m not sure I’ll look to adapt.

Giving money to Spotify is out of the question, but I may pay for Deezer or something.

How’d it work out?

I mean in terms of hijacking DNS. Might be worth a look.

It runs quite well; Docker’s not a full fledged virtual machine so much as a virtualization layer. I also love the portability of running this in Docker. I rsync a backup of this and the Appdata folder every night. When or if this server fails, I can be up and running again in minutes on another machine.

Is your ISP interfering?

services:

  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: sheldon
    environment:
      HOST_CONTAINERNAME: pihole
      TZ: ${TZ}
      WEBPASSWORD: ${WEBPASSWORD}
      DNSMASQ_LISTENING: "all"
      PIHOLE_DNS_1: "unbound#53"
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "8080:80/tcp"
    # network_mode: host
    dns:
      - 127.0.0.1
    networks:
      dns:
        ipv4_address: 172.22.0.2
    volumes:
      - /mnt/appdata/pihole/etc-pihole:/etc/pihole
      - /mnt/appdata/pihole/etc-dnsmasq.d:/etc/dnsmasq.d
    restart: unless-stopped
    depends_on:
      unbound:
        condition: service_healthy

  unbound:
    container_name: unbound
    image: klutchell/unbound:latest
    networks:
      dns:
        ipv4_address: 172.22.0.3
    volumes:
      - /mnt/appdata/unbound:/opt/unbound/etc/unbound/custom
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "dig", "google.com", "@127.0.0.1"]
      interval: 10s
      timeout: 5s
      retries: 5

  wg-easy:
    container_name: wg-easy
    image: ghcr.io/wg-easy/wg-easy:15
    ports:
      - "51820:51820/udp"
      - "51821:51821/tcp"
    # environment:
    #   TZ: ${TZ}
    #   LANG: en
    #   WG_HOST: ${WG_HOST}
    #   PASSWORD_HASH: ${PASSWORD_HASH}
    #   WG_DEFAULT_DNS: 172.22.0.2
    #   WG_MTU: 1420
    networks:
      dns:
        ipv4_address: 172.22.0.4
    volumes:
      - /mnt/appdata/wg-easy:/etc/wireguard
      - /lib/modules:/lib/modules:ro
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    sysctls:
      - net.ipv4.ip_forward=1
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv6.conf.all.disable_ipv6=0
      - net.ipv6.conf.all.forwarding=1
      - net.ipv6.conf.default.forwarding=1
    restart: unless-stopped

networks:
  dns:
    external: true

Feel free to just delete the wg-easy service.

Very well could be!

Lineage sounds a lot like “Linux.” Take it easy on the lad.

I think a lot of it is anxiety; being replaced by AI, the continued enshitification of the services I loved, and the ever present notion that AI is, “the answer.” After a while, it gets old and that anxiety mixes in with annoyance – a perfect cocktail of animosity.

And AI stole em dashes from me, but that’s a me-problem.

Nope. I’m running three Pies and a custom UNRAID build.

Share the loooaaaaad.

Pi 5 with a 1TB NVMe strapped to it. Pixelfed, so far, is sipping resources; Mastodon, on the other hand…

I’ve doubled my server load from one user… to two.