IdeaWell

Project ideas from Hacker News discussions.

Photopea creator weighs in on Photosuite project

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Copyright infringement and license violations
Many commenters accuse Photosuite of copying Photopea’s code, using an unofficial offline build, and stripping attribution/license notices.
- “the author literally admits he copied the code” – hex4def6
- “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…” – hex4def6
- “Even if the offline version was an authorized thing, there was no license attached to the project, meaning full copyright.” – gbin

2. Suspected AI/LLM involvement in code or responses
Several users believe the author’s explanations (or the code itself) were generated by a language model.
- “the comment where he's 'explaining' the code is clearly LLM written.” – superdisk
- “It definitely sounds like Claude.” – kayson
- “I wonder if the issue is being responded to by an agent. A lot of the responses sound like stuff Claude writes.” – cautiouscat

3. Broader implications for software ownership in the AI era
Discussants note that AI makes cloning trivial, challenging traditional copyright and suggesting a shift toward open‑source norms.
- “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.” – agar
- “the future of software is oss. unless governments lock down access to these tools to prevent this kind of reverse engineering.” – slopinthebag
- “It is just too easy cloning and improving projects with AI.” – lukan

🚀 Project Ideas

License Compliance Scanner for Minified Assets

Summary

  • Scans JavaScript, WASM, and CSS bundles for missing license headers and attribution text, flagging potential OSS license violations introduced by AI‑assisted rewrites.
  • Core value proposition: automated detection and remediation suggestions help developers stay compliant before publishing or distributing code.

Details

Key Value
Target Audience Open‑source maintainers, frontend developers, dev‑ops teams using AI to generate or modify code
Core Feature Dependency‑aware scanner that matches minified content against known library fingerprints and verifies required license notices are present
Tech Stack Node.js, Rust‑based parsing library (e.g., swc), GitHub Action integration, optional WebAssembly UI
Difficulty Medium
Monetization Revenue-ready: SaaS subscription ($15/mo per private repo, free for public OSS)

Notes

  • HN commenters noted MIT license stripping: “The entire ~200 KB Paper.js library is embedded in minified form with all author names, copyright notices, and license text stripped.” – ProjectBarks
  • Provides concrete utility for the frequent complaint that AI‑generated rewrites lose attribution, reducing legal risk and community backlash.

AI‑Generated Code Detector API

Summary

  • Uses stylometric and ML‑based analysis to estimate the likelihood that a code snippet was produced by a large language model, helping enforce attribution and detect potential infringement.
  • Core value proposition: gives maintainers an objective signal to question code origins and request proper licensing or clean‑room justification.

Details

Key Value
Target Audience Maintainers of popular libraries, legal teams, platform moderators (e.g., GitHub, npm)
Core Feature REST API that returns a probability score and highlights suspicious patterns (e.g., odd variable naming, repetitive structures) for submitted code snippets
Tech Stack Python, HuggingFace Transformers (CodeBERT/GPT‑NeoX), FastAPI, Docker deployment
Difficulty High
Monetization Revenue-ready: pay‑per‑call ($0.001 per 1000 chars) with free tier for open‑source projects

Notes

  • Many comments highlighted LLM‑generated justifications: “the comment where he's 'explaining' the code is clearly LLM written.” – superdisk
  • Enables the community to act on suspicions like “I suspect we're dealing with a child here with a cloud code subscription…” – geor9e, providing a technical basis for discussions about AI‑authored code.

Cleanroom Development Sandbox Service

Summary

  • Provides an isolated, auditable development environment where engineers can implement features based solely on functional specifications, guaranteeing no exposure to existing source code.
  • Core value proposition: reduces copyright infringement risk for companies creating alternatives (e.g., Photoshop‑like editors) by enforcing a provable clean‑room process.

Details

Key Value
Target Audience Product teams, startups, and enterprises building competing tools who need legal certainty
Core Feature Browser‑based VS Code instance running in a secure VM, with spec documents mounted, network blocked to external repos, and full operation logging for audit
Tech Stack Docker/Kubernetes, AWS Firecracker microVMs, VS Code Server, TypeScript backend, audit log storage (e.g., Elasticsearch)
Difficulty High
Monetization Revenue-ready: Enterprise licensing ($500/mo per seat) with trial tier for small teams

Notes

  • IvanK_net (Photopea creator) expressed frustration: “I tried to report in in the past, but I was completely ignored by Github / Microsoft.” – highlighting need for better enforcement mechanisms.
  • Supports the viewpoint that “the only way to prevent GTA6 being 'decompiled' and 'forked' by AI models is to run it remotely…” – offering a practical, legal‑safe alternative to cloud‑only distribution.

Read Later