From owner-freebsd-ports@freebsd.org  Thu Aug  6 11:20:18 2015
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89C479B5BC6
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Thu,  6 Aug 2015 11:20:18 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4C07FEDB
 for <freebsd-ports@freebsd.org>; Thu,  6 Aug 2015 11:20:18 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1ZNJDW-000Omh-Jj; Thu, 06 Aug 2015 13:20:10 +0200
Date: Thu, 6 Aug 2015 13:20:10 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Matthias Apitz <guru@unixarea.de>, Carlos Jacobo Puga Medina <cpm@fbsd.es>,
 "aorchid@mac.com" <aorchid@mac.com>,
 "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>
Subject: Re: Telegram-cli Issues
Message-ID: <20150806112010.GE40589@home.opsec.eu>
References: <1438811675.26770.4.camel@fbsd.es>
 <20150806105936.GA5474@c720-r276659>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150806105936.GA5474@c720-r276659>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2015 11:20:18 -0000

Hi!

> The Telegram protocol and clients have a feature to shown to the sender
> when the receiver has read the message, Telegram Support calls this
> "read" status for messages and says it is an essential feature of
> Telegram.
> 
> I call it a violation of the receivers privacy.

100% agreed.

> It would be nice, if we (FreeBSD) could add (as a patch in the ports
> tree) a configuration value to the telegram-cli which does not
> send such notifications when the configuration says so.
> 
> What do you (all and Maintainer) think about?

That would be very useful, yes.

-- 
pi@opsec.eu            +49 171 3101372                         5 years to go !