• 2 Posts
  • 175 Comments
Joined 4 years ago
cake
Cake day: July 28th, 2020

help-circle


  • I think your best bet is to assume that everything you don’t control is a vector.

    The modems run binary blobs you don’t control.

    A standard modem with a singular hookup to a router is as good as it gets. Maybe you are contemplating the modem as a combo – if it is also a router and wifi, you can bet the ISP sees that as “Their Network” and not “Your Network” and any WiFi capabilities could be used to reverse hack insecure devices theoretically like smart TV or IoT.

    You could put the modem router combo in a Faraday cage to dampen the signal theoretically.

    That may not be answers to the query but I think the smart short answer is: yes, unless verified no.

    Edit: to go further, theoretically they can capture any traffic and if they get the encryption key decrypt the traffic.

    Or maybe with a quantum computer decrypt with ease. And if you have any leaks or there are backdoors then who knows what the consequences could be, cough cough xz


  • Block the ISP DNS and use your own on the router level.

    You could look into wireguard or VPN on the router level.

    Probably OpenSense.

    As long ad your device has a IMEI though not like it matters.

    There’s probably a million other things you would need too. Make sure your browser doesn’t use its own DNS, eg, Firefox + CloudFlare by default.

    I assume you could theoretically split traffic up over multiple ISP’s making it a PITA to try to make sense of.

    Also obviously separate trusted & untrusted devices, WiFi and wired into separate networks.


  • Is it me or is source forge just the mark of dead things.

    I always avoid that place. It feels like where you go to get broken stuff.

    They’re gonna take me out back and shoot me for saying it but Launchpad too. Like I’m glad it works for you but it feels like when Debian had a website in 2015 that looked like 1997. How are we going to attract new talent when the rift between the average developers and the old guard widens over time. All the git VCS modernization supercharged development. Like bugzilla was “fine”, but " fine" was the problem in a world of better when you couldn’t even upload a > 250kb jpeg and other legacy hold us back stuff.






  • I was incorrect about the aspect ratio it’s 3:2 not 16:9 and I think 3:2 is fine especially at 2160x1440p.

    Still with the dialogs on the left and right anything except minimal would make the drawing area small taking the left and right.

    I did notice it on sale, maybe if you have humble expectations it would be okay for sketching, but if you are used to better quality things or larger draw surfaces you might not be easily impressed.




  • Assume I’m an amature and bad at this ;P

    In any case you might try a docker-compose.yml

    version: "3.8"
    # Compose file build variables set in .env
    services:
      supervisor:
        platform: linux/amd64
        build:
          context: ./build
          args:
            PYTHON_VERSION: ${PYTHON_VERSION:-3.10}
            PYTORCH_VERSION: ${PYTORCH_VERSION:-2.2.2}
            WEBUI_TAG: ${WEBUI_TAG:-}
            IMAGE_BASE: ${IMAGE_BASE:-ghcr.io/ai-dock/python:${PYTHON_VERSION:-3.10}-cuda-11.8.0-base-22.04}
          tags:
            - "ghcr.io/ai-dock/stable-diffusion-webui:${IMAGE_TAG:-cuda-11.8.0-base-22.04}"
            
        image: ghcr.io/ai-dock/stable-diffusion-webui:${IMAGE_TAG:-cuda-11.8.0-base-22.04}
        
        devices:
          - "/dev/dri:/dev/dri"
          # For AMD GPU
          #- "/dev/kfd:/dev/kfd"
        
        volumes:
          # Workspace
          - ./workspace:${WORKSPACE:-/workspace/}:rshared
          # You can share /workspace/storage with other non-WEBUI containers. See README
          #- /path/to/common_storage:${WORKSPACE:-/workspace/}storage/:rshared
          # Will echo to root-owned authorized_keys file;
          # Avoids changing local file owner
          - ./config/authorized_keys:/root/.ssh/authorized_keys_mount
          - ./config/provisioning/default.sh:/opt/ai-dock/bin/provisioning.sh
        
        ports:
            # SSH available on host machine port 2222 to avoid conflict. Change to suit
            - ${SSH_PORT_HOST:-2222}:${SSH_PORT_LOCAL:-22}
            # Caddy port for service portal
            - ${SERVICEPORTAL_PORT_HOST:-1111}:${SERVICEPORTAL_PORT_HOST:-1111}
            # WEBUI web interface
            - ${WEBUI_PORT_HOST:-7860}:${WEBUI_PORT_HOST:-7860}
            # Jupyter server
            - ${JUPYTER_PORT_HOST:-8888}:${JUPYTER_PORT_HOST:-8888}
            # Syncthing
            - ${SYNCTHING_UI_PORT_HOST:-8384}:${SYNCTHING_UI_PORT_HOST:-8384}
            - ${SYNCTHING_TRANSPORT_PORT_HOST:-22999}:${SYNCTHING_TRANSPORT_PORT_HOST:-22999}
       
        environment:
            # Don't enclose values in quotes
            - DIRECT_ADDRESS=${DIRECT_ADDRESS:-127.0.0.1}
            - DIRECT_ADDRESS_GET_WAN=${DIRECT_ADDRESS_GET_WAN:-false}
            - WORKSPACE=${WORKSPACE:-/workspace}
            - WORKSPACE_SYNC=${WORKSPACE_SYNC:-false}
            - CF_TUNNEL_TOKEN=${CF_TUNNEL_TOKEN:-}
            - CF_QUICK_TUNNELS=${CF_QUICK_TUNNELS:-true}
            - WEB_ENABLE_AUTH=${WEB_ENABLE_AUTH:-true}
            - WEB_USER=${WEB_USER:-user}
            - WEB_PASSWORD=${WEB_PASSWORD:-password}
            - SSH_PORT_HOST=${SSH_PORT_HOST:-2222}
            - SSH_PORT_LOCAL=${SSH_PORT_LOCAL:-22}
            - SERVICEPORTAL_PORT_HOST=${SERVICEPORTAL_PORT_HOST:-1111}
            - SERVICEPORTAL_METRICS_PORT=${SERVICEPORTAL_METRICS_PORT:-21111}
            - SERVICEPORTAL_URL=${SERVICEPORTAL_URL:-}
            - WEBUI_BRANCH=${WEBUI_BRANCH:-}
            - WEBUI_FLAGS=${WEBUI_FLAGS:-}
            - WEBUI_PORT_HOST=${WEBUI_PORT_HOST:-7860}
            - WEBUI_PORT_LOCAL=${WEBUI_PORT_LOCAL:-17860}
            - WEBUI_METRICS_PORT=${WEBUI_METRICS_PORT:-27860}
            - WEBUI_URL=${WEBUI_URL:-}
            - JUPYTER_PORT_HOST=${JUPYTER_PORT_HOST:-8888}
            - JUPYTER_METRICS_PORT=${JUPYTER_METRICS_PORT:-28888}
            - JUPYTER_URL=${JUPYTER_URL:-}
            - SERVERLESS=${SERVERLESS:-false}
            - SYNCTHING_UI_PORT_HOST=${SYNCTHING_UI_PORT_HOST:-8384}
            - SYNCTHING_TRANSPORT_PORT_HOST=${SYNCTHING_TRANSPORT_PORT_HOST:-22999}
            - SYNCTHING_URL=${SYNCTHING_URL:-}
            #- PROVISIONING_SCRIPT=${PROVISIONING_SCRIPT:-}
    

    install.sh

    sudo pacman -S docker
    sudo pacman -S docker-compose
    

    update.sh

    #!/bin/bash
    # https://stackoverflow.com/questions/49316462/how-to-update-existing-images-with-docker-compose
    
    sudo docker-compose pull
    sudo docker-compose up --force-recreate --build -d
    sudo docker image prune -f
    

    start.sh

    #!/bin/bash
    sudo docker-compose down --remove-orphans && sudo docker-compose up