[gofetch.git] / test / expected / SLASHDOT / 0102637536.html

<!DOCTYPE html>
<html>
<head>
  <meta http-equiv='content-type' content='text/html; charset=utf-8'>
  <meta name='viewport' content='width=device-width, initial-scale=1.0'>
  <style type='text/css'>
    body { margin: 1em 15%; }
  </style>
</head>
<body>
<div class='story'>
	<h2>Tor Browser Gets a Redesign, Switches To New Firefox Quantum Engine (zdnet.com)</h2>
	<div class='details'>(Thursday September 06, 2018 @11:30PM (msmash) 
from the for-the-record dept.)</div>
	<br/>
    <ul>
    <li>Reference: <a href=''>0102637536</a></li>
        <li>News link: <a href='https://yro.slashdot.org/story/18/09/06/1651255/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine'>https://yro.slashdot.org/story/18/09/06/1651255/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine</a></li>
        <li>Source link: <a href='https://www.zdnet.com/article/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine/'>https://www.zdnet.com/article/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine/</a></li>
    </ul>
	<br/>
	<div class='content' style='text-align: justify'>
		The Tor Browser has [1]rolled out a new interface with the release of v8 . From a report:<br/><br/>&gt; The Tor Browser has always been based on the Firefox codebase, but it lagged behind a few releases. Mozilla rolled out a major overhaul of the Firefox codebase in November 2017, with the release of Firefox 57, [2]the first release in the Firefox Quantum series . Firefox Quantum came with a new page rendering engine, a new add-ons API, and a new user interface called the Photon UI. Because these were major, code-breaking changes, it took the smaller Tor team some time to integrate all of them into the Tor Browser codebase and make sure everything worked as intended. The new Tor Browser 8, released yesterday, is now in sync with the most recent version of Firefox, the Quantum release, and also supports all of its features. This means the Tor Browser now uses the same modern Photon UI that current Firefox versions use, it supports the same speed-optimized page rendering engine and has also dropped support for the old XUL-based add-ons system for the new WebExtensions API system used by Chrome, Opera, Vivaldi, Brave, and the rest of the Chromium browsers.<br/><br/><br/><br/>[1] https://www.zdnet.com/article/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine/<br/><br/>[2] https://news.slashdot.org/story/17/11/25/1938225/firefox-quantum-is-better-faster-smarter-than-chrome-says-wired
	</div>
<hr/>
  <div class='comment' style='display: block; margin-left: 80px'>
    <h3></h3>
    <div class='by' style='font-style: italic;'></div>
    <div class='comment_content'></div>
    <div class='comment' style='display: block; margin-left: 80px'>
      <h3>Re: Isn't page render speed pretty irrelevant for (Score:1)</h3>
      <div class='by' style='font-style: italic;'>by Anonymous Coward</div>
      <div class='comment_content'><p></p><p>Not when you have the assets already cached. Most people donâ(TM)t just visit a site once. I was playing with it this morning. Itâ(TM)s a decent speed improvement even within the restraints of tor</p><p>More impressively msmash posted an actual tech article not a biasedpolitical article for a change. Losing too many readers now I suspect</p></div>
    </div>
    <div class='comment' style='display: block; margin-left: 80px'>
      <h3>Re: (Score:3, Insightful)</h3>
      <div class='by' style='font-style: italic;'>by Tough Love ( 215404 )</div>
      <div class='comment_content'><p></p><p>> It's not like a new page renderer is going to solve that.</p><p>The point is to be synced up to the current Firefox codebase. Which by the way is awesome. I have all my favorite extensions running, in spite of all the FUD about the new Webextensions API.</p></div>
      <div class='comment' style='display: block; margin-left: 80px'>
        <h3>Re: (Score:2)</h3>
        <div class='by' style='font-style: italic;'>by Tough Love ( 215404 )</div>
        <div class='comment_content'><p></p><p>>> It's not like a new page renderer is going to solve that.</p><p>> The point is to be synced up to the current Firefox codebase. Which by the way is awesome. I have all my favorite extensions running, in spite of all the FUD about the new Webextensions API.</p><p>Why would anybody mod that comment troll?</p></div>
        <div class='comment' style='display: block; margin-left: 80px'>
          <h3></h3>
          <div class='by' style='font-style: italic;'></div>
          <div class='comment_content'></div>
          <div class='comment' style='display: block; margin-left: 80px'>
            <h3>Re: (Score:2)</h3>
            <div class='by' style='font-style: italic;'>by Tough Love ( 215404 )</div>
            <div class='comment_content'><p></p><p>It is FUD. Firefox's extension ecology is as vibrant as ever, but far more secure. And if somebody disagrees, they should do so instead of taking the belly slither route.</p></div>
            <div class='comment' style='display: block; margin-left: 80px'>
              <h3></h3>
              <div class='by' style='font-style: italic;'></div>
              <div class='comment_content'></div>
              <div class='comment' style='display: block; margin-left: 80px'>
                <h3>Re: (Score:2)</h3>
                <div class='by' style='font-style: italic;'>by theweatherelectric ( 2007596 )</div>
                <div class='comment_content'><p></p><p>You can use the built-in [1]Reader View [mozilla.org] for a lot of pages, but it's not available for all pages. It depends on the page structure.</p><p></p><p></p><p></p><p></p><p>[1] https://support.mozilla.org/en-US/kb/firefox-reader-view-clutter-free-web-pages</p></div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
  <div class='comment' style='display: block; margin-left: 80px'>
    <h3>Tested today (Score:1)</h3>
    <div class='by' style='font-style: italic;'>by Anonymous Coward</div>
    <div class='comment_content'><p></p><p>First impression is I like it. Video playback seems sluggish but overall positive. Hopefully any NSA addons did not make the cut.</p></div>
  </div>
  <div class='comment' style='display: block; margin-left: 80px'>
    <h3>Who can afford to run a tor exit node ? (Score:4, Interesting)</h3>
    <div class='by' style='font-style: italic;'>by dargaud ( 518470 )</div>
    <div class='comment_content'><p></p><p>I really wonder that. I support tor. I've never actually used it because I don't have much to hide, but I understand that other do. So I ran a tor relay (not exit) as my way of supporting the project for a while; from my home adsl. After a while I noticed some weird stuff going on. Some websites (important ones) wouldn't load properly. Emails sent would bounce or simply never reach their destination. After looking at the problem I found that my IP was on some minor blacklists. I stopped the relay and after 2 days I was off the blacklists. Hence my question, if running a simple relay gets you blacklisted, what does running an exit point does to your other internet usage from that IP ? Who can afford separate IPs besides institutions ? So who is really really running them ? Certainly not private citizens...</p></div>
    <div class='comment' style='display: block; margin-left: 80px'>
      <h3>Re: (Score:3)</h3>
      <div class='by' style='font-style: italic;'>by ftobin ( 48814 )</div>
      <div class='comment_content'><p></p><p>You can run something like a Linode instance pretty cheaply and get more IPs. I've run a highly restricted exit node in the past (low bandwidth, select ports), and I've had the same problems with you if I try to use my Linode as a web proxy. My most recent problem has been with Shut Up and Sit Down RSS feeds, which are blocking my host  :-\</p></div>
      <div class='comment' style='display: block; margin-left: 80px'>
        <h3>Re:Who can afford to run a tor exit node ? (Score:4, Informative)</h3>
        <div class='by' style='font-style: italic;'>by tlhIngan ( 30335 )</div>
        <div class='comment_content'><p></p><p>> You can run something like a Linode instance pretty cheaply and get more IPs. I've run a highly restricted exit node in the past (low bandwidth, select ports), and I've had the same problems with you if I try to use my Linode as a web proxy. My most recent problem has been with Shut Up and Sit Down RSS feeds, which are blocking my host  :-\</p><p>And that's just because no matter how noble the cause, idiots will just ruin it. You don't need a list of Tor exit nodes because if you run a reasonably popular website, you'll find out quite rapidly what they are and auto-blacklist t hem.</p><p>It's why CDNs like CloudFlare block Tor - the abuse from Tor exit nodes ensures that whatever trigger you use, it'll be triggered and you'll end up blocking it. It's not like it's done deliberately - you don't have to seek out new Tor exit nodes. They just make themselves known.</p><p>I'd even venture to say if you want to allow Tor traffic, you have to whitelist them specifically It's not that Tor is bad, it's just that it's got a bunch of bad actors that really do ruin it for those who need it.</p></div>
        <div class='comment' style='display: block; margin-left: 80px'>
          <h3>Re: (Score:2)</h3>
          <div class='by' style='font-style: italic;'>by ftobin ( 48814 )</div>
          <div class='comment_content'><p></p><p>> And that's just because no matter how noble the cause, idiots will just ruin it. You don't need a list of Tor exit nodes because if you run a reasonably popular website, you'll find out quite rapidly what they are and auto-blacklist t hem.</p><p>I should mention that I don't and never did allow access on port 80 or 443, yet Shut up and Sit Down's RSS feed blocks me. There is no way my host was causing issues for their site, with the 20 KB/s of bandwidth I allowed. Additionally, I only allowed ports like IRC, DN</p></div>
        </div>
      </div>
    </div>
    <div class='comment' style='display: block; margin-left: 80px'>
      <h3>Re: (Score:2)</h3>
      <div class='by' style='font-style: italic;'>by bill_mcgonigle ( 4333 ) *</div>
      <div class='comment_content'><p></p><p>Check out the Library Freedom Project.</p></div>
    </div>
    <div class='comment' style='display: block; margin-left: 80px'>
      <h3>Re: (Score:2)</h3>
      <div class='by' style='font-style: italic;'>by AHuxley ( 892839 )</div>
      <div class='comment_content'><p></p><p>Governments.</p></div>
    </div>
  </div>
  <div class='comment' style='display: block; margin-left: 80px'>
    <h3></h3>
    <div class='by' style='font-style: italic;'></div>
    <div class='comment_content'></div>
    <div class='comment' style='display: block; margin-left: 80px'>
      <h3>Re: (Score:2)</h3>
      <div class='by' style='font-style: italic;'>by AHuxley ( 892839 )</div>
      <div class='comment_content'><p></p><p>NSA, CIA, GCHQ did not worry about anonymous communication.</p><p>Police with lots of cash per investigation at a national level don't worry about anonymous communication anymore.</p></div>
    </div>
  </div>
</div>
</body>
Commit	Line	Data
299a08f3 NR	1	<!DOCTYPE html>
	2	<html>
	3	<head>
	4	<meta http-equiv='content-type' content='text/html; charset=utf-8'>
	5	<meta name='viewport' content='width=device-width, initial-scale=1.0'>
	6	<style type='text/css'>
	7	body { margin: 1em 15%; }
	8	</style>
	9	</head>
	10	<body>
	11	<div class='story'>
c715ea02	12	<h2>Tor Browser Gets a Redesign, Switches To New Firefox Quantum Engine (zdnet.com)</h2>
299a08f3 NR	13	<div class='details'>(Thursday September 06, 2018 @11:30PM (msmash)
	14	from the for-the-record dept.)</div>
	15	<br/>
	16	<ul>
c715ea02	17	<li>Reference: <a href=''>0102637536</a></li>
299a08f3 NR	18	<li>News link: <a href='https://yro.slashdot.org/story/18/09/06/1651255/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine'>https://yro.slashdot.org/story/18/09/06/1651255/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine</a></li>
	19	<li>Source link: <a href='https://www.zdnet.com/article/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine/'>https://www.zdnet.com/article/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine/</a></li>
	20	</ul>
	21	<br/>
	22	<div class='content' style='text-align: justify'>
e818d449	23	The Tor Browser has [1]rolled out a new interface with the release of v8 . From a report:<br/><br/>> The Tor Browser has always been based on the Firefox codebase, but it lagged behind a few releases. Mozilla rolled out a major overhaul of the Firefox codebase in November 2017, with the release of Firefox 57, [2]the first release in the Firefox Quantum series . Firefox Quantum came with a new page rendering engine, a new add-ons API, and a new user interface called the Photon UI. Because these were major, code-breaking changes, it took the smaller Tor team some time to integrate all of them into the Tor Browser codebase and make sure everything worked as intended. The new Tor Browser 8, released yesterday, is now in sync with the most recent version of Firefox, the Quantum release, and also supports all of its features. This means the Tor Browser now uses the same modern Photon UI that current Firefox versions use, it supports the same speed-optimized page rendering engine and has also dropped support for the old XUL-based add-ons system for the new WebExtensions API system used by Chrome, Opera, Vivaldi, Brave, and the rest of the Chromium browsers.<br/><br/><br/><br/>[1] https://www.zdnet.com/article/tor-browser-gets-a-redesign-switches-to-new-firefox-quantum-engine/<br/><br/>[2] https://news.slashdot.org/story/17/11/25/1938225/firefox-quantum-is-better-faster-smarter-than-chrome-says-wired
299a08f3 NR	24	</div>
	25	<hr/>
	26	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	27	<h3></h3>
299a08f3 NR	28	<div class='by' style='font-style: italic;'></div>
	29	<div class='comment_content'></div>
	30	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	31	<h3>Re: Isn't page render speed pretty irrelevant for (Score:1)</h3>
299a08f3 NR	32	<div class='by' style='font-style: italic;'>by Anonymous Coward</div>
	33	<div class='comment_content'><p></p><p>Not when you have the assets already cached. Most people donâ(TM)t just visit a site once. I was playing with it this morning. Itâ(TM)s a decent speed improvement even within the restraints of tor</p><p>More impressively msmash posted an actual tech article not a biasedpolitical article for a change. Losing too many readers now I suspect</p></div>
	34	</div>
	35	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	36	<h3>Re: (Score:3, Insightful)</h3>
299a08f3 NR	37	<div class='by' style='font-style: italic;'>by Tough Love ( 215404 )</div>
	38	<div class='comment_content'><p></p><p>> It's not like a new page renderer is going to solve that.</p><p>The point is to be synced up to the current Firefox codebase. Which by the way is awesome. I have all my favorite extensions running, in spite of all the FUD about the new Webextensions API.</p></div>
	39	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	40	<h3>Re: (Score:2)</h3>
299a08f3 NR	41	<div class='by' style='font-style: italic;'>by Tough Love ( 215404 )</div>
	42	<div class='comment_content'><p></p><p>>> It's not like a new page renderer is going to solve that.</p><p>> The point is to be synced up to the current Firefox codebase. Which by the way is awesome. I have all my favorite extensions running, in spite of all the FUD about the new Webextensions API.</p><p>Why would anybody mod that comment troll?</p></div>
	43	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	44	<h3></h3>
299a08f3 NR	45	<div class='by' style='font-style: italic;'></div>
	46	<div class='comment_content'></div>
	47	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	48	<h3>Re: (Score:2)</h3>
299a08f3 NR	49	<div class='by' style='font-style: italic;'>by Tough Love ( 215404 )</div>
	50	<div class='comment_content'><p></p><p>It is FUD. Firefox's extension ecology is as vibrant as ever, but far more secure. And if somebody disagrees, they should do so instead of taking the belly slither route.</p></div>
	51	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	52	<h3></h3>
299a08f3 NR	53	<div class='by' style='font-style: italic;'></div>
	54	<div class='comment_content'></div>
	55	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	56	<h3>Re: (Score:2)</h3>
299a08f3 NR	57	<div class='by' style='font-style: italic;'>by theweatherelectric ( 2007596 )</div>
	58	<div class='comment_content'><p></p><p>You can use the built-in [1]Reader View [mozilla.org] for a lot of pages, but it's not available for all pages. It depends on the page structure.</p><p></p><p></p><p></p><p></p><p>[1] https://support.mozilla.org/en-US/kb/firefox-reader-view-clutter-free-web-pages</p></div>
	59	</div>
	60	</div>
	61	</div>
	62	</div>
	63	</div>
	64	</div>
	65	</div>
	66	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	67	<h3>Tested today (Score:1)</h3>
299a08f3 NR	68	<div class='by' style='font-style: italic;'>by Anonymous Coward</div>
	69	<div class='comment_content'><p></p><p>First impression is I like it. Video playback seems sluggish but overall positive. Hopefully any NSA addons did not make the cut.</p></div>
	70	</div>
	71	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	72	<h3>Who can afford to run a tor exit node ? (Score:4, Interesting)</h3>
299a08f3 NR	73	<div class='by' style='font-style: italic;'>by dargaud ( 518470 )</div>
	74	<div class='comment_content'><p></p><p>I really wonder that. I support tor. I've never actually used it because I don't have much to hide, but I understand that other do. So I ran a tor relay (not exit) as my way of supporting the project for a while; from my home adsl. After a while I noticed some weird stuff going on. Some websites (important ones) wouldn't load properly. Emails sent would bounce or simply never reach their destination. After looking at the problem I found that my IP was on some minor blacklists. I stopped the relay and after 2 days I was off the blacklists. Hence my question, if running a simple relay gets you blacklisted, what does running an exit point does to your other internet usage from that IP ? Who can afford separate IPs besides institutions ? So who is really really running them ? Certainly not private citizens...</p></div>
	75	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	76	<h3>Re: (Score:3)</h3>
299a08f3 NR	77	<div class='by' style='font-style: italic;'>by ftobin ( 48814 )</div>
	78	<div class='comment_content'><p></p><p>You can run something like a Linode instance pretty cheaply and get more IPs. I've run a highly restricted exit node in the past (low bandwidth, select ports), and I've had the same problems with you if I try to use my Linode as a web proxy. My most recent problem has been with Shut Up and Sit Down RSS feeds, which are blocking my host :-\</p></div>
	79	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	80	<h3>Re:Who can afford to run a tor exit node ? (Score:4, Informative)</h3>
299a08f3 NR	81	<div class='by' style='font-style: italic;'>by tlhIngan ( 30335 )</div>
	82	<div class='comment_content'><p></p><p>> You can run something like a Linode instance pretty cheaply and get more IPs. I've run a highly restricted exit node in the past (low bandwidth, select ports), and I've had the same problems with you if I try to use my Linode as a web proxy. My most recent problem has been with Shut Up and Sit Down RSS feeds, which are blocking my host :-\</p><p>And that's just because no matter how noble the cause, idiots will just ruin it. You don't need a list of Tor exit nodes because if you run a reasonably popular website, you'll find out quite rapidly what they are and auto-blacklist t hem.</p><p>It's why CDNs like CloudFlare block Tor - the abuse from Tor exit nodes ensures that whatever trigger you use, it'll be triggered and you'll end up blocking it. It's not like it's done deliberately - you don't have to seek out new Tor exit nodes. They just make themselves known.</p><p>I'd even venture to say if you want to allow Tor traffic, you have to whitelist them specifically It's not that Tor is bad, it's just that it's got a bunch of bad actors that really do ruin it for those who need it.</p></div>
	83	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	84	<h3>Re: (Score:2)</h3>
299a08f3 NR	85	<div class='by' style='font-style: italic;'>by ftobin ( 48814 )</div>
	86	<div class='comment_content'><p></p><p>> And that's just because no matter how noble the cause, idiots will just ruin it. You don't need a list of Tor exit nodes because if you run a reasonably popular website, you'll find out quite rapidly what they are and auto-blacklist t hem.</p><p>I should mention that I don't and never did allow access on port 80 or 443, yet Shut up and Sit Down's RSS feed blocks me. There is no way my host was causing issues for their site, with the 20 KB/s of bandwidth I allowed. Additionally, I only allowed ports like IRC, DN</p></div>
	87	</div>
	88	</div>
	89	</div>
	90	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	91	<h3>Re: (Score:2)</h3>
299a08f3 NR	92	<div class='by' style='font-style: italic;'>by bill_mcgonigle ( 4333 ) *</div>
	93	<div class='comment_content'><p></p><p>Check out the Library Freedom Project.</p></div>
	94	</div>
	95	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	96	<h3>Re: (Score:2)</h3>
299a08f3 NR	97	<div class='by' style='font-style: italic;'>by AHuxley ( 892839 )</div>
	98	<div class='comment_content'><p></p><p>Governments.</p></div>
	99	</div>
	100	</div>
	101	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	102	<h3></h3>
299a08f3 NR	103	<div class='by' style='font-style: italic;'></div>
	104	<div class='comment_content'></div>
	105	<div class='comment' style='display: block; margin-left: 80px'>
c715ea02	106	<h3>Re: (Score:2)</h3>
299a08f3 NR	107	<div class='by' style='font-style: italic;'>by AHuxley ( 892839 )</div>
	108	<div class='comment_content'><p></p><p>NSA, CIA, GCHQ did not worry about anonymous communication.</p><p>Police with lots of cash per investigation at a national level don't worry about anonymous communication anymore.</p></div>
	109	</div>
	110	</div>
	111	</div>
	112	</body>