It’s related to the CSAM stuff that happened a bit ago. Most of the instances purged and disabled the Pictrs database until a better solution can be determined. The general thought process is to use an external site for now
Which makes sense. Image serving and threaded text serving probably shouldn’t run in the same service. They have completely different storage and caching requirements. Also, they have rather different legal risks for server operators; and thus different moderation requirements.
For example, there are images that it’s illegal to possess in the US or Western Europe (CSAM) but there’s not a lot of text that’s illegal to possess — national security secrets / classified information, yes, but that hasn’t been a problem here.
It’s not a bug, it has been disabled on purpose temporarily.
It would have been nice to know that.
There were several pinned posts when it happened.
Not about that particular aspect. I read them.
Except they literally made a post about it.
I remember seeing a post about it. Maybe you missed it.
I guess. I looked at the pinned posts regularly to see if there was an explanation and didn’t see one.
It’s related to the CSAM stuff that happened a bit ago. Most of the instances purged and disabled the Pictrs database until a better solution can be determined. The general thought process is to use an external site for now
Which makes sense. Image serving and threaded text serving probably shouldn’t run in the same service. They have completely different storage and caching requirements. Also, they have rather different legal risks for server operators; and thus different moderation requirements.
For example, there are images that it’s illegal to possess in the US or Western Europe (CSAM) but there’s not a lot of text that’s illegal to possess — national security secrets / classified information, yes, but that hasn’t been a problem here.