Re: [Bug-gnuzilla] Encrypted Media Extensions (EME) to be removed?

[Ian D]

On 05/18/2014 06:09 AM, Solal wrote:
> Le 18/05/2014 11:27, al3xu5 / dotcommon a écrit :
> > Hi all
> >
> > Have you read about Encrypted Media Extensions (EME)? See:
> > https://u.fsf.org/xk
> >
> > I think next releases of Icecat should be build *without* EME and
> > any other DRM-related stuff.
> >
> > Hope you all agree. Regards
> I completely agree. The EME absurdity is because DRM depends of
> proprietary software. Free web browsers make EME totally harmless.
> I think aslo do it only in IceCat is stupid : Firefox, Iceweasel and
> BurningDog can do the same thing. I think they will all agree because
> Mozilla, Debian and gNewSense are as FSF : they care about freedom...
    If I'm not mistaken, gNewSense will have to remove it in their 
version, or risk losing the support of the FSF.  As for Debian, they 
*seem* to want to get along with the FSF, so they may remove it from 
IceWeasel.

    I think someone should try to keep up with Firefox's source code, 
to try and find out how to remove EME.  Chances are we either need to 
specify a compiler flag, or apply several patches to remove EME.
> > PS: Personally, also I think it should be better to completely
> > remove ALL the other "dangerous" stuff. Such are, in my opinion,
> > any SaaS/Cloud and Tracking "features" (i.e. "Firefox Sync",
> > "geolocation", "social" ...)
> For Firefox Sync, why not create IceCat Sync, totally P2P? For SaaSS,
> this is impossible (it's technically impossible to know if a service
> is a SaaSS or not, only an human can do it)? For "social" sutff (which
> are totally unsocial), I agree. For geolocation, I'm not agreeing
> because some web services use geolocation.
    We actually found that the old Firefox Sync was alright.  I'm not 
sure about the new one (the one from 29.0).  If we had more people to 
work on it, then we might be able to create a version of Firefox Sync 
ourselves, as you are suggesting.  Personally, I agree with you, that we 
should.

    If geolocation doesn't respect the user's freedom, then it 
shouldn't be included in IceCat, regardless of what web services use 
it.  In my opinion, if it can be removed or turned off, then it 
shouldn't be a problem.

Ian D