That’s only with Sync. But the notes are just markdown, so you can also just use GitHub or whatever to sync them. They never need to hit Obsidian’s servers, and that’s actually the default because you have to pay for Sync.

That’s actually a big negative compared to Obsidian. It’s just a bunch of markdown files in a folder, so you can sync them using e.g. git and manage conflicts that way

How does this differ from Obsidian?

Not for PiHole but I was testing this recently with traefik. This has a bunch of traefik stuff in there (I’m on mobile so it’s too hard to edit it) but hopefully you see how the networks work

# Testing macvlan setup for traefik
# Will only work on linux because of macvlan network

version: '3'

services:
  traefik-whoami:
    image: traefik/whoami
    container_name: traefik_whoami
    networks:
      - bridge_network
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.whoami.rule=Host(`whoami.test`)"
      - "traefik.http.routers.whoami.entrypoints=http"
  
  traefik-reverse-proxy:
    image: traefik:v2.10
    container_name: traefik_reverse_proxy
    command:
      - "--api.insecure=true"  # Enable the API dashboard (insecure for testing)
      - "--providers.docker=true"  # Enable Docker provider
      - "--providers.docker.exposedbydefault=false"  # Disable exposing all containers by default
      - "--entrypoints.http.address=:80"  # HTTP entrypoint
      - "--entrypoints.http.forwardedheaders.insecure=true"  # Insecure forwarding (for testing)
      - "--providers.docker.network=bridge_network"  # Use bridge network for traefik discovery
    ports:
      - "1180:80"  # Expose HTTP entrypoint
      - "12345:8080"  # Expose Traefik dashboard
    networks:
      bridge_network: {}
      macvlan_network:
        ipv4_address: 192.168.1.69
    volumes:
      # TODO: Use docker.sock proxy instead of mounting directly
      # https://github.com/Tecnativa/docker-socket-proxy
      - /var/run/docker.sock:/var/run/docker.sock:ro
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.reverse-proxy.rule=Host(`traefik.test`)"
      - "traefik.http.routers.reverse-proxy.entrypoints=http"

networks:
  bridge_network:
    driver: bridge

  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: 192.168.1.0/24
          gateway: 192.168.1.1
          ip_range: 192.168.1.69/32  # Must be outside router's DHCP range

Why not? You can just connect the PiHole container to both networks and inter-container communication should work as usual. I haven’t tried this with PiHole specifically but I’ve done it with other services in the past

LFS?

In the Netherlands there’s “Jan Modaal”, modaal (modal) referring the most commonly occurring value in or peak of a distribution. This name is used often when representing the experience of the most average Dutchman.

It’s especially often used in financial discussions and journalism, like “owning a house is getting further out of reach for Jan Modaal.”

You uh… you might have chosen the wrong field if you hate displacing labour

TIL wallhaven, what a neat find. This could make a solid cron job for grabbing a new wallpaper every day

This was a lovely exchange comrades

An the issue is only inside the network? I’d complain to IT about that, yeah. Maybe they are overriding the DNS record with their own DNS server or something.

Can you set your own DNS servers on your client devices? Does cloudflare or quad9 resolve it?

Do you have a static IP? If not, have you tried some kind of dynamic DNS like DuckDNS?

Each instance supports its own api afaik, so yes. But if the user searches for an instance, then you have the host, so assuming the endpoint is public the app should be able to hit it.

yes

I’m not sure I agree. If a user types in a Lemmy instance host, the app should be able to make a call to list that instance’s communities.

I had a browse through the issues but I couldn’t find a good example - would love a link if someone finds one!

not from the app, I asked but didn’t get repose from the devs!

This is true. However many big maintained public images are multi-arch so down for ARM, and the fact that Docker runs in a VM on Windows and OSX when you install it doesn’t matter to most people. On Linux indeed it reuses the host’s kernel (which is why containers can be a lot lighter than VMs)

It’s not NAS specific, it’s platform independent - that’s the whole point. You have an application you want to run, and you package it all up into a docker image which contains not only the application but it’s dependencies and their dependencies all the way down to the OS. That way you don’t need to worry about installing things (because the container already has the application installed), all you have to do is allocate some resources to the container and it’s guaranteed* to work

*nothing is ever as simple as it first appears

One area where this is really helpful is in horizontally scaling workloads like web servers. If you get a bunch more traffic, you just spin up a bunch more containers from your server image on whatever hardware you have laying around, and route some of the traffic to the new servers. All the servers are guaranteed to be the same so it doesn’t matter which one serves the request. This is the thing kubernetes is very good at.

Edit: see caveats below

It’s absolutely orientalist, similar to Zelazny’s Lord of Light but for Islam instead of Hinduism. For these, I was able to view them as a product of their time and enjoy the story even while recognizing some problematic elements.

I found the 2nd book to be a bit of a slog, and I enjoyed the 3rd a lot more again. Since it was about new characters once again coming of age (… kind of), it has that same sense of exploration and discovery as the 1st. The 1st is definitely my fave so far though.