Yeah, things requiring choosing a instance like, say, email, are doomed to fail
You can actually run it in async model without pictrs safety and just have it scan your newly uploaded images directly from storage. It just doesn’t prevent upload this way, just deletes them.
You don’t get public traffic redirected. It’s not how it works
It stops doing checks. Iirc you can configure it yes
https://github.com/db0/fedi-safety and the companion app https://github.com/db0/pictrs-safety which can be installed as part of your lemmy deployment in the docker-compose (or with a var in your ansible)
Not all web traffic, just the images to check. With any decent bandwidth, it shouldn’t be an issue for most. It also setup in such a way as to not cause a downtime if the checker goes down.
The software is setup in such a way that you can run it on your pc if you have a local gpu. It only needs like 2 gb vram
Upgraded. All went pretty smooth. Good job peeps!
Very nice
I suspect some misconfiguration on their pictrs.
!mechabellum@lemmy.dbzer0.com if you’re a tactics freak. It like fucking crack to me.
Still 404 on my end
They did run a revolt server for a while, but they apparently had to revert back to discord for reasons.
I’m getting a 404
Ye I really don’t understand how the same post in mastodon is possible to appear in two different groups, but not in lemmy. I am not familiar enough with the internals.
I’m guessing lemmy is not capable of crossposting the same thing to two different communities in general, the same way it’s not possible via lemmy itself.
I’m not sure how it chooses which community to post to when there’s multiple. I would assume it would pick the first one? If it’s not, that, maybe it’s random?
That’s not how copyrights work.
This is what this post is suggesting, yes
I don’t see how it’s a privacy risk since you’re not exposing your IP or anything. Likewise the images are already uploaded to your servers, so there’s no extra privacy risk for the uploader.