Also not affiliated but my open-source tinycld uses docx as the backend storage for its text package. Supports _most_ of the features (including comments and suggestions) but is still very young. It has a golang backend that reads/writes docx and translates to YJS that the editor reads for multi-user access. Has web/iOS/Android support.
I found docx to be a very well documented format and a surprisingly good fit for this.
Oh man, that’s disappointing. We implemented this in a test environment and have been hammering on it. Would love to know what’s going on as it solves a real pain point for us.
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.
what was that item from just a day or so ago where an opensource project had said they developed using AI, and a developer said "take it down, you copied it from us"
I thought of it because this project said they used AI
I was going to guess that they accused the author of copying code from Office. Was AI used in the project? Perhaps a model regurgitated copyrighted code leading to a sternly worded notice from legal...?
Ooooh yeah. Looking through the author's past posts: "got a lot of skepticism because we're developing heavily with AI"
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
The original source (matching the latest published NPM version) is still at https://github.com/mhurhangee/patrick/tree/main/packages and Apache-2.0, so I imagine that someone who'd like a copy can pick it up from there.
This link should be enough to work out the relevant links. [1]
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
Also not affiliated but my open-source tinycld uses docx as the backend storage for its text package. Supports _most_ of the features (including comments and suggestions) but is still very young. It has a golang backend that reads/writes docx and translates to YJS that the editor reads for multi-user access. Has web/iOS/Android support.
I found docx to be a very well documented format and a surprisingly good fit for this.
https://tinycld.org has a live demo
Not affiliated but I been using https://github.com/superdoc-dev/superdoc and it is very good and compatible with many docx features.
Oh man, that’s disappointing. We implemented this in a test environment and have been hammering on it. Would love to know what’s going on as it solves a real pain point for us.
There's plenty of open-source docx editors though? What makes eigenpal's editor so special?
Could you recommend your picks in the space?
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.
What is wrong with LibreOffice?
Hahahahahahahahahahahahahahahaha hahahahahahahaha
How long do you have?
I can't include the links because HN filters dead links.
what was that item from just a day or so ago where an opensource project had said they developed using AI, and a developer said "take it down, you copied it from us"
I thought of it because this project said they used AI
( https://news.ycombinator.com/item?id=48085993 )
it is forseeable that MS would be very interested in taking a security stance vs a very possible vector.
A vector against a standardized XML+ZIP document format?
‘’ <—— li’l Dr Evil air quotes to put around ‘standardized’ ;-)
If anything it’s DOCX itself that was the vector!
I was going to guess that they accused the author of copying code from Office. Was AI used in the project? Perhaps a model regurgitated copyrighted code leading to a sternly worded notice from legal...?
Ooooh yeah. Looking through the author's past posts: "got a lot of skepticism because we're developing heavily with AI"
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