Blocking users keeps their messages from appearing to you. Blocking an instance removes all user and community communications from your views. There might be more
Blocking users keeps their messages from appearing to you. Blocking an instance removes all user and community communications from your views. There might be more
Not to be pedantic, commercial systems do go through lock replacements if they are budgeting properly.
A guest wouldn’t notice unless they were watching maintenance teams replacing lock internal components.
How about when there are folks who have been harmed by people with agendas?
They’d prefer their code or commentary to be inclusive, not exclusive?
They’re not trying to force everyone to use the alternative product with this message. I think you can export the podcast subscriptions to a number of clients.
This was a fast response, and doesn’t cover the whole scope of handling networking in docker. As mentioned elsewhere there is a different network philosophy for Standalone Containers & Overlay networking.
You declare the ip in your setup, or in the yaml file. An example for the docker-compose file is in the link below. I’d expect you’ll want to declare the network and such as well, if you’re not familiar.
https://gist.github.com/natcl/3d881d00a56c8a961e6dab8ba51a5a37
It seems if you block an instance, folks from that instance can still post in other federated servers and be seen.
I don’t see an option for ‘muting’ on the midwest.social instance for individual users or other instances.
I am guessing it’s Boost or instance specific, where the application would sort back the output and selectively render replies. I don’t know.