bulwark
disabling image uploads and image serving
I’m assuming this means death for image-based communities here on infosec (the hardware community comes to mind).
Will this impact images originating from (served by) other instances?
Unless the BIOS locks down control of fan speed (as is the case with some Dell models), you should be able to use fancontrol
to modify your fan curve.
You can install it with sudo apt install fancontrol
, then you would run sudo pwmconfig
to run fan tests and create a config file. To reduce fan noise you would typically raise the minimum trigger temperature to engage the fans.
If the tests came out alright, enable fancontrol with sudo systemctl enable fancontrol --now
.
For more information and suggestions, take a look at this ArchWiki entry.
Trying to catch up on documentation, I’ve been implementing a couple of services during the past few weeks and need to write it all down before I forget.
I do this for every service I implement as part of my backup strategy, it tends to be easier to recover from a disaster when you have reproducible steps to follow.
A reminder: if you care enough to validate the checksum of your recently downloaded ISO, don’t follow links from a stranger. Navigate to the distributors website and find the checksum yourself.
I respect and understand your decision, I’ve personally had to block a few communities from that instance due to their problematic content.
For the sake of transparency (which I feel have been the spirit of this instance so far), could you give us some examples that led up to this decision?