Fairly easy to tell at the moment, LLMs are not very coherent or interesting in long form writing as yet.
But if you want to believe otherwise that's up to you (or perhaps you just hope it could be otherwise?). If you prefer, you can read that sentence as 'How refreshing to read intelligent, coherent thoughts in a blog post instead of the garbage we so often see nowadays.'
The sentiment is the same, it's about quality and intelligent thought, not style or provenance. Maybe one day we'll have to say intelligence rather than human, which is a fun thought. I don't feel we're close to that yet though.
"Use of AI: The author prompted Claude and ChatGPT interactively to simplify the proofs, focusing only on disproving basic statement of ETH, without optimizing log factors. The author expanded the proofs manually and made them more human-readable and added explanations and a worked example."
For the past two years, I have been exporting my images in WebP instead of JPG. If I share it online or send it by an email, I am pretty sure the other side will be able to see them.
I honestly think that all phones and even professional cameras should replace JPG with WEBP, we will have like 30% smaller photos.
The DNG format (for raw photos) allows JPEG XL compression (it used to allow only JPEG in the past). I wish some country made it mandatory for cameras to let user take photos in DNG (just like USB-C is mandatory in the EU).
I am happy that HEIC from Apple did not take off (as it was proprietary, protected by patents).
Good to know, I had let the team know. It’s handled by the appropriate folks so I won’t see further updates, but this should be in good hands now.
Personal(!) opinion: do get a standard template drafted for these cases by a legal professional. You don’t have to retain anyone or sue anyone, but having a consistent, and compliant filing always expedites decisions - this isn’t GitHub specific. Some platforms like YouTube try to abstract this process and end up with the opposite problem of lots of specious claims. Hence the transparency of publishing all notices we receive. Again no idea whether the filing is the issue in this specific case, nor saying you did anything wrong here, just general advice for fewer headaches.
JXL is too new to draw any conclusions. But indeed, the market has spoken and it doesn't want avif. I tried adding avif support to a service myself, but the very slow encode speed made it unsuitable without paying for a larger server (or worse, a thumbnailner-as-a-service). Only a handful of enthusiasts (who chime in every such thread!) like avif.
Personally I fully expect jxl to succeed where avif failed and webp floundered.
Thanks! One is Ticket 4822535, another is Ticket 4726557.
Github did take down this https://github.com/spooknik/Photopea-Appimage and other repos in the past, but now, I feel like I talk to a robot. I am happy to hear that they have real employee! :D
Hey guys, thank you all very much for your comments! I just woke up, I did not really believe my post would get this much attention, so thanks!
Honestly, I was a hoping that giving attention to this problem here at HN might lead to someone from Github actually noticing my problem and looking into it.
I think I will try solving it with a lawyer. But it would be really cool if I could spend my days writing code instead of dealing with lawyers and stuff.
I could find are a bunch of Photopea repositories on GitHub, but the authors are all either from China or Russia, so getting damages for infringement will be difficult to enforce. Hiring a lawyer sounds like a waste of money to me.
In my experience GH usually does 512(c) takedowns in days; so it taking a month is quite abnormal. OP’s posted response suggests he didn’t file a copyright takedown but rather an anti-circumvention claim; which is a bit special in DMCA law, and generally best avoided when you have merits to do a regular 512(c).
We also don’t have details of the repo. The author has commented on another project that claims to be a LLM _re-implementation_ of Photopea, without directly using source. If that’s the case, it’s entirely understandable why GitHub won’t take it down.
Sadly though, you have to do the cost/benefit analysis of the legal process and your likelihood of recovering anything.
I spent $18k in legal fees over a $22k claim in a construction dispute. I won the suit and was awarded legal fees. So I'm owed $40k plus interest. I've collected exactly $0. The last lawyer I spoke to said I need to cut my losses in legal fees at some point because from a practical standpoint, winning damages isn't the same as collecting them. Especially if the defendant isn't local and has few assets.
> But it would be really cool if I could spend my days writing code instead of dealing with lawyers and stuff.
I think anybody in any line of work or life would like that. It's however unlikely to never run into an issue where a lawyer is really needed, so don't hesitate when you realize you need one.
>Honestly, I was a hoping that giving attention to this problem here at HN might lead to someone from Github actually noticing my problem and looking into it.
> users who we all know are, in fact, entitled to get everything for free
That kind of thing is explicitly required under HN rules - if a company requires payment, it's only OK to post if a “workaround” to avoid paying is available.
Additionally, HN explicitly say it's OK:
* For HN comments to ask how to get around payment requirements, and
* For HN users to help other users to get around payment requirements
Thank you for saying this. It's literally insane to me how thoroughly entrenched this sense of entitlement has become. It's at the point where it can't even be parodied, because a chunk of society, maybe even the majority, seriously holds the view that they are entitled to any software thing they want for free.
On reflection, it's a great convenience to leave your cart around. So I think cart pushing is a valuable service to provide, and leaving your cart should be fine if it's stable and not in the way of anything.
If he wants revenue he can restrict his product to paying users. Double dipping with the popularty of free access only to abuse users with spychological manipulation spam should never be accepted.
Depending on your definition, shareware models have been around for 40 years at this point. If you disagree with the terms, don't use it. That's a personal decision though, not a global moral position.
By the way, PhotoSuite is just a stolen copy of my project www.photopea.com , which I have been working on for 8 hours a day for the past ... 14 years? :D
It was discussed here on HN yesterday and then, the anonymous person behind it removed the "Issues" section completely from their Github
Never got to try out PhotoSuite, looks like it really was just ripping-off your code, the repo owner already deleted it, and now it forks PhotoCraft.
I have a huge respect for your work on Photopea, been using it constantly since the time I completely moved to Linux a year ago. It has the best Photoshop parity yet to find! Would you ever consider to:
1. Open sourcing your work (partially or completely) under some kind of a permissive/copyleft license.
2. Rewriting some parts of the website that require performance as WASM targets.
3. Using any modern JS frameworks, e.g. Svelte.
2) WASM is not faster than Javascript "by default". Both can be fast or slow depending on how you write it. I don't think having everything in WASM would make Photopea significantly faster. Also, Photopea uses many libraries as WASM (WEBP decoding, ZSTD decoding, JPG decoding, Harfbuzz, ... JXL / AVIF encoding)
3) I never used any Framework, but if it is just a bunch of a JS code, I think I managed to write an equally good JS code for the UI over the past 14 years.
yeah it would. an SPA is exactly what you'd want for a "webapp" like this, where you want everything loaded upfront so that you're mostly interacting with stuff offline. it's also very cache friendly so, really no benefit to using SSR.
SSR only really makes sense when you either want to optimize for fast page loads, or do PHP-style conditional rendering or whatever
I get that, but isn't that model dead now? Doesn't this whole drama prove it? Is there any way to protect an SPA from ~"Hey Claude, de-obfuscate this, then clean-room design our app in another session" in 2026 - and then apply better marketing - without even knowing anything about code? Doesn't this apply to all client-side & native code? Gaming companies are very aware of this.. claude + ghidra + bevy is going to kill all IP protection for games. Their attempt to stop this is why there is no more physical media.
As another browser example along the lines of Photopea, ScreenRun is amazing as a true one-time pay, client-side app. I have loved that thing ever since I paid the $50. Such a cool app and model that has no server costs. Whoever made that is also my hero. But aren't those days now over? I guarantee there are >100 ripoffs of it now. Isn't an SPA now just basically open source, in the worst way only?
Meanwhile, Photopea.com only works via a website for normies. It is ad-supported, so given all the work put in, and updates, and the fact that it is web served... wouldn't SSR be a better option? (I hate this reality)
edit: I am allergic to Next, so I have been using Sveltekit since I realized that SPAs are now accidental open source. What have others been using for SSR and why? That is the discussion I would really like to have.
OK, I have thought about this more and I realized that I have never worked on compute intensive apps like Photopea, so I am truly ignorant here. I also did only SPAs forever, and I am now only learning about SSR and hydration. I guess if there was a truly server-side rendered Photopea, using React something like React Server Components, it would probably not be supportable by free + ads. It might actually cost at least as much a month as the inspiration of the app.
I guess my point was, how can anyone protect any client-side IP in the modern era?
I remember using your tool a lot for years but in the past year or so the ads have made it unusable. It feels more like browsing ign.com with no adblock or something. Just brutally slow and intrusive visually speaking.
And at 8 Euro a month I can't quite justify the Photopea premium plan.
I use it enough I would happily pay say $50 for a self-hosted single user license that will not get updates. But not 8 euro a month forever.
I am finally forcing myself to un-learn the decades of Adobe muscle memory and replace it with gimp/krita. Or maybe I'll vibe up something that does exactly what want and nothing more; bespoke one-off tooling is just so easy to do now.
There have been only two photo editors that fully support the PSD format: Photopea and Adobe Photoshop. When a new one appears, which fully supports the PSD format, from an anonymous creator, it is very likely a copy one of these two. And they usually name it Photopea-offline, etc.
Why is so hard for people to post a link? If y'all are going to be making claims, post the links to back it up. Then show how the code is the same. If the original is online and the copy is offline, that would seem to indicate a material difference (without digging into both their code)
This smells a lot like the Laya thing to me, especially with the astroturfing by friends and fans
First of all, thanks Ivan! Happy user of Photopea.
Second, the trademark will help you against the masqueraders, those copying your tool and the Photopea brandmark. That will help with customers complaining about some other modified product. It will not help in case you find someone copying your codebase and putting it out in the open under a different name. For that, you'll need a copyright.
Doing both of these might be expensive but gives you complete legal standing. Companies will have no choice but to take down the copies.
reply