![](https://lemmy.ca/pictrs/image/4283c4a1-9603-4a66-9419-3884f0412f8b.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
The key for me was being told: it’s okay to ride (to hold) the clutch a little before/during/after you’re switching gears.
The key for me was being told: it’s okay to ride (to hold) the clutch a little before/during/after you’re switching gears.
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
Asahi Linux is shaping up nicely. I’ll probably install that soon. 👀
True that. Small victories 🥲
Make one, if for nothing else as a portfolio piece!
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!
Does anyone happen to have an invite they could throw my way? 👀
Hm. I am having trouble with setting up sonarr to reorganizing my existing download. This is a lot of work to get Jellyfin to work smoothly 🥲🫡
Kind of. It’s all one big Downloads folder, but I have shows in a subfolder. I am in the process of setting up Sonar 🫡
I’ve pushed up my setup if you’d like to check it out! I use it with ProtonVPN, but can be adapted to be used with others.
Removed link: see other comments for a working docker-compose
That’s odd. The project has been archived. No more active development. This seems like such a cool project too. I wonder what happened 🙏
Removed by mod
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.
That’s not my experience. I use it on macOS. My messages are always synced. Super fast and runs smooth.
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.
FB Messenger and Instagram Messenger would be the worst for privacy… But Telegram is basically just FB Messenger with nicer UX features.
There’s a couple of platforms that have better privacy and security (debatable) features than Signal, but Signal is more widely adopted amongst the E2EE Messengers.
Ahhh this makes a lot of sense! Thank you 🙏
I’ve been seeing this in the All section… what is it?
Imagine an insurance company using data about you that it purchased from FB or Twitter to give you different insurance rates.
Or your social posts or posts tagged of you affecting your credit score or job application or even your rent application.
There are so many scenarios where having your privacy respected would protect you from unnecessary and unfair judgement.
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.