How about you assume less? I spent 40+ minutes looking for this here, here, here and here and I’m already fairly familiar having done work on two other ActivityPub based projects.
In addition public-addressing (or the lack of use thereof) in no way claims to achieve what you’ve stated - which is probably why it’s not the answer to my query.
Ahh, didn’t even know there was a flag for that. I don’t suppose you could link to the relevant w3c or FEP for it?
All votes are public, they’re literally broadcast to the Fediverse writ large. You vote on something on your server, your server then tells the server owning the thing you voted on and that server then tells anyone who is interested (subscribers on other servers). That way everyone knows that this comment was voted on, but that information is indelibly tied to you - an entity on the Fediverse.
Lemmy devs just chose not to a) show that information in a UI (plenty of other software out there does) and b) not inform people that was the case. Which leads to the whole point of the thread, hiding this from users merely gives a false sense of security.
You say that, but you simply have to be using something that isn’t Lemmy and that information is there (doubly so if you’re an admin on any of these systems)
Except, if you’re using anything other than Lemmy at this point that information is already about. The Likes/Dislikes are considered public information by the protocol. Lemmy devs probably just didn’t get around to building out the UI for that before the Reddit APIcolypse.
All your followers would see it and sometimes you don’t want replies?
On my Pixel I long press at the bottom and then press on the code. I think it’s called google lens or something.
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.
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.
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 :(
I’ve not used dockge so it may be great but at least for this case portainer puts all the stack (docker-compose) files on disk. It’s very easy to grab them if the app is unavailable.
I use a single Portainer service to manage 5 servers, 3 local and 2 VPS. I didn’t have to relearn anything beyond my management tool of choice (compose, swarm, k8s etc)
“…prohibits repair stores from repairing components on the mainboard. Instead, the entire component must be replaced…”
A flagrant disregard for the costs of e-waste on the environment. What a surprise.
I’ve not tried it but have been keep tabs.
The two main problems appear to still be ongoing PRs/issues; magazine/community sidebar content doesn’t update and doesn’t federate out at all to lemmy, and moderation actions don’t federate at all (any of the various types) - which is particularly problematic.
If only k/mbin federated better - I’d be all over it :(
Privately operated ICBM’s. I can’t see how that’ll fly but I look forward to finding out.
Main page of dashboard
If you long press on a tile (this is kitchen)
Immich does support folders?
https://immich.app/docs/administration/storage-template/
With this you can store your photos in whatever structure you want.
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.
Hugo can be as simple as installing it, configuring a site with some yaml that points at a really available theme and writing your markdown content.
It gets admittedly more complex if you’re wanting to write your own theme though.
But I think this realistically applies to most all static site generators.