From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [ANN] Editable HTML export of Org-mode files Date: Tue, 14 Aug 2012 23:45:28 +0200 Message-ID: <87vcglywp3.fsf@gnu.org> References: <87pq6ua0kk.fsf@gmx.com> <87393p7qvy.fsf@pank.lan> <87lihhrdvy.fsf@gnu.org> <87a9xx7gtq.fsf@gmx.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57783) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1OvA-0007Zj-JT for emacs-orgmode@gnu.org; Tue, 14 Aug 2012 17:45:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T1Ov9-0004lo-Df for emacs-orgmode@gnu.org; Tue, 14 Aug 2012 17:45:04 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:56151) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1Ov9-0004jd-4L for emacs-orgmode@gnu.org; Tue, 14 Aug 2012 17:45:03 -0400 Received: by wgbez12 with SMTP id ez12so657109wgb.30 for ; Tue, 14 Aug 2012 14:45:02 -0700 (PDT) In-Reply-To: <87a9xx7gtq.fsf@gmx.com> (Eric Schulte's message of "Tue, 14 Aug 2012 06:56:16 -0600") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: emacs-orgmode@gnu.org, Rasmus Hi Eric, Eric Schulte writes: > With respect to security, elnode has a simple authentication system > which seems to work well in my local trials. It has no forms for > setting passwords online, so users would have to generate a hash of > their password locally, and then send the hash to someone who would > manually add it to the elnode authentication database on orgmode.org. > > During authentication the hashed password is sent in plain text, so we > would need to run the elnode server behind an https proxy server. I > don't think this would be difficult to implement and is a good idea for > any system with authentication. Thanks for those details. > With respect to integration with the existing Worg, this system should > work well in concert with the git backend. Git could still be used for > offline edits as it is currently. The org-ehtml server could be > configured to commit all web edits to git. A conflict checker would be > needed, which could be added to the `org-ehtml-before-save-hook'. I think a page should be locked when a user is editing it through org-ehtml.el. This would prevent conflicts from concurrent editing from the web. As for conflicts between the .org to be written (from org-ehtml) and the .org that might have been pushed trough git, what would be the behavior? Discard this edit? Use org-merge-driver to help resolve the conflict? Let the user download the .org he has been editing, so that his changes are not lost? This is still quite unclear to me. In any case, we should first try this on a prototype for a while and see if this is robust enough. -- Bastien