I reverse proxy everything through a Caddy instance running on the same machine so I avoid the firewall dance entirely by just prefixing all my port assignments in the compose file with the loopback IP (eg. 127.0.0.1:3000:3000). Nftables denies all but 80 and 443 and I don't have to worry about restarts/flushes breaking things.
>We WANT to know that there's a collision in transmission so that we know we need to retransmit
Digital trunked public safety systems solved this problem decades ago. If you key up when the frequency is in use you get a distinct rejected tone. I'd think prevention is far preferable to sorting it out once everyone's finished walking on each other.
If pixelfed and mastodon are federated with each other, you should be able to view users and posts from both sites on either site - no need to sign up for both.
It's all your posts and replies as a user. While they currently host the only* PDS themselves, the end goal is for every end user to have their own PDS. Inrupt/SOLID calls this concept a "pod".
*(actually they just onboarded a second production PDS yesterday.. progress!)
A long time *ago I read re: Feynman's divorce that false accusations of abuse were common back then because no-fault divorce didn't exist. Couples that wanted a divorce would have to concoct a story in order to get a judge to sign off. I don't have strong feelings either way because it's impossible to know what really happened between them, but I found it an interesting counterpoint.