quaff

Ah good point, gotta delete the old unencrypted chat too to avoid confusion. That’s definitely more than just 3 clicks.

If you’re talking to 30 people, it’s 90 clicks. It might be 3 clicks if you know where to look, but end of the day, even if you know where to find it, that’s still that many clicks times how many people you chat with. It’s not ideal. I wouldn’t say it’s complicated sure, but it’s not easy.

Yeah, the fact that FB messenger uses Signal protocol, means the encryption is better recognized than the one used in Telegram. But the lack of on-by-default or the need to drill in a few options before enabling secret chats.. I mean it’s even named the same thing as Telegram.

It’s three clicks. And it opens a separate chat from the existing one. It’s obscure enough that you could say the UX deprioritizes (which at best is not an actively malicious design choice) usage of end-to-end encryption.

If Telegram is considered an encrypted messenger, then FB messenger should be too. Works exactly the same. I don’t know about you, but being the same level as FB messenger should speak volumes to whether Telegram is “encrypted” or not 🙄

You should try out https://pcpartpicker.com/

Great tool to spec out a computer and give you an idea of how much it’ll cost you.

Neat. But it’s kind of concerning to see yet another OSS project hitch it’s community resourcing to Discord.

I’ve switched from Quad9 to Mullvad DNS a month ago, and I’ve been noticing some domains aren’t resolving. Domains that shouldn’t be blocked. It feels like Mullvad’s rules are extra restrictive.

Are there any updates regarding microphone and Touch ID support in this release?

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.

Asahi Linux is shaping up nicely. I’ll probably install that soon. 👀