[liberationtech] Ghostery, NoScript.. add-ons frequently phone home

[Aymeric Vitte]

Let me answer anyway.

I know what is being sent outside, I have given some examples in my 
first reply.

I don't get what's the big deal for Mozilla to clarify for everybody 
what FF is sending outside without the users being aware of it, for what 
purpose and what is inside the https message, since this is supposed to 
protect people.

The answer "block google.com and related sites" does not really help.

Le 27/04/2015 01:38, Yosem Companys a écrit :
> This thread has turned belligerent, so it has been closed. Please feel 
> free to continue discussing other subjects of interest.
>
> Thanks,
> Yosem
> One of the moderators
>
> On Sun, Apr 26, 2015 at 4:36 PM, Al Billings <albill at openbuddha.com 
> <mailto:albill at openbuddha.com>> wrote:
>
>     I'm not sure why you're asking us for the list instead of finding
>     it yourself.
>
>
>
>     > On Apr 26, 2015, at 4:14 PM, Aymeric Vitte
>     <vitteaymeric at gmail.com <mailto:vitteaymeric at gmail.com>> wrote:
>     >
>     > Answer the question, YOU said "block google.com
>     <http://google.com>" and "related sites", I did not
>     >
>     > The question was:
>     >
>     > Could you be more precise and give the complete list of
>     safebrowsing_stuff.google.com
>     <http://safebrowsing_stuff.google.com> and "related sites" that FF
>     is using (including Mozilla's)?
>     >
>     > Which is not about safebrowsing or similar only as shown in my
>     previous answer and certainly not about blocking all things
>     >
>     > Le 26/04/2015 22:26, Al Billings a écrit :
>     >> If you're the kind of person paranoid about safebrowing pings
>     and similar, yeah, you should pull the tinfoil hat tighter and
>     block all things.
>     >>
>     >>
>     >>
>     >>> On Apr 26, 2015, at 11:06 AM, Aymeric Vitte
>     <vitteaymeric at gmail.com <mailto:vitteaymeric at gmail.com>> wrote:
>     >>>
>     >>> Are you serious? "block google.com <http://google.com>"
>     >>>
>     >>> Should we block mozilla.org <http://mozilla.org> too?
>     >
>     > --
>     > Check the 10 M passwords list: http://peersm.com/findmyass
>     > Anti-spies and private torrents, dynamic blocklist:
>     http://torrent-live.org
>     > Peersm : http://www.peersm.com
>     > torrent-live: https://github.com/Ayms/torrent-live
>     > node-Tor : https://www.github.com/Ayms/node-Tor
>     > GitHub : https://www.github.com/Ayms
>     >
>     > --
>     > Liberationtech is public & archives are searchable on Google.
>     Violations of list guidelines will get you moderated:
>     https://mailman.stanford.edu/mailman/listinfo/liberationtech.
>     Unsubscribe, change to digest, or change password by emailing
>     moderator at companys at stanford.edu <mailto:companys at stanford.edu>.
>     --
>     Liberationtech is public & archives are searchable on Google.
>     Violations of list guidelines will get you moderated:
>     https://mailman.stanford.edu/mailman/listinfo/liberationtech.
>     Unsubscribe, change to digest, or change password by emailing
>     moderator at companys at stanford.edu <mailto:companys at stanford.edu>.
>
>
>
>

-- 
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/liberationtech/attachments/20150427/ed66e9d8/attachment.html>