The open source DOCX editor submitted to HN a few weeks ago has been deleted
98
ggcanyon 1 day ago 43 comments
FR version is available. Content is displayed in original English for accuracy.
The github repo under eigenpal is gone. The web site at docx-editor is 503. No idea what's going on.

Discussion (43 Comments)Read Original on HackerNews
the top comment on the show hn would seem quite apt if so https://news.ycombinator.com/item?id=46971202
I would guess that they have lost access to a resource lately ... I've read there's a lot of that going around atm.
[1] https://news.ycombinator.com/threads?id=thisisjedr
[A] https://news.ycombinator.com/item?id=46947229
[B] https://news.ycombinator.com/item?id=48228411
[1] https://docx-editor.dev/
[2] https://github.com/eigenpal/docx-js-editor
[3] https://github.com/eigenpal/docx-editor
Edit for additional show hn thread
I found docx to be a very well documented format and a surprisingly good fit for this.
https://tinycld.org has a live demo
I expect I could find whether you're using hardened server implementations or reimplementing, but if it's the former, you should advertise that, or if the latter, you shouldn't.
I do not know what you expect by "hardened server implementations", it's open-source and people will probably host it a lot of different ways? If you're talking about the various services it offers like imap/webdav, I'm using well established golang libraries which I hope are secure but I have not performed a security audit or anything like that.
"If you're talking about the various services it offers like imap/webdav, I'm using well established golang libraries"
That's exactly what I'd hope to see said somewhere as a naive person. Maybe security people would say "that's only 50% of the attack surface!!!" but I'm not one so it sounds good to me.
I thought of it because this project said they used AI
( https://news.ycombinator.com/item?id=48085993 )
Edit (since I can’t seem to reply directly) - to the commenter suggesting LibreOffice below: quite different things. This was a library for implementing reasonably high fidelity docx viewing / editing in the browser.
So AI was in use. Then the author says that following the spec alone wasn't enough to get it working, they got "active community feedback" and fed that feedback into the AI until it worked just like Word. I have to think that if there were ANY conditions under which a model might output code that Microsoft legal would threaten to sue you for, these would be them
If anything it’s DOCX itself that was the vector!
Understanding DOCX Malware and Hidden Threats
https://cloudmersive.com/article/Understanding-DOCX-Malware-...
Hackers using Weaponized Office Document to Exploit Windows Search RCE
https://cybersecuritynews.com/office-document-to-exploit-win...