- Published on
The open source DOCX editor submitted to HN a few weeks ago has been deleted
- Authors
- Name
- DeepHorus
An open source DOCX editor that recently gained traction on Hacker News has been entirely removed from the internet, leaving the developer community speculating about the reasons behind its disappearance. The project, which offered browser-based viewing and editing of Microsoft Word documents with high fidelity, was submitted as a Show HN post by user thisisjedr just weeks ago. Both the GitHub repositories—eigenpal/docx-editor and eigenpal/docx-js-editor—and the project’s website docx-editor.dev are now inaccessible, returning 404 errors. This swift deletion has sparked conversations about the legal and technical risks of replicating proprietary document formats, especially when artificial intelligence is involved.
The editor’s core appeal was its ability to render and manipulate DOCX files directly in the browser without external dependencies, aiming to match Microsoft Word’s behavior. The developer disclosed in the original HN thread that the implementation relied heavily on AI, specifically large language models, to interpret the DOCX specification and generate working code. According to comments, following the official Open XML specification alone was insufficient; the developer fed community feedback into the AI until the output “worked just like Word.” This approach raised eyebrows, as it effectively reverse-engineered the format through iterative AI-generated patches.
Key factual details include the deletion of all project resources after the Show HN post garnered significant attention. The top comment under the submission now appears prescient: it warned that the project might face issues, possibly referencing the developer’s history of multiple submissions and potential self-promotion concerns. Other users noted that the developer’s account, thisisjedr, had submitted several other projects, including userplane.io, but the DOCX editor was the only one to be completely taken down. The repository names—eigenpal/docx-editor and eigenpal/docx-js-editor—exist only in archived references.
The implications of this event extend beyond one abandoned project. The use of AI to replicate a proprietary format like DOCX introduces legal grey areas. Microsoft holds patents and copyrights related to the DOCX specification, and code that closely mimics Word’s behavior could be considered derivative work. Some HN commenters argued that if there was any scenario where AI-generated code could invite a lawsuit from Microsoft, this was it. Additionally, security experts highlighted that DOCX files are a common vector for malware, and automated generation of such files could inadvertently reproduce vulnerabilities or be exploited by malicious actors.
Community reactions have been divided. Many sympathized with the developer’s effort, praising the technical achievement of browser-based DOCX editing. Others criticized the reliance on AI for “black box” reverse-engineering, arguing that a cleaner, spec-only approach would be more sustainable. Several commenters pointed to the risks of using HN primarily for self-promotion, citing the site’s guidelines that discourage excessive promotion of one’s own work. The developer’s decision to delete everything—rather than pivot or license the code—suggests external pressure or a loss of confidence.
Looking ahead, the case serves as a cautionary tale for developers building tools that mimic proprietary software, especially when AI is used to fill gaps in understanding. As large language models become more adept at generating functional code, the legal landscape will need to catch up. Meanwhile, the open source community is left wondering what other projects might face similar fates. For now, the DOCX editor serves as a reminder that while AI can accelerate development, it cannot replace careful legal and ethical consideration when replicating existing standards.
