dmca

@SrLinguicaVIVE Theres a github for DMCAs github.com/github/dmca/tree/master/2026/10 And yes they started the DMCA lawsuits.

¿Cómo que Photopea mandó a dar de baja/bloquear a un pocotón de repositorios que se copiaron de una copia que se copia a otro programa cerrado? github.com/github/dmca/blob/master/2026/10/2026-1…

Understanding DMCA for personal project I got DMCA'd on a web project that adds mobile touch support to another project that has been used to infringe on Microsoft's copyright. My project did not contain any of their intellectual property though, and I'm not seeing what they are actually claiming my project did, outside of generally infringing. Do y'all know how to get more info on these claims? I was thinking this would be the place to ask for web-related content. github.com/github/dmca/blob/3a58d0508239f439f35b5… Edit: The verdict appears to be: 1. Even though this was not made from the problematic repo, and doesn’t include any of Microsoft’s property, the fact that it could enable someone who ended up with a build without owning the Microsoft product to use it on mobile is enough for them to take it down 2. This is microsoft investigating microsoft and finding themselves blameless, so regardless of legality it was doomed from the start I appreciate y’all taking the time to give feedback!

Has Photopea suspended a clone of Photocraft? Photocraft is not a clone of Photopea, they don't even use the same development language. How is it even possible that a Photoshop clone like Photopea can takedown an unrelated project for infringing content and btw claiming the copyright on completely different and unrelated projects? I'm speaking specifically about this project : eolix/photosuite And the photopea DMCA request : github.com/github/dmca/blob/master/2026/10/2026-1… Edit : as someone pointed out, the wayback Machine indicate that the repository changed the code from Photopea (probably) to Photocraft in October, so the DMCA request was legitimate

Tracking DMCA takedowns of AI-made game ports: why a 200 OK isn't enough In early October a wave of "vibe-coded" browser ports went viral: Halo, The Simpsons: Hit & Run, GTA Vice City, Call of Duty Zombies, all running in a browser tab, many of them built with heavy help from AI coding tools. Lists of them spread on X faster than anyone could check them. I run PortedGames, a directory of these ports (browser builds, PC ports and recompilations). It re-checks every entry once a day, because the first question people ask is "does this one still work?". Within two weeks the more interesting question was "which ones got taken down, and by whom?". So I started a takedown tracker. This post covers what the data shows so far, and why the obvious way to detect a takedown (check the HTTP status) misses many of them. The numbers (as of Oct 19, 2026) 12 ports taken down after a copyright claim since Sep 11: | Rights holder | Takedowns | |---|---| | Activision | 5 | | Mojang / Microsoft | 2 | | Rockstar Games | 1 | | SEGA | 1 | | SNK | 1 | | Maddy Makes Games | 1 | | Not named by the site | 1 | A few things stand out: - Activision took down four Call of Duty browser remakes on the same day (Oct 10), all by one developer, plus an unreleased AI-assisted decompilation of Modern Warfare 2 that was reportedly hit a week earlier. - Time online varies a lot. Of the 9 ports with a known release date, the median stayed up for 29 days. The GTA V browser port lasted hours. A Celeste WebAssembly port sat on GitHub for 321 days before its game data was removed. - It isn't only browser remakes. The list includes a static recompilation (Metal Slug XX, Xbox 360), a "clean-room" Minecraft reimplementation that Mojang says contains over 2,000 original files, and a long-running campaign against Eaglercraft repositories (18 GitHub notices since August). - 8 of the 12 never produced a public GitHub DMCA notice. The ports ran on their own domains or on hosts like Railway and Cloudflare Pages, so the usual place to look (github/dmca) doesn't show them. Every row on the tracker links its evidence: the notice, the author's post, or what the site itself now says. Why status codes lie My first link checker was the obvious one: request the page, 2xx means up, 4xx/5xx means down. It reported the first port below as working even though the game was gone. 1. Notice pages return 200 and keep their title. The Modern Warfare 2 browser port "Open Victor Zulu" still serves a page titled "Open Victor Zulu". The body is now a short notice saying the game was taken down "due to a DMCA request". A status check sees 200. A title check sees the game's name. Only the body text tells you it's gone. 2. Dead addresses get recycled. Three pages.dev addresses that used to host Call of Duty remakes now all redirect to the same unrelated site. Follow the redirect and you get a 200 from a page that has nothing to do with the game. 3. Bot protection looks like "up". Some hosts answer automated requests with a Cloudflare "Just a moment..." challenge page (200) or a 403/429. The first looks up when it might be down. The second looks down when it's probably fine. 4. Takedowns don't always reach GitHub. As above: if the port isn't on GitHub, there's no public notice to find. What the checker does now The daily check is a small Node script. For each port: - 2xx in under 6 seconds: Working. 2xx but slow: Slow. 4xx/5xx or a network error after one retry: Down. - 403/429: inconclusive. Keep the previous status and don't bump the "last checked" date, rather than mark a working port as down. - Read the body, not just the status. If the visible text is short (game pages are mostly JavaScript; notices are a few lines) and reads like a takedown notice, flag it: // A 200 is not enough: taken-down ports often keep serving a short notice page. const TAKEDOWN = /\b(taken (the game |it |this )?(down|offline)|(game|site|project) (is|has been) (taken down|removed|shut down|discontinued)|offline for now|no longer (available|online|playable)|due to an? (DMCA|copyright|legal)|DMCA (request|notice|takedown|complaint)|cease and desist|received a takedown)\b/i; const SHORT_PAGE = 4000; // visible characters const m = text.length < SHORT_PAGE && text.match(TAKEDOWN); - Expect something specific. Each entry can declare a string that must appear on the page (usually the game's own name). If a recycled domain redirects somewhere else, that string is missing and the entry gets flagged. - A person confirms. The script only ever flags. "Taken down" is set by hand after reading the page and finding a source, and the script never overwrites it. A regex is good at noticing; it isn't evidence. The short-page limit matters more than it looks. Some real game pages mention "DMCA" in a footer or FAQ. Restricting the match to short pages keeps those from being flagged, because a working WebAssembly game page has very little visible text before the game loads. The data The tracker is at portedgames.com, and the same rows are available as JSON at portedgames.com (rights holder, method, release and takedown dates, days online, sources). It's free to use with a link back. If you know of a takedown I've missed, or I got something wrong, the contact address is on the page. One note on scope: the directory never hosts or links game files, ROMs or ISOs, only each project's own page, and ports their authors closed voluntarily aren't counted as takedowns. I run PortedGames, so take the framing with that in mind; the evidence for each row is linked so you can check it yourself.

Photopea DMCA Takedown on GitHub

REA 不到 10 天衝上 23 萬星：叫 AI 拆開任何軟體，它讀得到什麼、讀不到什麼 加入頻道會員，新片提早 24 小時看：youtube.com GitHub 上一個叫 REA 的逆向工程工具，2026 年 10 月初不到 10 天從約 6,869 顆星衝到 23 萬多顆（10 月 15 日上午 236,869）。爆紅期間，X 上一篇被看了 120 多萬次的長文教學開頭說你每個月付費訂閱的軟體，功能早就躺在你自己的電腦裡，標題寫成用它能免費拿到任何東西。這句話只對了一半。這支片講 REA 實際做什麼、官網示範為什麼多半挑原始碼公開或能拿原程式核對的對象、官方部落格的東方 Project 重建案例和它自己記下的錯誤，再用我自己研究一款語音輸入 App、另做一個版本的經驗，講逆向工程讀得到什麼、讀不到什麼，最後是台灣著作權法和營業秘密的界線。 章節 00:00 不到 10 天衝上 23 萬顆星 00:39 這句話只對了一半 00:52 逆向工程與 REA 01:27 官網的計算機示範 01:52 示範的前提 02:14 為什麼挑開源軟體 02:38 東方文花帖的重建 03:02 抓錯的測試也會出錯 03:28 我也走過一遍 04:00 電腦這一端與伺服器 04:20 自己做的版本 ripless 04:43 AI 犯過的錯 05:10 REA 讀不到的那一半 05:31 轉貼途中掉了但書 06:07 免責聲明 06:24 拿來保護自己 06:39 台灣著作權法 07:25 營業秘密 07:47 頻道會員 08:12 看懂之後能不能公開 08:38 收尾 說明 星數是 2026 年 10 月 15 日上午從 GitHub API 讀到的數字，之後仍在增加。官網示範的計算機是 Windows 計算機，微軟 2019 年起以 MIT 授權公開原始碼；官網其他示範約一半是開源軟體或公開的解題挑戰，另一半像 Notion 是封閉軟體，拿實際程式與它的表現交叉核對。「四步流程」是那篇 X 教學作者整理的說法，不是 REA 官方定義。《東方文花帖》697 個函式、696 個通過初步比對出自 REA 官方部落格，負責重建的人也是 REA 主要開發者之一；比對工具沒核對寫死數值、在 5 個函式找出 12 個錯誤引用，是同一篇文章記下的前一個專案（TH08《東方永夜抄》）。親身段那款語音輸入 App 刻意不點名，片中只講方法與心得，沒有破解加密、沒有碰它與伺服器之間的通訊；錯字率、時間與成本是我自己的測試，不是公開評測。片中法律內容是整理條文與判決，不是法律意見；還原工程例外的三個條件出自經濟部認定要點。RimWorld 的段落是開發商在下架通知裡的主張，GitHub 處理時註記反規避主張的資訊不足、其他著作權主張成立。 主要來源 REA 官網：rea.tools REA GitHub：morluto/rea REA 免責聲明：github.com/morluto/rea/blob/main/DISCLAIMER.md REA 官方部落格〈The industrial revolution in reverse engineering〉：rea.tools REA Notion 個案：rea.tools Windows 計算機原始碼：microsoft/calculator X 教學原文（@0xCodila）：x.com 被加上社群註記的轉貼（@firesidealpha）：x.com ArtCraft（storytold）：github.com/storytold PS1 靜態重編譯（1379.tech，2026-03-11）：1379.tech RimWorld 下架通知：github.com/github/dmca/blob/master/2026/10/2026-1… 著作權法第 80 條之 2：law.moj.gov.tw 著作權法第 96 條之 1：law.moj.gov.tw 最高法院 110 年度台上字第 3193 號判決（司法院公報）：judicial.gov.tw 經濟部〈著作權法第八十條之二第三項各款內容認定要點〉：law.moea.gov.tw 畫面來源 網頁畫面為各網站頁面截圖（2026-10-15 擷取），畫面右上逐段標示出處。ripless 畫面為預覽模式的假資料。 訂閱電子報《狐說八道》 anduril.tw #逆向工程 #AI #REA [en-US] REA Hits 230,000 Stars in Under 10 Days: Using AI to Deconstruct Any Software—What It Can and Can... A reverse engineering tool called REA on GitHub saw its star count surge from approximately 6,869 to over 230,000 in less than 10 days in early October 2026 (reaching 236,869 by the morning of October 15th). During this period of explosive popularity, a long tutorial on X, which received over 1.2 million views, began by claiming that the functions of the software you subscribe to monthly are already stored on your computer, and the title stated that it could provide access to anything for free. This statement was only half true. This video explains what REA actually does, why its official demonstrations mostly focus on publicly available source code or objects that can be verified with the original code, the Touhou Project reconstruction case on its official blog, and the errors it records. It then uses my own experience researching a voice input app and creating a different version to explain what reverse engineering can and cannot reveal, and finally, the boundaries between Taiwanese copyright law and trade secrets. Chapter 00:00 Reaching 230,000 Stars in Less Than 10 Days 00:39 This Statement is Only Half True 00:52 Reverse Engineering and REA 01:27 Official Computer Demonstration 01:52 Prerequisites for the Demonstration 02:14 Why Choose Open Source Software? 02:38 Reconstructing the Touhou Project 03:02 Mistakes in Testing Can Also Lead to Errors 03:28 I've Gone Through It Too 04:00 The Computer Side and the Server 04:20 My Own Ripless Version 04:43 Mistakes AI Has Made 05:10 The Half You Can't Read in REA 05:31 A Prohibition Was Lost During Reposting 06:07 Disclaimer 06:24 Using It to Protect Yourself 06:39 Taiwan Copyright Law 07:25 Trade Secrets 07:47 Channel Membership 08:12 Can I Share It After Understanding It? 08:38 Conclusion Note: The star count is from the GitHub API as of the morning of October 15, 2026, and has been increasing since. The computer used for the official demonstration is a Windows computer, and Microsoft has released the source code under the MIT license since 2019. About half of the other demonstrations on the official website are open-source software or public problem-solving challenges, while the other half, like Notion, are closed software. Their performance is cross-checked against actual programs. The "four-step process" is a term compiled by the author of the X tutorial, not an official REA definition. Of the 697 functions in *Touhou Bunka Shoujo*, 696 passed the initial comparison from the official REA blog; the person responsible for the reconstruction is also one of REA's main developers. The comparison tool failed to check hard-coded values ​​and found 12 incorrect references in 5 functions; this was from a previous project (TH08 *Touhou Eiyashou*) recorded in the same article. The video deliberately avoids naming the voice input app used in the demonstration, only sharing methods and experiences without addressing encryption cracking or the communication between the app and its server. The error rate, time, and cost figures are from my own testing, not a public review. The legal content is a compilation of articles and judgments, not legal advice. The three conditions for the engineering exception are based on the Ministry of Economic Affairs' criteria. The RimWorld section reflects the developer's claims in the removal notice; GitHub noted insufficient information regarding anti-circumvention claims and the validity of other copyright claims. Main Sources REA Official Website: rea.tools REA GitHub: morluto/rea REA Disclaimer: github.com/morluto/rea/blob/main/DISCLAIMER.md REA Official Blog "The Industrial Revolution in Reverse Engineering": rea.tools REA Notion Case Study: rea.tools Windows Computer Source Code: microsoft/calculator X Original tutorial (@0xCodila): x.com Repost with community annotation (@firesidealpha): x.com ArtCraft (storytold): github.com/storytold PS1 static recompiler (1379.tech, 2026-03-11): 1379.tech RimWorld removal notice: github.com/github/dmca/blob/master/2026/10/2026-1… Article 80 of the Copyright Law 2: law.moj.gov.tw Article 96-1 of the Copyright Act: law.moj.gov.tw Supreme Court Case No. 3193, 2011 Judgment No. [Number] (Judicial Yuan Gazette): judicial.gov.tw Ministry of Economic Affairs' "Key Points for Determining the Content of Each Paragraph of Article 80-2, Paragraph 3 of the Copyright Act": law.moea.gov.tw Image Source: The webpage images are screens...

Good news: GitHub has taken down the DMCA-reported doodlum repositories 🎉 Just wanted to share a positive update with the community of ENB. Doodlum who make Community Shaders based on ENB by doing unfair practices of developing mod and tries to destory original ENB author by spreading fake new about boris 5 GitHub repositories and its forks that had been reported through a DMCA complaint by boris has now been taken down by GitHub. It’s good to see that the report was reviewed and action was taken. Hopefully this also serves as a reminder that developers should respect copyright and intellectual-property rights when publishing code or projects online. Not trying to start any drama or call anyone out — just sharing the good news for those who were following the situation. Thanks to everyone who supported the effort of boris and helped bring attention to the issue. 🙏 Explaination from boris enbdev.com Another unfair practice treym.medium.com One less infringing repository online. 👍 orignal dmca link https://github.com/github/dmca/blob/master/2026/09/2026-09-03-enbseries.md https://github.com/github/dmca/blob/master/2026/09/2026-09-03-enbseries-2.md https://github.com/github/dmca/blob/master/2026/09/2026-09-03-enbseries-3.md https://github.com/github/dmca/blob/master/2026/09/2026-09-03-enbseries-4.md https://github.com/github/dmca/blob/master/2026/09/2026-09-03-enbseries-5.md

Is there a ticket code or other contact you've been in touch with? As for DMCA filings, we publish all of them here: github/dmca I see two from Photopea, one from 2022 (github.com/github/dmca/blob/d97814f268e07e62aabe8…) and one from 2024 (github.com/github/dmca/blob/d97814f268e07e62aabe8…) - could you point to the recent filing? I work at GH, but am not involved in DMCA filings, and can in no way answer or judge this case, but potentially follow up internally.