• woelkchen@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    9 hours ago

    then acting entitled to use the Photopea author’s own personal work with zero compensation.

    Running batch tasks on the Photopea author’s own infrastructure because Photopea is a website. Lichtmetzger wrote in a reply that he’s not using Photopea to edit a photo once in a while and now he’s bummed out (I would kinda understand that) but that he’s actually processing a big number of images on someone else’s resources.

    • lichtmetzger@discuss.tchncs.deOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      7
      ·
      8 hours ago

      The images get processed in your own browser. The only infrastructure I’m using is the bit of Javascript and HTML I am loading when accessing the site, the rest is handled by my own machine.

      • woelkchen@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        3
        ·
        edit-2
        8 hours ago

        The only infrastructure I’m using is the bit of Javascript and HTML

        If Photopea was so simple, you could just download the necessary parts and self-host.

        This won’t work because there is actual server-side code running, meaning you’re hogging someone else’s resources to do your commercial-grade tasks.

        • lichtmetzger@discuss.tchncs.deOP
          link
          fedilink
          English
          arrow-up
          8
          arrow-down
          5
          ·
          edit-2
          8 hours ago

          This won’t work because there is actual server-side code running

          That is not true! You can figure that out for yourself - open up the site, disconnect your internet and resize/crop some images. It will do it just fine, because all of that code runs in your own browser.