So now that Lemmy and the community overall are getting a lot of attention, with /c/memes being one of the biggest communities across instances, I think we should be a bit more strict about certain things.

I’d like your opinion, though. What do you think about a rule about only allowing images, and that such images need to be uploaded to Lemmy instead of linking to something like Imgur. I think that text and videos are a better fit for some other community (at least until we get something where we are able to play videos within Lemmy).

  • Krafting@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    images need to be uploaded to Lemmy instead of linking to something like Imgur

    Not a good idea, sites like Imgur allows lemmy to not store the data, which takes up a huge amount of space, accross all instances. It’s better to have image on the instance, yes, but after a bit of work, the lemmy’s devs can show external images inline, just like on reddit.

    • bdonvrA
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Not exactly true, unlike Mastodon I believe only the original instance stores the photo. Even when browsing a remote instance, you’re loading from their server.

      • Krafting@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Oh, might be right, yeah.

        But still, devs should implement showing videos/images from other services to show up here inline, instead of having to click the link!

      • autumn@reddthat.com
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I think it’s cached on federating servers - that’s why copies of beehaw communities still exist on lemmy.world and sh.itjust.works despite defederating

        • bdonvrA
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          The posts are cached, like the text and comments. The images aren’t AFAIK. The links to the images are also cached, and BeeHaw can’t tell what instance is accessing them, it just sees a request from each user’s computer for the image.