lemmyvore

Well that’s the nice part about the Aeropress, the process is so customizable that you can find a good recipe for just about any coffee.

The Hoffman recipe is not meant to be perfect, just a safe starting point. It can’t possibly fit every single coffee batch out there.

OP hasn’t purchased any book. They’re on a plan that lets them listen to any book for free, except it’s time-limited.

When you “cast” from the phone to the Chromecast, what happens it that the phone gives the Chromecast an URL where it can find the stream to play. The phone can read that stream because it’s connected to the Tailscale VPN. The Chromecast isn’t, so the stream URL is inaccessible to it. You see the Jellyfin logo because that’s a feature of casting (the app on the phone gives the Chromecast a logo to show).

There’s no point in announcing the subnet from your laptop, because your laptop is not a router for the local LAN. You can use this to reach local LAN devices from remote Tailscale nodes but not the other way around.

Some possible solutions:

1. You enable the hotspot feature on the phone while connected to Tailscale, and connect the Chromecast to the wifi of the phone. But the stream will consume the cellular connection, because you’re using the phone’s wifi for the hotspot (the phone only has one wifi interface so it cannot use it both to connect to the local LAN and for hotspot).
2. If you connect the local laptop to the router with a wired connection you can use its wifi as hotspot, connect the laptop to Tailscale, connect the Chromecast to the laptop hotspot, and the stream will arrive over the local connection.
3. You can try to install Tailscale on the router, if it runs OpenWRT or something similar, and if it has enough storage space (the Tailscale packages are kinda large). If you announce the subnet from the router then it will work as intended and all the devices on the local LAN will be able to “see” the remote laptop.
4. If you’re using nginx as reverse proxy with TLS certificates for the remote Jellyfin you can try this: expose it to the internet without Tailscale and use nginx-ip-whitelister to temporarily allow access from your local LAN’s public IP. All devices in the local LAN will see the remote Jellyfin. But read the warnings on the project page, it’s not as secure as a VPN. And of course “expose jellyfin to the internet” is not as simple as it sounds (you need a domain, you need to get Let’s Encrypt certs, a public IP, a port forward etc.)

You can use the guide to install just Jellyfin and Qbittorrent.

You’ll have to do what the *arr are doing manually — search torrents yourself and track down each episode etc., then add them to Qbittorrent, then transfer the files to where Jellyfin expects them when they’re done downloading, look for subtitles etc.

It’s not as nice as the *arr setup because it can’t “take requests”, basically you have to be the one to get the stuff that your friends and family ask for and manage it with Jellyfin… on the other hand it’s much faster to get going — and you can always add *arr stuff later, one by one.