Yes, this is standard in the forgery business - dust and speckle filter, drop the res, ensure the light is balanced, and maybe blur if you can get away with it.
These general techniques are weak against specific detection models that understand how the original image should’ve been generated. Another example is camera noise modeling since the injected noise won’t be consistent with how a phone camera etc actually behaves, or an ML model for image depth might see that it's at the wrong distance somehow.
Scaling the image down seems like one of the best tricks if you can get away with it. Another cheap one would be shifting the image 4 pixels over to break up the DCT artifact grid.
Busses don't have to have a mindset issue. They don't where I live. You'll just take the bus if it's faster than the tram or goes closer to where you want to be, that's the only consideration involved.
It's not "hopeless to manage", learn some networking and be forever rewarded. Same with learning to manage devices, servers, etc. I develop now but I'd be much less valiable without that background.
Just firewall off all management interfaces and allow via IP as needed. It's still possible your webserver will get become vulnerable, but you'll prob here about it here if it is.
Isn't it so relieving now that the pendulum is swinging back?
I'm so glad I moved into C# and non-web dev/management and got out of that rat race. Tech always swings back and forth, but I'm so very happy to have made it past SPAs being the end all be all.