Power loss is the product of current squared and resistance. Power loss can be minimised by decreasing the current or resistance. As resistance = (length * resistivity) / thickness, to lower the resistance over a set distance we either have to decrease the resistivity (== better wires == expensive!) or increase the thickness (== expensive!). Therefore, we increase the voltage using a transformer before transmitting power over long distances, decreasing the current and hence greatly minimising power loss.
Now, when it detects a story that is from a wire service and just reposted, it will show it on the Gnews site, as Gnews has a subscription for all of them (except AFP apparently.)
You sure about that? Google displays wire stories from AFP, on the Google News FR website at the very least. Also, this has been happening for at least a month. I figured this was a non-event for./ goers, but apparently we're just extraordinarily slow on the uptake.
P.S. Only the last sentence of the summary is really a troll, that little tickle that got you to post in this thread. The rest of it is debatable, so here we are.
It worked, eh? While I did make a mistake RE: wording ("litigation" and "target"), I think the summary achieved the intended effect. The rest of the summary was objective news, the last line was to get./'ers into a frothing mess. It worked;-)
Why is HSBC still the only bank doing this?
Westpac also offer this, or at least for our higher-valued accounts. Nifty little toys that make me feel like a secret agent, they are.;-)
Placing the onus largely on the Opera developers is the wrong way to look at it, IMHO.
As hosts would benefit greatly from this (exponentially so, with the hosts serving the most bandwidth benefitting the most), it would be in their best interests to do whatever it costs to reduce costs. (No pun intended.)
A minimally-modified BitTorrent tracker can be in a standardised location (eg./downloadmanager/tracker), that the browser can check whenever downloading a file from a server. If the location doesn't exist; fine, download via HTTP. (Possibly offer the user a chance to manually substitute a.torrent file here?) If the location does exist, however, it indicates that the webhost is capable and willing to act as a tracker for the file. As the server is hosting the file, hashing it won't pose a problem.
I realise that existing patchy solutions already address a few of these points, but no progress have been made on the browser front. To do so would be to stand out from the competition and be an incentive for all concerned.
While it's certainly kickarse to see a browser implement BitTorrent downloads, it would be even more impressive if they could combine this facet of the program with HTTP downloads. While I can see a number of difficulties with this (technical challenge, lack of standards, etc) these can be minimised in a number of ways.
It would certainly mean much faster speeds for end-users, lower bandwidth costs for hosts and resulting increased user numbers of a standards-compliant browser.
2. ???
3. Profit!
iTMS isn't a P2P application, however. If they were clever about this, they could offer all sorts of incentives: such as credits for uploading lots of data to other subscribers.. they'd certainly cut their costs!
Slashdot Mirror
High school physics:
Power loss is the product of current squared and resistance. Power loss can be minimised by decreasing the current or resistance. As resistance = (length * resistivity) / thickness, to lower the resistance over a set distance we either have to decrease the resistivity (== better wires == expensive!) or increase the thickness (== expensive!). Therefore, we increase the voltage using a transformer before transmitting power over long distances, decreasing the current and hence greatly minimising power loss.Now, when it detects a story that is from a wire service and just reposted, it will show it on the Gnews site, as Gnews has a subscription for all of them (except AFP apparently.)
You sure about that? Google displays wire stories from AFP, on the Google News FR website at the very least. Also, this has been happening for at least a month. I figured this was a non-event for ./ goers, but apparently we're just extraordinarily slow on the uptake.
Have these Slashdot editors not been to school?
Like FreePOPs. You can have your Windows Live Mail and POP3, too!
Not quite. The cat is both included and not included at the same time!
P.S. Only the last sentence of the summary is really a troll, that little tickle that got you to post in this thread. The rest of it is debatable, so here we are.
./'ers into a frothing mess. It worked ;-)
It worked, eh? While I did make a mistake RE: wording ("litigation" and "target"), I think the summary achieved the intended effect. The rest of the summary was objective news, the last line was to get
Why is HSBC still the only bank doing this? Westpac also offer this, or at least for our higher-valued accounts. Nifty little toys that make me feel like a secret agent, they are. ;-)
$DEITY have mercy on the first to patent the time machine.
It pays to think outside the box, even if that box isn't particularly big to begin with.
As hosts would benefit greatly from this (exponentially so, with the hosts serving the most bandwidth benefitting the most), it would be in their best interests to do whatever it costs to reduce costs. (No pun intended.)
A minimally-modified BitTorrent tracker can be in a standardised location (eg. /downloadmanager/tracker), that the browser can check whenever downloading a file from a server. If the location doesn't exist; fine, download via HTTP. (Possibly offer the user a chance to manually substitute a .torrent file here?) If the location does exist, however, it indicates that the webhost is capable and willing to act as a tracker for the file. As the server is hosting the file, hashing it won't pose a problem.
I realise that existing patchy solutions already address a few of these points, but no progress have been made on the browser front. To do so would be to stand out from the competition and be an incentive for all concerned.
While it's certainly kickarse to see a browser implement BitTorrent downloads, it would be even more impressive if they could combine this facet of the program with HTTP downloads. While I can see a number of difficulties with this (technical challenge, lack of standards, etc) these can be minimised in a number of ways. It would certainly mean much faster speeds for end-users, lower bandwidth costs for hosts and resulting increased user numbers of a standards-compliant browser. 2. ??? 3. Profit!
iTMS isn't a P2P application, however. If they were clever about this, they could offer all sorts of incentives: such as credits for uploading lots of data to other subscribers.. they'd certainly cut their costs!