Yes, but arguably it was never very scalable for federated software to store large media. It gets utterly massive quick. Third party image/video hosts that specialize in hosting those things can do a better job. And honestly, that's the kinda data that is just better suited for centralization. Many people can afford to spin up a server that mostly just stores text and deals with basic interactions. Large images or streaming video gets expensive fast, especially if the site were to ever get even remotely close to reddit levels.

[–] cadekat@pawb.social 8 points 1 year ago

If you're only responsible for caching for your own users, you don't unduly burden smaller instances.

[–] NightAuthor@beehaw.org 11 points 1 year ago (1 children)

We need more decentralization, a federated image/gif host with CSAM protections

[–] 30p87@feddit.de 2 points 1 year ago (1 children)

How would one realize CSAM protection? You'd need actual ML to check for it, and I do not think there are trained models available. And now find someone that wants to train such a model, somehow. Also, running an ML model would be quite expensive in energy and hardware.

[–] NightAuthor@beehaw.org 2 points 1 year ago

There are models for detecting adult material, idk how well they’d work on CSAM though. Additionally, there exists a hash identification system for known images, idk if it’s available to the public, but I know apple has it.

Idk, but we gotta figure out something

[–] kate@lemmy.uhhoh.com 3 points 1 year ago (1 children)

Maybe a system where the files federate after 3 upvotes from outside the original instance?

[–] parlaptie@feddit.de 8 points 1 year ago (1 children)

That'd still be exploitable. You could just run 3 of your own instances. Coming up with a system to stop malicious users that can't be gamed would be tricky.

[–] cadekat@pawb.social 2 points 1 year ago

Caching only if some number of your own users upvote might work.