• cadekat@pawb.social
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Won’t that lead to some horrible hug-of-death type scenarios if a post from a small instance gets popular on a huge one?

    • CoderKat@lemm.ee
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      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
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

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

    • kate@lemmy.uhhoh.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

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

      • parlaptie@feddit.de
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        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.

      • 30p87@feddit.de
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        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.