From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Question collaborative editing - Wikipedia reference Date: Mon, 5 Oct 2020 08:34:37 +0300 Message-ID: <20201005053437.GT15516@protected.rcdrun.com> References: <83eemji6e8.fsf@gnu.org> <20201001141144.GO4797@protected.rcdrun.com> <20201001160136.chwmpollk4d3qc2e@Ergus> <20201004175447.GG15516@protected.rcdrun.com> <87362tvnil.fsf@gmail.com> <20201004194815.GH15516@protected.rcdrun.com> <11EB917D-3276-4D34-8DCD-2336E8062950@mit.edu> <20201005040245.GJ15516@protected.rcdrun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4070"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.14.0 (2020-05-02) Cc: Ergus , Fermin , Caio Henrique , Noam Postavsky , Emacs developers , Karl Fogel , Stefan Monnier , Eli Zaretskii To: Qiantan Hong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 05 07:35:18 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kPJ9a-0000ww-Bb for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Oct 2020 07:35:18 +0200 Original-Received: from localhost ([::1]:44158 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kPJ9Z-0007gi-Cu for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Oct 2020 01:35:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60028) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPJ95-0007Ht-Ey for emacs-devel@gnu.org; Mon, 05 Oct 2020 01:34:47 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:38583) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPJ91-0003Yj-V6; Mon, 05 Oct 2020 01:34:47 -0400 Original-Received: from localhost ([::ffff:197.157.34.178]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000005A13D.000000005F7AB070.000056F2; Sun, 04 Oct 2020 22:34:39 -0700 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/04 23:53:38 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:257072 Archived-At: * Qiantan Hong [2020-10-05 07:11]: > > - let each user customize their username in collaborative > > client-server connection, just as Gobby editor is doing it. Without > > such feature none of the users will know who is the other user. > Thanks for your suggestion! > I’m thinking of grabbing some code from https://github.com/zk-phi/togetherly/ > It uses different color to distinguish users. I can probably then add some > way to toggle displaying full user name with some hotkey to toggle. > Also need to add a list of connected users and color. I do not think that user names should be disturbing much, but it should be displayed, maybe in the minibuffer, that user "Qiantan" is editing currently the text. Other idea is that at least temporarily, the text edited by certain user could have specific color of the user. Colors should be assign by the server. Color would disappear as soon as user stops editing. > > - make sure that it can also start through Tor > Haven't test it. The current stuff sends S-exps over TCP, anybody > knows any potential problem interacting with VPN/Tor? Maybe that is too much at once. > > - enable server to have password, so that not every user without > > password can connect, just as Gobby editor is doing it. > Does it have one single temporary password of a server or > instead a user-password model? If it’s the former then is it reasonable > to just send plain password (over TLS connection)? Then that will > be quick to implement. I think that there should be single password to enter single editing session, when editing session starts, password should be requested or customized as default.