|
| 1 | +1. Identification of the Original Work |
| 2 | +Work: ElegantOTA Pro |
| 3 | + |
| 4 | +Official URL: https://elegantota.pro |
| 5 | + |
| 6 | +License: Softt Commercial License 1.2 |
| 7 | + |
| 8 | +Nature: Commercial proprietary software (frontend and backend) for embedded OTA updates |
| 9 | + |
| 10 | +ElegantOTA Pro includes a custom frontend with drag-and-drop UI, SVG animations, and a C++ backend using AsyncWebServer, session authentication, gzipped HTML serving, firmware rollback, and OTA progress tracking. |
| 11 | + |
| 12 | +ElegantOTA Pro is licensed under Softt Commercial License 1.2 and the license explicitly mentions that: |
| 13 | +Licensee shall not sublicense the Licensed Material to any third party. |
| 14 | +Licensee shall not use the Licensed Material to build, develop, or offer any product or service that directly or indirectly competes with the products or services offered by Licensor. |
| 15 | + |
| 16 | +2. Infringing Repository Details |
| 17 | +Repository URL: https://github.com/adrihd/PrettyOTA |
| 18 | + |
| 19 | +The repository above contains infringing content across its entire codebase, including: |
| 20 | + |
| 21 | +🔹 Frontend Infringement |
| 22 | +prettyOTA.html: Replicates [private] UI layout, class structure, visual animations, and branding style from ElegantOTA Pro. |
| 23 | + |
| 24 | +🔹 Backend Infringement |
| 25 | +PrettyOTA.cpp/.h/.Callbacks.cpp: Contains OTA handlers, gzipped page delivery, user session management, reboot logic, callback structure (onStart, onProgress, onEnd), and file upload routing that are substantially similar to [private] original work / source code of ElegantOTA Pro. |
| 26 | + |
| 27 | +This is also clearly evident from the demo GIF/video included in the README file of the PrettyOTA repository where we can see a lot of similarity between ElegantOTA Pro and PrettyOTA. (Our demo video is located at https://elegantota.pro) |
| 28 | + |
| 29 | +3. Infringing Forks |
| 30 | +This repository in itself is a fork of an infringing repository which was disabled recently under the following notice: [private]. |
| 31 | + |
| 32 | +I confirm that I have personally reviewed each fork and that my sworn statements apply to all of them. |
| 33 | + |
| 34 | +4. Remedy Requested |
| 35 | +Due to the nature and extent of the infringement, the infringing party must: |
| 36 | + |
| 37 | +Delete the entire PrettyOTA repository and all of its forks |
| 38 | + |
| 39 | +Cease redistributing, modifying, or referencing any portion of ElegantOTA Pro or derivative work |
| 40 | + |
| 41 | +Refrain from building similar OTA systems based on stolen intellectual property |
| 42 | + |
| 43 | +Removal of PrettyOTA from any public registries including but not limited to PlatformIO registry and Arduino Library Registry |
| 44 | + |
| 45 | +No attribution or code-level modification can resolve this, as the project as a whole is a derivative and infringing work. |
| 46 | + |
| 47 | +5. Sworn Statements |
| 48 | +I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration. |
| 49 | + |
| 50 | +I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed. |
| 51 | + |
| 52 | +I have read and understand GitHub’s Guide to Filing a DMCA Notice. |
| 53 | + |
| 54 | +6. My Contact Information |
| 55 | +Name: [private] |
| 56 | + |
| 57 | +Company Name: Softt |
| 58 | + |
| 59 | +Email: [private] |
| 60 | + |
| 61 | +Phone Number: [private] |
| 62 | + |
| 63 | +7. Infringer Information |
| 64 | +GitHub Username: @adrihd |
| 65 | + |
0 commit comments