• 0 Posts
  • 29 Comments
Joined 3 years ago
cake
Cake day: January 7th, 2022

help-circle




  • I removed mine since I moved away from Gitlab. There’s other comments with working docker composes, but here’s the latest working version of mine if you’re interested:

    services:
      gluetun:
        image: ghcr.io/qdm12/gluetun:latest
        container_name: gluetun
        # line above must be uncommented to allow external containers to connect. See https://github.com/qdm12/gluetun/wiki/Connect-a-container-to-gluetun#external-container-to-gluetun
        restart: always
        cap_add:
          - NET_ADMIN
        devices:
          - /dev/net/tun:/dev/net/tun
        volumes:
          - ./data:/gluetun
        environment:
          ## ProtonVPN Wireguard
          - VPN_SERVICE_PROVIDER=custom
          - VPN_TYPE=wireguard
          - VPN_ENDPOINT_IP=${WIREGUARD_ENDPOINT_IP}
          - VPN_ENDPOINT_PORT=${WIREGUARD_ENDPOINT_PORT}
          - WIREGUARD_PUBLIC_KEY=${WIREGUARD_PUBLIC_KEY}
          - WIREGUARD_PRIVATE_KEY=${WIREGUARD_PRIVATE_KEY}
          - WIREGUARD_ADDRESSES=${WIREGUARD_ADDRESSES}
          - TZ=Etc/UTC
        ports:
          - ${QBITTORRENT_EXPOSED_WEBUI_PORT}:8080/tcp # qBittorrent Web UI
    
      qbittorrent:
        # https://docs.linuxserver.io/images/docker-qbittorrent
        build: .
        container_name: qbittorrent
        restart: always
        volumes:
          - ./config:/config
          # using download path as mount so other services can play nice
          - ${QBITTORRENT_DOWNLOAD_PATH}:${QBITTORRENT_DOWNLOAD_PATH}
          - ${QBITTORRENT_THEMES_PATH}:/themes
        environment:
          # https://github.com/linuxserver/docker-qbittorrent#umask-for-running-applications
          - PUID=${QBITTORRENT_WRITE_UID}
          - PGID=${QBITTORRENT_WRITE_GID}
          - UMASK=0002
          - TZ=Etc/UTC
          - WEBUI_PORT=8080
        network_mode: "service:gluetun"
        depends_on:
          gluetun:
            condition: service_healthy
    
      portcheck:
        image: eiqnepm/portcheck:latest
        container_name: portcheck
        restart: always
        environment:
          - QBITTORRENT_PORT=6881
          - QBITTORRENT_WEBUI_PORT=8080
          - QBITTORRENT_WEBUI_SCHEME=http
          - QBITTORRENT_USERNAME=admin
          - QBITTORRENT_PASSWORD=${QBITTORRENT_ADMIN_PASSOWRD}
          - TIMEOUT=300
          - DIAL_TIMEOUT=5
        network_mode: "service:gluetun"
        depends_on:
          qbittorrent:
            condition: service_healthy
    

  • Pretty simple to switch (if you have a little docker experience). Create a folder (e.g. ./postgres), add the folder as a volume in the postgres portion of the compose file (maybe something like /db), then run just the database with newly mounted folder, shell in, and copy everything from the Postgres folder to this new folder. After that, swap mounts so the new folder is used as Postgres db and you’re good. If something went wrong, the pgdata volume is still there to switch back to.


  • Good share. I saw the nudge in the mobile app, but I didn’t realize there was breaking changes and upgraded in the middle of the night before bed (what the hell was I thinking???). Spent a good extra hour trying to figure out why.

    Key take away, the pgvecto.rs version needs to be upgraded. If you are using docker, update the docker-compose.yml. If you’re not, upgrade your pgvector.rs version first. 🙏














  • I’m getting at the fact that most platforms do stupid shit like “this message might not be deleted if the receiver already saw it” like WhatsApp does and/or replacing messages with placeholders saying “this message was deleted”. Telegram can be plain-text and can have a lot of issues but it guarantees that stuff is actually removed without trying to bullshit you like other do.

    There’s absolutely 0 guarantee that what you’ve “deleted” is deleted. On any platform really. But what you can rely on is the fact that the E2EE is there to make sure things are only readable by whoever the messages were intended for (barring being hacked and compromised keys etc). The message can say whatever it wants, doesn’t mean a lot if you can’t trust the source. Again, we’re just talking about different threat models. With Telegram, it’s not meant for secure and private communication. It has a different audience. And to push Telegram as a private or secure communication, you’re actively doing the public a disservice.

    If we assume that your privacy / security is broken (because it is) I might as well use the platform that provides the best desktop and mobile experience with fast syncs, ability to disable animations, have real desktop apps and not electron shit.

    If you can’t trust even open source technology that you can review and build yourself. And trust renowned cryptographers reviews of this technology… then why are you in a privacy community telling people their experiences aren’t true to what they’re telling you?