Tell HN: GitHub refuses to remove cracked copies of my software after a month

📝 Discussion Summary (Click to expand)

Three prevalent themes in the discussion

Whether copying code equals “stealing”
sneak: “Copying isn’t stealing. We settled this in the 90s.”
otterley: “The word ‘stealing’ isn’t limited to physical objects.”
ianberdin: “I personally know Ivan… he devoted half his life to it… when someone has literally stolen his work, nobody is reacting. And that's terrible.”
The need for legal action and frustration with GitHub’s response
JohnFen: “You should discuss this with an attorney that is experienced with IP law… IP law is very complex… you need expert legal advice.”
Ianberdin: “GitHub should respond to this.”
IvanK_net: “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.”
Challenges of monetizing client‑side JavaScript and the inevitability of copying in the AI/open‑source era
mingus88: “If your business model depends on your code being a secret, JavaScript is not a good play… The business model needs to enhance what the code offers since it’s basically a commodity now.”
lrvick: “Software is no longer a moat and DMCA means nothing anymore.”
wafflemaker: “Headspace without being tracked… Using headspace lost its charm… I wonder if Andy ever agreed to this.” (reflecting the tension between monetization and user expectations).

🚀 Project Ideas

Generating project ideas…

Monitors GitHub and other code hosts for unauthorized copies of your client‑side JavaScript/HTML/CSS assets.
Generates evidence‑rich DMCA takedown notices and can submit them automatically via platform APIs.
Connects you with IP lawyers for escalation when needed.
Core value: Saves indie creators hours of manual policing and increases takedown success rates.

Key	Value
Target Audience	Indie developers and SaaS founders whose core IP lives in client‑side code (e.g., Photopea‑type editors, games, widgets).
Core Feature	Automated similarity scanning (MinHash/LSH) + DMCA notice generation + submission tracker + lawyer marketplace.
Tech Stack	Python (scanning service), GitHub/GitLab/Bitbucket APIs, AWS Lambda + SQS, PostgreSQL, React dashboard, Stripe for billing.
Difficulty	Medium
Monetization	Revenue-ready: SaaS subscription (tiered by # of projects & monthly scan volume).

Commenters lament that GitHub’s DMCA process feels automated and unresponsive; a service that prepares proper, evidence‑backed notices would be welcomed (see “jameshilliard” and “ChrisArchitect” notes about needing correct filings).
Provides a concrete way to act on the frustration expressed by IvanK_net (“I think I will try solving it with a lawyer”) while letting him spend more time coding.
Potential to evolve into a broader IP protection platform (e.g., monitoring for AI‑generated reproductions).

Offers a hosted, ad‑free, premium version of open‑source client‑side apps (like Photopea) with value‑added features such as cloud storage, real‑time collaboration, and priority support.
Keeps the source code openly available so the community can still contribute, but monetizes via the service layer.
Core value: Removes the incentive to fork and redistribute stripped‑down copies by delivering a superior, hassle‑free user experience.

Key	Value
Target Audience	End‑users of open‑source creative tools who want reliability, privacy, and extra features; creators seeking a steady revenue stream without locking code.
Core Feature	Managed hosting of the open‑source app, user accounts, premium plugins/modules, usage analytics, and optional white‑labeling for teams.
Tech Stack	Node.js/React frontend, Dockerized backend, Kubernetes orchestration, Redis for sessions, S3‑compatible storage, PostgreSQL, Stripe.
Difficulty	Medium‑High
Monetization	Revenue-ready: Freemium model – free basic hosted instance, $5‑$15/mo per user for premium features (storage, collaboration, support).

Several users (e.g., “pbasista”, “peskymaterial”) note that ads and tracking drive people to strip them out and redistribute clean copies; an ad‑free hosted service removes that pain point.
Commenters express willingness to pay for a polished, trustworthy experience (see “busymom0” praising Photopea and “janalsncm” suggesting monetization via support/hosting).
Provides a path for creators like Ivan to monetize via service rather than fighting endless forks.

A web‑based assistant that helps creators draft, validate, and file DMCA takedown notices correctly on platforms like GitHub.
Tracks notice status, sends reminders, and offers a marketplace to consult IP lawyers for follow‑up actions.
Core value: Lowers the barrier to effective legal action, reducing reliance on informal community advice.

Key	Value
Target Audience	Indie developers, small studios, and open‑source maintainers facing copyright infringement on code‑hosting sites.
Core Feature	Notice template wizard (auto‑fills repo URLs, infringement excerpts), validation against platform requirements, submission API integration, status dashboard, lawyer chat/booking.
Tech Stack	React/Vue frontend, Node.js/Express backend, Firebase Auth, GitHub API, Twilio/Email notifications, Stripe for pay‑per‑notice or subscription.
Difficulty	Low‑Medium
Monetization	Revenue-ready: Pay‑per‑notice ($2‑$5) or monthly subscription for unlimited filings; optional lawyer fees passed through.

Many commenters advise “talk to a lawyer” (e.g., “JohnFen”, “bartread”) but note cost and complexity as barriers; LegalEase streamlines the first steps.
The discussion highlights GitHub’s vague refusals (e.g., “we're unable to confirm a violation of 17 U.S. Code § 1201”); a tool that ensures notices are filed under the correct section (copyright, not anti‑circumvention) would address this gap.
Could become a go‑to resource for HN users frustrated by ineffective DMCA processes, encouraging more disciplined IP enforcement.