Photopea creator weighs in on Photosuite project(github.com) |
Photopea creator weighs in on Photosuite project(github.com) |
Thank you all for your support! Many repositories like this one exist on GitHub, I tried to report in in the past, but I was completely ignored by Github / Microsoft. I feel pretty powerless here :( I tried to call them out publicly - https://x.com/photopeacom/status/2106877355738140875
This "PhotoSuite" thing got me a bit angry, since the author presented it as an original work, when I clearly see that such a project can be made from my "pp.js" file in two hours using Claude. Also, I believe that their README.md did not mention Photopea before I wrote my first comment there.
Thousands of people shared "PhotoSuite" on social media and nobody minded the fact that they don't know who the creator is. The creator is still offering it on their website as their original work: https://www.photosuite.app/
We live in interesting times. AI can (or will be able to) de-obfuscate every bit of code that was ever published, convert binaries to readable C++ and so on. So, in theory, AI models will train on the source code that we consider "closed-source" now, and will be able to recreate this software if asked. But it wouldn't be possible if a real person did not spend thousands of hours of their life to write that software years sooner.
I have always been excided to see people make AI create something new, what didn't exist before. But so far, I mostly saw only "approximations" of expensive software, when AI tries to recreate each feature and each button according to what it thinks it should do, or "forks", when AI takes the full code of something and tries to "bend" it to hide the similarity with the original work.
Genuine question: isn't this what photopea did to photoshop?
In this case, it was a clear copy-paste of my code, whith the variable names changed by the AI.
The hard reality though is any site written in JavaScript is now part of an LLM's training set and can (and will be) be trivially rewritten into something new. Interesting times.
>“He who hath grown wise concerning old origins, lo, he will at last seek after the fountains of the future and new origins. […] For the earthquake—it choketh up many wells, it causeth much languishing: but it bringeth also to light inner powers and secrets. The earthquake discloseth new fountains.”
— Nietzsche, Thus Spake Zarathustra
> the reader emits the model's shape rather than the file's
Oh hello Claude
> the writer derives its field count from Object.keys().length while skipping the sentinel
It makes a lot of sense architecturally. It's much simpler to update a webpage than force every user to update their app when something needs to change. Consequently a lot of apps, especially on mobile, use a system webview with a page loaded from a server and rendered to look like the app for anything that gets regular updates. The alternative is having lots of versions of the page and needing to manage all the different variations of payloads from them.
Backwards compatibility in an API isn't that hard, but when there's a simpler option (a webview) people will take it.
That said, if there's no native stuff in the app, it is a bit harder to justify.
This kind of thinking is what brought us the trend of painful Electron apps like Teams.
I'll do a code audit (and you should too, before casting stones). The code is there.
https://github.com/photopea/photopea/issues/9042
This is childish behavior.
> There are people on both sides of the fence, and I want out.
Victim card. How classy. You are using every trick in the book, one by one
So that did not work out, but I used it a bit and interacted with him couple of times there, before moving on to easel and later pixi, after it became clear it would not take off and the other ones had more support.
Glad for him to found success with Photopea later, and he definitely has my sympathy here.
But I doubt this will work out much longer in the long run. It is just too easy cloning and improving projects with AI.
That's a dangerous word. Did you mean adding more features?
Photopea is not, and has never been open source, AFAIK.
A rip off would be using the actual Photoshop source code.
I suspect we're dealing with a child here with a cloud code subscription who isn't quite familiar with US copyright law or software licenses yet.
Archived at: https://web.archive.org/web/20261006025310/https://github.co...
He's the definition of the word "bootlicker".
"But he admitted to killing him, he's innocent!"
> @kuckir, to be clear about the lineage: PhotoSuite started from the Photopea build mirrored at https://github.com/ruanjiyang/Photopea-Offline, and the README credits Photopea as the primary inspiration and prior art. Over the past year it's been rewritten and rearchitected module by module, retargeted for desktop, restructured into ~330 source files, with a lot of features Photopea doesn't have. It's a rewrite of that lineage.
That Photopea-Offline is an unofficial rip of the actual app. Pretty sure using a pirated version doesn't suddenly grant you license rights to use & extend the code into another competing product...
> That's a bold accusation. Would you care proving which bits of the code are "stolen"?
https://github.com/eolix/photosuite/issues/77#issuecomment-5...
to banning photopea, to when photopea responds with a 2nd account re: some duplicate code which is very hard to explain w/o being, well, duplicated to what you pasted above.
edit: it's not, the reddit post https://www.reddit.com/r/Bard/comments/1wxmqpt/ive_created_o...
and github repositories
https://github.com/storytold/photocraft (Photoshop)
https://github.com/storytold/vectorcraft (Illustrator)
https://github.com/storytold/filmcraft (Premiere)
https://github.com/storytold/lightcraft (Lightroom)
https://github.com/storytold/printcraft (Acrobat Pro)
https://github.com/storytold/effectcraft (After Effects)
https://github.com/storytold/designcraft (InDesign)
It's embarrassing to be honest. The eolix guy couldn't even respond to the very first piece of evidence by the Photopea creator, before spewing some clearly and poorly generated, LLM response. So of course he'd resort to issue-closing, title-changing, banning, bullying and then Whatabout-ism.
Beautiful rainbow of moral failures...
Goodluck with that "internal audit" buddy. The internet never forgets.
A side note: I wonder what pre-Microsoft Github would do in such cases. I don't think I've ever seen modern Github take action against any clone repo with legitimate copyright issues.
I don't like it but thats the situation on the ground IMO
the future of software is oss. unless governments lock down access to these tools to prevent this kind of reverse engineering. which is a horrible future to envision.
[1] https://github.com/vladtrc/iw4L
[2] https://www.youtube.com/watch?v=9UbADrcEW5w
[3] https://github.com/chasmlol/2010-rust-rewrite-mashup
[4] https://www.reddit.com/r/bevy/comments/1wuu7bx/are_you_seein...
[5] https://www.reddit.com/r/bevy/comments/1wuag9d/skate_3_was_r...
> 4.4. Paper.js (ext1790438722.js)
> Upstream Project: Paper.js (by Jürg Lehni & Jonathan Puckey)
> License: MIT License
> Specific Violations: MIT Condition: The MIT License mandates: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." The entire ~200 KB Paper.js library is embedded in minified form with all author names, copyright notices, and license text stripped.
I question the seriousness of the author of "Photosuite". Who goes through the trouble of creating accounts to prove poorly, that they "didn't steal code".
Or rather created it and eolix is your other alias?
I don't mean to discredit LLM capabilities, it's just that these examples are heavily favored by what's already documented online.
- the software would run only on your own server and clients will access it remotely through an interface
- you will sell the software together with the hardware and a proprietary operating system, which does not allow anyone to get the ones and zeros of your software
So, the only way to prevent GTA6 being "decompiled" and "forked" by AI models is to run it remotely (with a video interface), or sell it together with a proprietary console :D
btw this is the actual solution, not that whole stop killing games movement. not regulation.
The vast majority of license violations are just MIT or ASL projects whose license text got stripped in the minified deliverable. Just adding source maps for those libraries is enough to become compliant.
I have no clue with regards to LGPL on the web but since it is delivered via WASM, there is a linking boundary so it might just be an issue regarding letting users bring their own implementation.
The only credit he gave was saying the original project was inspiration.
Then he deleted and banned the original author posting proof that it was a rip of and not just inspiration.
So I welcome him leaving and reconsidering.