The Tor Browser overlaps only slightly. It provides strong anonymity with a cost on usability (defaulting through Tor). The steps to get from today's open internet to a more secured one requires granularity of privacy options. Tor is important but there is still space to deal with webmail crypto, distributed dns and other features even without switching the default search engine. And these will not all come from extensions, nor should they.
Consider the issue of building indicators and UI for proper fingerprint verification for eventual webmail gpg support. This will overlap, contribute and borrow from current efforts to deal with certificate evolution and reliability indicators. The potential for privacy improvements should excite UI designers at Mozilla and developers alike. And though the search engine switch is only one minor change of many even this could still be done in a donor friendly manner. Implement a Privacy option similar to private browsing that switches the engine and features (http referrer support and the likes). On Monday, July 22, 2013 10:34:18 PM UTC+2, R. Jason Cronk wrote: > I think there are some valuable points here. My only counter would be > > Mozilla can't effectively remove Google by default at this point as it > > accounts for somewhere between 80% and 90% of the non-profit's revenue. > > > > http://pulse2.com/2012/11/17/mozilla-earned-163-million-in-2011/ > > > > To my knowledge, DuckDuckGo (and it's privacy preserving competitor > > StartPageSearch) have no revenue streams that could effectively fund > > Mozilla. > > > > One additional comment, if you're want to develop to support an enhanced > > privacy conscious web browser, I would point you to the TOR project > > which uses a modified Firefox ESR specifically engineered to protect the > > privacy of the users. See > > https://www.torproject.org/getinvolved/volunteer.html.en to volunteer. > > > > Jason > > > > > > On 7/22/2013 4:10 PM, Kd M wrote: > > > There is a wide open space for improving privacy and security on the > > internet. Little to nothing has changed since 1992 when Steve jobs demoed > > email encryption (http://youtu.be/7mgG4a591zQ?t=59m38s). The world changed > > though and many people use webmail these days. This is a space where > > Mozilla could take upon itself to set standards by introducing the means to > > securely generate and store key pairs, exposing this through API's for > > extensions or rolling one that is actually usable and integrated for all. > > > > > > It would be pertinent to look ahead and support the design of distributed > > DNS systems. This can not be done with extensions. In 1990 in response to > > concerns from the EU that ICANN may permit the USG to abuse DNS for > > national reasons they responded saying they would only ever ensure the > > functionality of the internet. 3 years ago they were responsible for > > helping DHS take down URLs that linked to content or were political in > > nature. So supporting distributed DNS is the right thing to do to protect > > the neutrality of the internet in the future. > > > > > > Finally, and this i guess is the hardest sell, Mozilla should use > > duckduckgo by default. > > > > > > This may sound all political in nature but only if you already divested > > from the idea that political neutrality is important to the internet. These > > ideas help save that neutrality and protect the definition of privacy those > > of us that grew up with the internet have come to understand. > > > > > > If none of these are things Mozilla is able to do I would be happy to join > > a fork or hear from developers interesting in building a truly privacy > > conscious, while still usable, browser. > > > _______________________________________________ > > > dev-privacy mailing list > > > [email protected] > > > https://lists.mozilla.org/listinfo/dev-privacy > > > > > > > > > *R. Jason Cronk, Esq., CIPP/US* > > /Privacy Engineering Consultant/, *Enterprivacy Consulting Group* > > <enterprivacy.com> > > > > * phone: (828) 4RJCESQ > > * twitter: @privacymaverick.com > > * blog: http://blog.privacymaverick.com _______________________________________________ dev-privacy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-privacy
