From owner-freebsd-questions@FreeBSD.ORG Wed May 14 20:23:32 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 043BAA66 for ; Wed, 14 May 2014 20:23:32 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A591926AB for ; Wed, 14 May 2014 20:23:30 +0000 (UTC) Received: from r56.edvax.de (port-92-195-108-40.dynamic.qsc.de [92.195.108.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 5F34F3CD18; Wed, 14 May 2014 22:23:21 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s4EKNKda002105; Wed, 14 May 2014 22:23:20 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 14 May 2014 22:23:20 +0200 From: Polytropon To: Antonio Olivares Subject: Re: Firefox will adapt closed source DRM Message-Id: <20140514222320.cce7c921.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2014 20:23:32 -0000 On Wed, 14 May 2014 14:44:48 -0400, Antonio Olivares wrote: > Dear folks, > > Firefox will adapt DRM stuff into it. Can it be turned off, i.e, when > compiling it? > or do we simply move on to another browser? That would not help much. Many users have "Flash" installed, which is also closed source and implements DRM as well. Such kind of plugins, usually video players or gaming interfaces, have been used by websites for at least a decade to restrict the access to the content. Now that there seems to be a W3C "consensus" of making such functionality part of HTML, there's hardly a way around it. If Firefox does not implement the restriction management within its "HTML engine", it will appear to the user that "the web is broken", which (of course) is a fault of the browser, so in order to see the dancing bunnies, he will switch to a different browser which applies the restriction management accordingly. And if this functionality is only available or legal in proprietary (non-open, non-free) form, then it's basically the same approach as installing a "Flash" plugin. I don't want to sound impolite, but following this trend is the only chance of Firefox to "stay in the game". :-( More inspiration here: http://andreasgal.com/2014/05/14/eme/ -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...