Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1

François Kooman <fkooman@tuxed.net> Thu, 03 December 2015 10:09 UTC

Return-Path: <fkooman@tuxed.net>
X-Original-To: storagesync@ietfa.amsl.com
Delivered-To: storagesync@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C30831A6F81 for <storagesync@ietfa.amsl.com>; Thu, 3 Dec 2015 02:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level:
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFGWZXOfkLM1 for <storagesync@ietfa.amsl.com>; Thu, 3 Dec 2015 02:09:52 -0800 (PST)
Received: from ursa.uberspace.de (ursa.uberspace.de [95.143.172.203]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCEF41A6EF4 for <storagesync@ietf.org>; Thu, 3 Dec 2015 02:09:51 -0800 (PST)
Received: (qmail 29056 invoked from network); 3 Dec 2015 10:09:50 -0000
Received: from localhost (HELO ?10.87.3.103?) (127.0.0.1) by ursa.uberspace.de with SMTP; 3 Dec 2015 10:09:50 -0000
To: Michiel de Jong <mbdejong@mozilla.com>
References: <mailman.108.1449000023.26068.storagesync@ietf.org> <1449004445.2745758.455126129.5028FD2B@webmail.messagingengine.com> <CAO_YprZhCmUxEf=aGCYL=+CLbjUoD1ifpDFsrS7N40Npo4wr+w@mail.gmail.com> <1449050174.3667910.455617161.12EEE3C5@webmail.messagingengine.com> <1449051540970-b577e6c2-393e54ef-bbe05be4@gmail.com> <1449052128.3674794.455635937.667C3E1F@webmail.messagingengine.com> <CAPpPfeAdrCZcsYZo7=W6N14K4F2LutXN8BFTetikzKZSr8+vVA@mail.gmail.com> <259424f4.2bca.1516717ef55.Coremail.fsong@bjtu.edu.cn> <56600F0A.9000200@tuxed.net> <CAPpPfeDPHGR+vn0=ji9frF2kr+J=YR76g0e7yOndKzz97bxdHQ@mail.gmail.com>
From: François Kooman <fkooman@tuxed.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <566014EA.2010705@tuxed.net>
Date: Thu, 03 Dec 2015 11:09:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAPpPfeDPHGR+vn0=ji9frF2kr+J=YR76g0e7yOndKzz97bxdHQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/4pkSJqHdzVfiYtCPtGKoC7325fM>
Cc: fsong@bjtu.edu.cn, Linhui Sun <lh.sunlinh@gmail.com>, storagesync <storagesync@ietf.org>, Hugo González Labrador <ietf@hugo.labkode.com>
Subject: Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1
X-BeenThere: storagesync@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mechanisms to synchronize client file systems with Internet-based data storage services <storagesync.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storagesync>, <mailto:storagesync-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/storagesync/>
List-Post: <mailto:storagesync@ietf.org>
List-Help: <mailto:storagesync-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storagesync>, <mailto:storagesync-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2015 10:09:53 -0000

On 12/03/2015 10:52 AM, Michiel de Jong wrote:
> I think we should not (try to) pick one protocol - https://xkcd.com/927/

Saying that after writing your own spec ;)

> I think sync *clients* should be "protocol polyglots" in the same way as
> https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_clients#Protocol_support

Because it worked so well for messaging clients? Yeah, I guess it works
if you live in the year 2000 and don't care about file transfer, voice,
video, offline messaging, receive notifications, sending pictures, group
chats, sync between devices, usable encryption, stickers and the holy
grail: federation. Is this not solved by Signal nowadays?

In theory it is a great idea and I'd agree with you, but in practice not
so much. KISS is key here. I'd recommend building on technology that is
already there, working and proven and free!

Cheers,
François