• 5 Posts
  • 43 Comments
Joined 12 days ago
cake
Cake day: June 18th, 2025

help-circle

  • If the only thing holding you back from NixOS is my python comment, my issue was with Numpy, which really really demands that you install it globally. Pretty sure you can make it work by using a dev-shell, installing it globally in that shell, then doing everything else in that dev environment normally. I was newish to nixos at the time.

    Otherwise I tend to fall back to ubuntu server, but only because it was something I knew. I prefered Centos7 back in the day before RedHat killed Centos. NixOS was my move from there. Been using Alpine as the os in my docker images, but havent really explored a lot of other recent linux os’s at the moment.






  • Ok, got another one for ya based on some comments below. You have all the usual addons to block ads and such, but you create a sock-puppet identify, and use AI to “click” ads in the background (stolen from a comment) that align with that identity. You dont see the ads, but the traffic pattern supports the identity you are wearing.

    So rather than random, its aligned with a fake identity.




  • This is like chaff, and I think it would work. But you would have to deal with the fact that whatever patterns it was showing you were doing “you would be doing”.

    I think there are other ways that AI can be used for privacy.

    For example, did you know that you can be identified by how you type/speak online? what if you filtered everything you said through an LLM first, normalizing it. Takes away a fingerprinting option. Could use a pretty small local LLM model that could run on a modest local desktop…


  • Ton of comments, and I havent read them all, but I wanted to ask if you really meant popular or if you wanted something for a specific reason. Easy for new ppl to linux, good for desktops, etc etc.

    I dont really use GUIs on linux, except for when I want to have a fancy pants riced network monitor type situation. I am a big fan of NixOS except for python Dev stuff. Big fan of being able to clone a machine or recover a machine with a single conf file.












  • sure thing, here you are

    services:
      pihole:
        container_name: pihole
        image: pihole/pihole:latest
        ports:
          # DNS Ports
          - "53:53/tcp"
          - "53:53/udp"
          # Default HTTP Port
          - "8082:80/tcp"
          # Default HTTPs Port. FTL will generate a self-signed certificate
          - "8443:443/tcp"
          # Uncomment the below if using Pi-hole as your DHCP Server
          #- "67:67/udp"
          # Uncomment the line below if you are using Pi-hole as your NTP server
          #- "123:123/udp"
        environment:
          # Set the appropriate timezone for your location from
          # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g:
          TZ: 'America/New_York'
          # Set a password to access the web interface. Not setting one will result in a random password being assigned
          FTLCONF_webserver_api_password: 'false cat call cup'
          # If using Docker's default `bridge` network setting the dns listening mode should be set to 'all'
          FTLCONF_dns_listeningMode: 'all'
          FTLCONF_dns_upstreams: '127.0.0.1#5335' # Unbound
        # Volumes store your data between container upgrades
        volumes:
          # For persisting Pi-hole's databases and common configuration file
          - './etc-pihole:/etc/pihole'
          # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'
          #- './etc-dnsmasq.d:/etc/dnsmasq.d'
        cap_add:
          # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
          # Required if you are using Pi-hole as your DHCP server, else not needed
          - NET_ADMIN
          # Required if you are using Pi-hole as your NTP client to be able to set the host's system time
          - SYS_TIME
          # Optional, if Pi-hole should get some more processing time
          - SYS_NICE
        restart: unless-stopped
      unbound:
        container_name: unbound
        image: mvance/unbound:latest # Change to use 'mvance/unbound-rpi:latest' on raspberry pi
        # use pihole network stack
        network_mode: service:pihole
        volumes:
          # main config
          - ./unbound-config/unbound.conf:/opt/unbound/etc/unbound/unbound.conf:ro
          # custom config (unbound.conf.d/your-config.conf). unbound.conf includes these via wilcard include
          - ./unbound-config/unbound.conf.d:/opt/unbound/etc/unbound/unbound.conf.d:ro
          # log file
          - /srv/docker/pihole-unbound/unbound/etc-unbound/unbound.log:/opt/unbound/etc/unbound/unbound.log
        restart: unless-stopped
    

    I am relatively new to docker as well tbh. I did a lot with virtualization and a lot with linux and never bothered, but I totally get the use case now ha. just an FYI, if you use docker on Windows it runs slower as it has to leverage the Windows subsystem Linux (WSL) and a slightly different docker engine (forget which one). So linux is your best bet. If you do want to use a full VM I found Qemu to be the best option for least resource usage.