• 0 Posts
  • 24 Comments
Joined 2 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
    




  • quaff@lemmy.catoLinux@lemmy.mlRectangle for Linux?
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    1
    ·
    3 months ago

    It’s funny. I have been forced to use macOS because of work, and I use rectangle to mimic what KDE plasma does out of the box. I’d suggest using KDE if you wanted something powerfully customizable and user friendly. If you find something that works with other windows decorations (non-KDE), I’d love to know about them too for when I inevitably switch back to Linux Desktop!








  • Most people I chat with on Signal uses desktop too, I’ve never heard complaints. Most of my contacts use it now. There were hiccups in the earlier months but now it’s smooth and works great.

    I use Telegram every now and then. It’s has some nice features. But it’s not secure. The reason the messages “sync” fast there… is because it’s all plain text and on the server. For everyone to read. This is an undisputable fact about Telegram. The nature of the large channels you mentioned requires this insecure mode of storing chat histories, so that everyone can access. Where as with Signal, everything is E2EE. Except a tiny bit of metadata. Telegram everything is unencrypted until you use secret chats. Again. Different threat models. You can’t really compare it to Signal. It’s more akin to FB messenger. Which is not secure. Or private.

    Messages being deleted for everyone is a pretty common feature across all the platforms now. I’m not sure what you’re getting at. Arguably, chat history being stored plain text is much more a privacy nightmare (it’s literally the reason people want E2EE) than anything else.



  • I never understood these arguments for Telegram. Sure, it does have more features. It’s not better in terms of usability and cross platform support though. I use Signal desktop everyday. It’s a great experience. Cross platform… The only platform Signal doesn’t support is Web. Which… if there are mobile apps and desktop apps. Web is an insecure redundant need IMO. For the argument that web is good for scenarios where you can’t install desktop apps: I would flip the question to… why would you give a platform you have 0 control, permission to access your secure & private messaging? It just comes down to threat modelling. Telegram is neither secure, nor private. It shouldn’t even be in the same conversation unless talking about FB Messenger, messaging on Instagram or DMing on Twitter/X.