From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Chris Vine Newsgroups: gmane.lisp.guile.user Subject: Re: Diversification [ branched from Re: conflicts in the gnu project now affect guile] Date: Wed, 23 Oct 2019 00:24:27 +0100 Message-ID: <20191023002427.f91e23fa3475223c648487b4@gmail.com> References: <-IsD5PBFie-kW2VJSYNHx00LodtSHflKNWtY2vjNVQDN126iTMsqHrdxl8zeWE8a53TzM_27wskjsrylIh4bN5jIGVNYOBC6zmE3p1RGyBg=@protonmail.com> <87ftjk1us3.fsf@netris.org> <907270af-1f2f-42f3-ec36-047fdd48a74f@posteo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="113399"; mail-complaints-to="usenet@blaine.gmane.org" To: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Wed Oct 23 01:24:32 2019 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iN3Vw-000TQ0-2s for guile-user@m.gmane.org; Wed, 23 Oct 2019 01:24:32 +0200 Original-Received: from localhost ([::1]:48790 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iN3Vu-0003Vn-98 for guile-user@m.gmane.org; Tue, 22 Oct 2019 19:24:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34245) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iN3Vb-0003Vf-Sc for guile-user@gnu.org; Tue, 22 Oct 2019 19:24:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iN3Va-00038f-6P for guile-user@gnu.org; Tue, 22 Oct 2019 19:24:11 -0400 Original-Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]:51727) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iN3VZ-00036o-Ue for guile-user@gnu.org; Tue, 22 Oct 2019 19:24:10 -0400 Original-Received: by mail-wm1-x336.google.com with SMTP id q70so11938999wme.1 for ; Tue, 22 Oct 2019 16:24:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=LmU9yz2pZ3ttnvRn/feTeB3xiX5qQLf+vVk8o2Ewp8g=; b=cKSHvqgmK+l5o13bGxXRXYJ/+dWT3z3A4D+l/BfboRsNabl/rmg3D4+Utn0w+NciF5 Do6ztjDqxk5RFjQWJPWQ6c2kbD8vDpyDdGdgvzXJaBMBJRuIV3RmUtS66rPAF34WXRFc fSZwJyTlCMNzMp/4ulSDMx+lQcQ5+N5G9p6ZixIlrNXFjIgWb6ne0MWTWT8ftCPjRhz4 /aDMqQ/Ep0dWFdkaoHxXlvDIgBdhbNx32wstLpXpPUm74pp5tnk/kzTbXQlD2UjCr+SD zIRr4LJbaRVXv3m11mSqJmrUqUC0hvhpgkiKi+YknD4XhZfRUlmMGiYPgzVvdATig8On w+pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=LmU9yz2pZ3ttnvRn/feTeB3xiX5qQLf+vVk8o2Ewp8g=; b=IREZWXnm6DEQI4Lj66FfrKijotpW8kqUJIxhsAfeEumfKkhNZFWp6JWIea1FefrdUI o97o6j3MGe6ogHiVbK3rVj0eznpzMTmz3p0S26JiA6DJzmZ1N/qri0Sza+onoa2d6U+b bTDlAcGU++Gterb/6aki6eoB/QyBWHhjYbEBJU0XTsd42sRrfIRkBh7XEeMYZyToLF02 XnawhosDOYfn0vw4/AqQxoFS9wewjJPuE44UTTYVWekqL8d/R0AOJ4v9b1KEj5xdigQA lLAGWlW/rfQWRyFLBNwnwn91jzV/++Qwy0SIC2LDDOYD+96PUadxYqjzKKLl+oO0JPd1 eOhg== X-Gm-Message-State: APjAAAW2OX72WTpGoG1dbMS60aXvS5QOhnJaa3bz7iDdiqGN9/mY5x1Z J3fr+0rbo9qVck3U9fVtD/jC+KJC X-Google-Smtp-Source: APXvYqxFbpn4rvCXYLC0iHnYx373bo+3OFC/cxq982tXg7b6bU/Fn4QAQX/i7Hv3mBa/m36oNw4ycw== X-Received: by 2002:a1c:9cc6:: with SMTP id f189mr4810633wme.144.1571786647982; Tue, 22 Oct 2019 16:24:07 -0700 (PDT) Original-Received: from bother.homenet ([2002:218:8d56:10:78b1:cce7:564a:b9a6]) by smtp.gmail.com with ESMTPSA id 65sm17079556wrs.9.2019.10.22.16.24.06 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2019 16:24:07 -0700 (PDT) Original-Received: from bother.homenet (localhost [127.0.0.1]) by bother.homenet (Postfix) with SMTP id 39613260C93 for ; Wed, 23 Oct 2019 00:24:27 +0100 (BST) In-Reply-To: <907270af-1f2f-42f3-ec36-047fdd48a74f@posteo.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::336 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:15783 Archived-At: On Tue, 22 Oct 2019 21:23:32 +0200 Zelphir Kaltstahl wrote: [snip] > The reason however, why I have only ever used Riot with one person is, > surprise surprise, that most people are not willing to sacrifice the > tiniest bit of comfort, for enhanced security. This one person I used it > with tried to get 2 more people on board, who were even less tech-savy > and whom I did not have the chance of helping directly, to get things > set up and so we remained 1-on-1 on Riot.IM. > > Let me explain further: > > To verify another person's device, one has to exchange information via a > second trusted channel. That information is a sequence of icons being > shown. If they are the same, that the other person sends you via the > second trusted channel, you can reasonably assume, that the device you > are communicating with is under their control. > > When it comes to the step of exchanging information about what icons are > displayed, most people will close the app and say "it's too > complicated", because they do not understand it ("Huh? How strange! Why > I have to do that? Are icons secure?") or do not want to do anything in > order to have security. They are not willing to invest as much as 5min > of effort, to have encrypted chat. What makes matters worse is, that > when you use Riot.IM in the browser, it might happen, that every time > you log in, the other person has to re-verify your device. Guess what > people will do when facing that workflow … This is a public mailing list, and any replacement of it is going to be a mailing-list-alike. Why do they (or chats) need to be encrypted or have the sender verified? No one should be posting sensitive personal information here so I don't understand the point of it. Lack of understanding of (or disagreement with) the purpose may be what is holding your idea back. If you want to set up private mailing lists or chat servers, fair enough, but that's not what this is. Discord seems a reasonably popular chat medium with a bridge to IRC and discourse seems reasonably popular as a web based mailing-list-ish medium with a somewhat more vibey feel than traditional mailing lists.