I would expect to see this kind of article in 2019 prior to the launch of WoW Classic, not now in October 2023. Classic has had the same mindset that's pervasive in retail from the very beginning. Everyone rushed straight to 60 and promptly began raidlogging to preserve their precious world buffs. Parsing and speed running in raids was all anyone cared about.
This is absurd... they made a trailer for their corporate merger: https://www.youtube.com/watch?v=AYU4q594LJ0
Your home instance will only start receiving posts from remote communities from the time that the first user subscribes to it onwards. So assuming you are the first person from the SDF.org Lemmy instance to sub to that community, the SDF.org instance will not backfill posts or comments from prior to the time that you subbed. If you know the URL of a specific post or comment, you can force the SDF.org instance to fetch it by plugging the post or comment's direct URL into the search bar.
See the Lemmy federation docs
Agreed. I've been using Fedora Silverblue for about a year. I love the immutable OS paradigm but IBM/Red Hat's recent actions have left me feeling uneasy and I want to find an alternative.
I'm also currently migrating all of my self-hosted services from docker to podman. Look into using Quadlet and systemd rather than podman-compose: https://www.redhat.com/sysadmin/quadlet-podman
Your Quadlet
.container
files will end up looking very similar to your docker compose files. Podman will automatically generate a systemd service unit for you if you drop the.container
file in your user systemd unit directory ($HOME/.config/containers/systemd/) and runsystemctl --user daemon-reload
. Then starting the container on boot is as simple assystemctl --user enable --now containername.service
.This will not solve your rootful vs. rootless issues, as others have pointed out, but Quadlet/systemd is nice replacement for the service/container management layer instead of docker-compose/podman-compose