you cant use (only) a quantum communication channel to communicate, because you cant control what values are sent. they're random. you have to use a classical communication channel together with it. the data sent through quantum entanglement is meaningless until you compare it to data sent via the classical channel.
so there is no speed increase. you cant communicate faster than the speed of light.
i'm not sure it would use less energy, i think it would actually use more, because quantum communication can only work together with a classical communication channel.
you cant actually send information using the quantum channel, because you cant control it. you can only compare it to the classical channel. the quantum channel gives you random bits, and the classical channel tells you whether each bit is correct or the opposite of what it should be.
firebug shows the generated source, not the original source. so, for example, if javascript changed something on the page, those changes would be in the generated source but not the original source.
i do use DOM inspector constantly, but there are certain things it wont help with (e.g. debugging certain HTML typos). i havent used View Selection Source, but i suspect it generates the source from the current DOM rather than displaying the original source, which means it would have the same problems as the DOM inspector.
I disagree, viewing source is very important, and if it's dynamically created content and it has to reload the page, the source you're viewing may not be the same source that created the page. It's essential for debugging (e.g. HTML typos). and for a POST request, reloading is absolutely unacceptable.
we can tell that other objects are moving away from us because of the Doppler redshift of light coming too us. the further the object is from us, the greater the redshift, meaning that the further the object the faster it's moving away from us.
really? i have a Gigabit network with a NAS and it seems to be just as fast as local drives (both are 7200 SATA 2). they both max out around 50MB/s. unless you have faster hard drives, I think the bottleneck on a gigabit NAS would be the hard drives and not the network.
if the ad is served via a tag (most are), the browser wont load anything after the tag until it downloads the javascript file. if the server hosting the ad is slow, it slows down the webpage with the ad on it.
ad servers are usually pretty fast, but when they slow down it's very noticeable.
TPB will have to change their end first. currently, the site redirects you to http://thepiratebay.org/ if you go to their site without thepiratebay.org in the host, e.g. : http://83.140.176.146
you'll have to put thepiratebay.org in your hosts file until they change it.
these are mostly just changes to applications in the "official gnome apps" list, and new apps added to that list. they're not really going to affect the performance of the desktop itself (i.e. gnome-panel, nautilus, metacity, etc).
aka, $150 upconverting DVD player. slightly overpriced, but considering it comes with 9* free HD movies, i'm happy. and yes, i bought it this week knowing full well HDDVD is probably going to lose.
* 2 you pick from the shelf, 2 in the box, 5 you choose from a small list and mail away for
I think it's more a case of Opera being pissed that it's not funded with Google money like Mozilla Firefox is.
they are, actually. they're funded for adding them in the search engines at the top right, same with firefox. this was mentioned in a mag article i read a few months ago, but i cant remember the mag.
here's a good intro. this assumes you have a file time.asp on your site that just outputs the time.
if, instead, time.asp outputs an XML file, in the code change.responseText to.responseXML, and from that you can use DOM functions (e.g. xmlHttp.responseXML.getElementsByTagName("time")[0].childNodes[0].nodeValue.
How else would you like people to make clickable text that executes a JavaScript method, and how would it be better than that approach?
use the onclick attribute, with return false at the end to cancel the href. that way, you can use the href for a URL to degrade gracefully. for example, if it's opening a popup window, have the href be the URL of the page that loads in the popup.
i was thinking the same thing. there's all of about 5-10 methods/properties to learn, and then you just need to know basic DOM functions for the response. it's not hard at all.
not if everything, including the URL you typed, was over HTTPS (and the SSL certificate matched up). they couldnt do anything to a request over HTTPS, except corrupt it.
if, however, you type in http://www.google.com/ and that site is supposed to redirect you to https://www.google.com/ they could change that first HTTP page to have a frameset and put their ads in.
Slashdot Mirror
you cant use (only) a quantum communication channel to communicate, because you cant control what values are sent. they're random. you have to use a classical communication channel together with it. the data sent through quantum entanglement is meaningless until you compare it to data sent via the classical channel.
so there is no speed increase. you cant communicate faster than the speed of light.
i'm not sure it would use less energy, i think it would actually use more, because quantum communication can only work together with a classical communication channel.
you cant actually send information using the quantum channel, because you cant control it. you can only compare it to the classical channel. the quantum channel gives you random bits, and the classical channel tells you whether each bit is correct or the opposite of what it should be.
it's actually available, apparently, but i'm pretty sure it's ridiculously priced. it's certainly not targeted at the average consumer.
i've been anxiously waiting for news of a consumer-level product for 2 years now. alas, still not in sight.
firebug shows the generated source, not the original source. so, for example, if javascript changed something on the page, those changes would be in the generated source but not the original source.
i do use DOM inspector constantly, but there are certain things it wont help with (e.g. debugging certain HTML typos). i havent used View Selection Source, but i suspect it generates the source from the current DOM rather than displaying the original source, which means it would have the same problems as the DOM inspector.
I disagree, viewing source is very important, and if it's dynamically created content and it has to reload the page, the source you're viewing may not be the same source that created the page. It's essential for debugging (e.g. HTML typos). and for a POST request, reloading is absolutely unacceptable.
the test is here.
i'm getting a 50/100 in Firefox.
really? i have a Gigabit network with a NAS and it seems to be just as fast as local drives (both are 7200 SATA 2). they both max out around 50MB/s. unless you have faster hard drives, I think the bottleneck on a gigabit NAS would be the hard drives and not the network.
if the ad is served via a tag (most are), the browser wont load anything after the tag until it downloads the javascript file. if the server hosting the ad is slow, it slows down the webpage with the ad on it.
ad servers are usually pretty fast, but when they slow down it's very noticeable.
the watermarking could be built into the compression algorithm, or added after the algorithm runs.
i imagine it might even be easier to watermark lossy formats, since imperfections (and anomalies) in the final product wouldn't arouse suspicion.
i'd suggest finding some way, hardware or software, to throttle your own upload speed just south of where it starts crapping out.
TPB will have to change their end first. currently, the site redirects you to http://thepiratebay.org/ if you go to their site without thepiratebay.org in the host, e.g. : http://83.140.176.146
you'll have to put thepiratebay.org in your hosts file until they change it.
these are mostly just changes to applications in the "official gnome apps" list, and new apps added to that list. they're not really going to affect the performance of the desktop itself (i.e. gnome-panel, nautilus, metacity, etc).
* 2 you pick from the shelf, 2 in the box, 5 you choose from a small list and mail away for
it's because the end-user is supposed to decide whether or not to open a link in a new window/tab, not the site.
make it 5, and i agree. it'd easily, easily be my #1 of the year, followed by COD4.
here's a good intro. this assumes you have a file time.asp on your site that just outputs the time.
.responseText to .responseXML, and from that you can use DOM functions (e.g. xmlHttp.responseXML.getElementsByTagName("time")[0].childNodes[0].nodeValue.
if, instead, time.asp outputs an XML file, in the code change
i was thinking the same thing. there's all of about 5-10 methods/properties to learn, and then you just need to know basic DOM functions for the response. it's not hard at all.
not if everything, including the URL you typed, was over HTTPS (and the SSL certificate matched up). they couldnt do anything to a request over HTTPS, except corrupt it.
if, however, you type in http://www.google.com/ and that site is supposed to redirect you to https://www.google.com/ they could change that first HTTP page to have a frameset and put their ads in.
this happens so often that even Wikipedia's entry for EMCA redirects to ECMA.
it takes me 10 seconds to create it myself.