Remove obsolete statement about working on Chrome APIs in the FAQ
Lunar

Lunar commited on 2014-08-12 13:16:13
Zeige 1 geänderte Dateien mit 6 Einfügungen und 5 Löschungen.


The answer is still probably not optimal, but previously it was misleading.
Wording courtesy of Sebastian.

... ...
@@ -1277,15 +1277,16 @@ on your security, anonymity, and usability priorities.
1277 1277
 Chrome/IE/Opera/etc with Tor.</a></h3>
1278 1278
 
1279 1279
 <p>
1280
-In short, using any browser besides Tor Browser Bundle with Tor is a
1280
+In short, using any browser besides Tor Browser with Tor is a
1281 1281
 really bad idea.
1282 1282
 </p>
1283 1283
 
1284 1284
 <p>
1285
-We're working with the Chrome team to <a
1286
-href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">fix some bugs and missing APIs in Chrome</a> so it
1287
-will be possible to write a Torbutton for Chrome. No support for any
1288
-other browser is on the horizon.
1285
+Our efforts to work with the Chrome team to <a
1286
+href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">add
1287
+missing APIs</a> were unsuccessful, unfortunately. Currently, it is impossible
1288
+to use other browsers and get the same level of protections as when using the
1289
+Tor Browser.
1289 1290
 </p>
1290 1291
 
1291 1292
 <hr>
1292 1293