I wonder why would one make a headline "Open source collaborative text editors", and then write about online editors which are neither fully open-sourced, nor fully collaborative. And then stop with them, without even mentioning solutions that are both truly real-time collaborative and truly open source.
Open source collaborative text editors
131–140 of 167 posts
Re: Open source collaborative text editors
#132https://gobby.github.io/ ? Not web-based though.
That brings back memories. Used gobby all the way back in school.
Re: Open source collaborative text editors
#133I wonder why would one make a headline "Open source collaborative text editors", and then write about online editors which are neither fully open-sourced, nor fully collaborative. And then stop with them, without even mentioning solutions that are both truly real-time collaborative and truly open source.
Such as?
Re: Open source collaborative text editors
#134I wonder why would one make a headline "Open source collaborative text editors", and then write about online editors which are neither fully open-sourced, nor fully collaborative. And then stop with them, without even mentioning solutions that are both truly real-time collaborative and truly open source.
Such as?
Well some of the links that others have posted here before me are such examples - starting with Etherpad.
I realize that the OP is about something that works with structured text, but the headline (as is) is just click-bait.
Re: Open source collaborative text editors
#135Is there a way to use one of them without hosting it yourself?
Also check out https://codeshare.io
Re: Open source collaborative text editors
#136Earlier quoted context omitted.
> One way to solve this is to fallback to differential sync when syncing huge offline edits This is another question -- does automatic syncing make sense for huge differences in users' contents? The answer might be no. OTOH, isn't this a rare scenario? How perfect it has to be?How much of a compromise can the users accept? These are interesting questions which shows that creating this kind of software isn't easy -- b…
First of all when discussing about offline edits we should make effort to draw attention that "offline" could mean different thing to different people. Offline editor from the point of view of the app's software developer might mean that editor can sometimes survive few minutes of lost connectivity, after which it will reconnect and possibly sync the team work. Offline from the perspective of a team of scientists wri…
Then there is the science fiction version where the editors are both online, but several light years apart with the resulting lag in updates.
Re: Open source collaborative text editors
#137I would be very appreciative if Google made a stripped down version of Google Docs for plaintext editing. There are a bunch of basic integration features that would also be fantastic, but if the product was literally just Google Docs, minus the WYSIWYG bits, and all plaintext w/ maybe some syntax highlighting thrown in, I'd be super happy.
You mean like this? https://hackmd.io/
Re: Open source collaborative text editors
#138A number of years back, I wrote an OT implementation in Clojure/ClojureScript as a hobby project [1] and learned a lot along the way. I even extracting out the core client/server implementations to their own package [2]. It's an incredibly fun topic, and one that's also really challenging. It also gave me first-hand experience with fuzz-testing where I could simulate all kinds of concurrent-edit conflicts and ensure…
I'll recommend this link too. Saw it on HN a long time ago. It's quite long but very well explained.
http://archagon.net/blog/2018/03/24/data-laced-with-history/
Re: Open source collaborative text editors
#139What about Cryptpad? https://cryptpad.fr/
Its full copyleft AGPL which could be an issue for someone trying to use it in a commercial application. But for other uses, it looks absolutely incredible. https://github.com/xwiki-labs/cryptpad
From the Cryptpad README, gotta love the humor:
The server does have a certain power, it can send you evil javascript which does the wrong thing (leaks the key or the data back to the server or to someone else). This is however an active attack which makes it detectable. The NSA really hates doing these because they might get caught and laughed at and humiliated in front of the whole world (again). If you're making the NSA mad enough for them to use an active attack against you, Great Success Highfive, now take the battery out of your computer before it spawns Agent Smith.
Re: Open source collaborative text editors
#140I wonder why would one make a headline "Open source collaborative text editors", and then write about online editors which are neither fully open-sourced, nor fully collaborative. And then stop with them, without even mentioning solutions that are both truly real-time collaborative and truly open source.
What do you mean by "not fully collaborative"? Both presented solutions seems like quite collaborative.