![](https://infosec.pub/pictrs/image/6974f67d-0f4b-4d85-8561-66763db949cf.jpeg)
![](https://slrpnk.net/api/v3/image_proxy?url=https%3A%2F%2Ffeddit.de%2Fpictrs%2Fimage%2Fb4871535-c973-4496-aa73-9b36d14a03ee.png)
“Tell me you don’t understand web apps without telling me you don’t understand web apps”
“Tell me you don’t understand web apps without telling me you don’t understand web apps”
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?
The SEO-angle is interesting, thank you for the insight!
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?
I live in an area with strong winds and I’m happy with Knirps, they can be found in both NA and EU.
More expensive than “regular” umbrellas, but they are built to last and are compact to boot.