Comment on photopea.com now locks out users blocking ads
woelkchen@lemmy.world 3 weeks agothen 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.de 3 weeks 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 3 weeks ago
If Photopea was so simple, you could just download the necessary parts and self-host.
It’s 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.de 3 weeks ago
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.
percent@infosec.pub 3 weeks ago
The image processing happens locally in the web browser.
Not to imply that hosting the static assets to power that (JS and WebAssembly binaries) is free, but it’s definitely much cheaper than the compute resources that would be required to do the heavy lifting server-side.
(Still worth paying for or allowing ads though. Photopea clearly took a lot of work to build)
woelkchen@lemmy.world 3 weeks ago
The completely insane claim was “The only infrastructure I’m using is the bit of Javascript and HTML”, meaning one could just save the page and run it fully locally.
This is of course BS.