It's an appropriate option when the whole instance is toxic. If there is literally no community on it that contributes something positive to the users of your own instance, why do you need to connect to it?
So? Singapore doesn't want any drugs in the country, and put up draconian laws. Just don't break those laws.
If I tell you that I will brutally murder you if you come to my house wearing a red tie, and you do that... Your death is at least partly on you. Because you had absolutely no good reason to do that.
There is absolutely no positive outcome to selling or consuming heroin. Just don't do it. It's not a hard rule to follow...
git can get confused about if a commit was merged or not.
You have to revert the revert before re-merging the branch. Otherwise git keeps track of the commits that you reverted and doesn't apply them ever again.
There are situations where it does actually cause problems when you want to merge the branch again. It knows that those specific commits have already been reverted once, so it doesn't apply them...
Going back to the Tailscale thing - is it possible to point the domain to the IP address of the Tailscale container, so that the domain is only accessible when I switch on the Tailscale VPN? Is this a good idea/bad idea? Is there a better way to do it?
Yeah that works perfectly. The domain will point to your Tailscale IP, but that IP is not reachable unless you are in the VPN.
Name a "non-western" state where you would like to live and enjoy their social security.