From owner-freebsd-questions@FreeBSD.ORG  Thu Aug 29 12:26:19 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id E6F151E9
 for <freebsd-questions@freebsd.org>; Thu, 29 Aug 2013 12:26:19 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id BB68622B7
 for <freebsd-questions@freebsd.org>; Thu, 29 Aug 2013 12:26:19 +0000 (UTC)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E422822156
 for <freebsd-questions@freebsd.org>; Thu, 29 Aug 2013 08:26:15 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute1.internal (MEProxy); Thu, 29 Aug 2013 08:26:15 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=wm+atzmsYy241gBQAQ7Iz5Mfsds=; b=g80
 XhWyteb7J/ipwYP1NbbcmXWHuOp9e5a3rQkhgepZPgWMEe49Clh7hBthZk7HwoEw
 PxIJO8VqrDYIda92xx1nMNYM3JRbcsjrCP8Ub1n6SIZlgvbZcxp2oxO3e91gRbm5
 FU+JkTIvcIYEmQKsm+AhSQWsy+GWckU9NSJvrakY=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 88514B00036; Thu, 29 Aug 2013 08:26:15 -0400 (EDT)
Message-Id: <1377779175.4658.15540849.45733C82@webmail.messagingengine.com>
X-Sasl-Enc: 3ZlQtSjzauYsCN9miRJGA/NDOO+7xQa84bympT96yEMd 1377779175
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-be0d4992
In-Reply-To: <CA+DHxHLYn5+gbWfELWwC7iYRYYw5KReUsoYtXgTQnLZMU==RiQ@mail.gmail.com>
References: <CA+DHxHLYn5+gbWfELWwC7iYRYYw5KReUsoYtXgTQnLZMU==RiQ@mail.gmail.com>
Subject: Re: Way to be announced about security updates and new releases
Date: Thu, 29 Aug 2013 07:26:15 -0500
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 12:26:20 -0000

On Wed, Aug 21, 2013, at 1:54, Antonio Kless wrote:
> Is there any way to be noticed, when security updates or new releases are
> available?
> 
> https://twitter.com/freebsd nearly would be a solution, if it did not
> repostquestions from its
> subscribers and other information that is not related to updates.
> 

http://twitter.com/freebsdsecurity is probably what you're looking for.
There are several twitter accounts run by FreeBSD members