![](https://doomscroll.n8e.dev/pictrs/image/70f50cc7-420f-4881-bc24-eb1af0d92cdb.webp)
![](https://lemdro.id/pictrs/image/6d56629c-a7b1-465d-8b58-ad77926e3a41.png)
And this picture perfectly demonstrates why I’m stuck buying the (usually slightly worse) “S” versions of smart watches.
And this picture perfectly demonstrates why I’m stuck buying the (usually slightly worse) “S” versions of smart watches.
Very first line of the GitHub readme. As a support tool it’s mostly useless, endless similar or identical questions answered differently or not at all and none of it indexed by search engines for use on the web.
It’s an awful data silo / black hole that increases volunteer load.
Easily doable in docker using the network_mode: "service:VPN_CONTAINER"
configuration (assuming your VPN is running as a container)
This is a 2 and a half (almost) year old article. I figured Tim’s thoughts on this were common knowledge at this point?
It’s unfortunate that (at least on the Bluesky side) an attempt at following a person doesn’t result in them getting a DM asking for that to be ok.
Which means following a person on Bluesky is not possible unless they’ve already opted in.
All I want to do is follow a couple of authors or content creators but none of them know what bridgy.fed is :(
With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)
Documentation people don’t read
Too bad people don’t read that advice
Sure, I get it, this stuff should be accessible for all. Easy to use with sane defaults and all that. But at the end of the day anyone wanting to using this stuff is exposing potential/actual vulnerabilites to the internet (via the OS, the software stack, the configuration, … ad nauseum), and the management and ultimate responsibility for that falls on their shoulders.
If they’re not doing the absolute minimum of R’ingTFM for something as complex as Docker then what else has been missed?
People expect, that, like most other services, docker binds to ports/addresses behind the firewall
Unless you tell it otherwise that’s exactly what it does. If you don’t bind ports good luck accessing your NAT’d 172.17.0.x:3001 service from the internet. Podman has the exact same functionality.
But… You literally have ports rules in there. Rules that expose ports.
You don’t get to grumble that docker is doing something when you’re telling it to do it
Dockers manipulation of nftables is pretty well defined in their documentation. If you dig deep everything is tagged and natted through to the docker internal networks.
As to the usage of the docker socket that is widely advised against unless you really know what you’re doing.
There’s a huge amount of it on the fediverse right now. People are working very hard at getting rid, all of them volunteers, and in their own time.
It’s the multiple volumes that are throwing it.
You want to mount the drive at
/media/HDD1:/media
or something like that and configure Radarr to use/media/movies
and/media/downloads
as it’s storage locations.Hardlinks only work on the same volume, which technically they are, but the environment inside the container has no way of knowing that.