Multiplay (huge UK lan party) gets by with a badge and stickers on your equipment with your name and an id number on. And a little security at the door to enforce it of course.
So we're not going to really be able to visit Martian websites then:( Technically HTTP doesn't have to be over TCP, but regardless you're not going to get a reply sooner than the RTT to Mars without faking it with a local cache (and having an expires time on the page of more than the RTT to Mars) or using dns trickery to direct requests to uni.mars to a local server on the same planet as them.
Incidentally, anyone know if the http "Expires:" in x seconds header is measured from the time the request is sent, the response is sent or the time the response is received? Normally latency is low enough for this not to matter, but in cases like this...
And not forgetting the fact that biological neural nets grow and strengthen and "learn" in ways that we have no idea about. The links in artificial neural nets are often fixed (just with variable weights), and the learning process is either manual/automatic adjustment of the link weights from outside or evolution. We have no way of making an artificial neural net "learn" like a biological one yet.
What about the fact that different cards give different results for texture filtering? Specifically their choice of mip level and anisotropic filtering. Think circle vs square differences.
Hell, some cards implement anti-aliasing differently to others.
The closest we can get to that is with HTTP/1.1, using HTTP Pipelining which needs two requests: Request page, using HTTP/1.1 with "Connection: keep-alive" header. Receive response, hopefully a "HTTP/1.1 200 OK" with another "Connection: keep-alive" header. Request all the images etc on the page one after the other in the same connection, without pausing for responses. Receive all the responses.
With suitably set cache headers to allow local caches to serve the page without the delay.
The only way to improve this is to add an additional response type, e.g. "HTTP/1.1 210 Additional", which the server would use (along with the "Location:" header) to give additional responses that it thinks the client needs or will need without them being requested. i.e.: Client: (on earth) GET / HTTP/1.1 Host: uni.mars Connection: keep-alive
Server: (on mars) HTTP/1.1 200 OK Connection: keep-alive
IPv6 addresses don't have to be excessively long, I have: 2001:XXXX:XXXX::1 (obviously the Xs aren't really the address, but giving an address on a lowly home internet connection on slashdot seems like a bad idea) Autoconfig defaults to adding the link's mac address to that as well (with FF:FE in the middle), so I also have a longer (almost max IPv6 length) address for the same connection.
We're not talking about BBC News, we're talking about BBC iPlayer. It's a site of theirs for watching online anything that was broadcast on BBC TV in the last week.
It's not the cows you should be worried about, it's the TREES! They're plotting against us I tell you! Every day they invade further into our cities. They've clearly already got to the planning councils. Have they got the government yet? I don't know.
"Profitable for apple" could mean that they aren't making a profit on the warranty and repairs themselves, but they cover the costs easily in the profit of the pc and the customer is so happy they buy more apple stuff later.
"Not losing your customers to the competition" can have a value too. It's a bit too indirect for most modern companies unfortunately, they seem to instead prefer to give all sorts of incentives to new customers and allow their existing customers to be drawn away by their competitors' new customer incentives. "We'll treat you like crap when you try to claim on the warranty, to make sure you never buy from us again!"
If one fails with probability p, and you have n of them, a total system failure is probability p^n, not 1-p^n. Well technically it's Mult(p,1->n) where p1 is the probability of the first failing, p2 the probability of the second, etc, multiplying them all together to get the chance of a total system failure. The probability of any one device in a redundant system failing is (1-((1-p)^n)). This equation rapidly approaches 1, so in larger setups failures will be a common occurrence, but they'll largely be harmless due to redundancy.
Of course this all assumes the failure mode of the device is "off" or "non-functioning". If it fails in a way which routes 15A of mains power into a network cable, redundancy might not help a whole lot.
Obviously that's not what happened, but it's not outside possibility for one device to take down an entire redundant system.
Quantum computing is statistical, it doesn't really have states at all. A quantum bit (qbit) has an X% chance of being 1 and Y% chance of being 0. Depending on the value of X, the bit could be a guaranteed 1 or 0, or could be randomly one or the other.
Even more confusingly, the probability of a quantum bit is actually a squared complex number, with the complex number (unsquared) being used in calculations. The (squared) numbers have to total 1.0, but the unsquared numbers can have negative terms. This doesn't have any effect normally, but makes some really interesting things happen when you operate on qbits, such as a quantum gate which will make a qbit's probability 0.5:0.5 (perfectly random) on first use and change it back to its original value on the second use (unrandomising it).
It's also F11 in firefox. I gives you a minimalistic address and toolbar, which auto-hides, leaving all but a few lines of pixels of your screen for rendering the page.
Slashdot Mirror
Multiplay (huge UK lan party) gets by with a badge and stickers on your equipment with your name and an id number on. And a little security at the door to enforce it of course.
So we're not going to really be able to visit Martian websites then :(
Technically HTTP doesn't have to be over TCP, but regardless you're not going to get a reply sooner than the RTT to Mars without faking it with a local cache (and having an expires time on the page of more than the RTT to Mars) or using dns trickery to direct requests to uni.mars to a local server on the same planet as them.
Incidentally, anyone know if the http "Expires:" in x seconds header is measured from the time the request is sent, the response is sent or the time the response is received? Normally latency is low enough for this not to matter, but in cases like this...
It's largely wrong that animals all see in black and white.
A lot of mammals can see light intensity and two colours. This probably includes dogs.
And not forgetting the fact that biological neural nets grow and strengthen and "learn" in ways that we have no idea about. The links in artificial neural nets are often fixed (just with variable weights), and the learning process is either manual/automatic adjustment of the link weights from outside or evolution. We have no way of making an artificial neural net "learn" like a biological one yet.
What about the fact that different cards give different results for texture filtering? Specifically their choice of mip level and anisotropic filtering. Think circle vs square differences.
Hell, some cards implement anti-aliasing differently to others.
Actually you can add it as a protocol through the properties of the network connection.
The closest we can get to that is with HTTP/1.1, using HTTP Pipelining which needs two requests:
Request page, using HTTP/1.1 with "Connection: keep-alive" header.
Receive response, hopefully a "HTTP/1.1 200 OK" with another "Connection: keep-alive" header.
Request all the images etc on the page one after the other in the same connection, without pausing for responses.
Receive all the responses.
With suitably set cache headers to allow local caches to serve the page without the delay.
The only way to improve this is to add an additional response type, e.g. "HTTP/1.1 210 Additional", which the server would use (along with the "Location:" header) to give additional responses that it thinks the client needs or will need without them being requested.
i.e.:
Client: (on earth)
GET / HTTP/1.1
Host: uni.mars
Connection: keep-alive
Server: (on mars)
HTTP/1.1 200 OK
Connection: keep-alive
--Data of index.html--
HTTP/1.1 210 Additional /style.css
Connection: keep-alive
Location:
--Data of style.css--
HTTP/1.1 210 Additional /logo.png
Connection: keep-alive
Location:
--Data of logo.png--
etc.
IPv6 addresses don't have to be excessively long, I have: 2001:XXXX:XXXX::1 (obviously the Xs aren't really the address, but giving an address on a lowly home internet connection on slashdot seems like a bad idea)
Autoconfig defaults to adding the link's mac address to that as well (with FF:FE in the middle), so I also have a longer (almost max IPv6 length) address for the same connection.
We're not talking about BBC News, we're talking about BBC iPlayer. It's a site of theirs for watching online anything that was broadcast on BBC TV in the last week.
It's not the cows you should be worried about, it's the TREES!
They're plotting against us I tell you!
Every day they invade further into our cities. They've clearly already got to the planning councils. Have they got the government yet? I don't know.
I'll stay indoors, it's safer.
Oh, wait, I misunderstood you.
No you didn't, you just thought it would be funny to act like you did.
I don't care about the stories being US-centric (which is what the FAQ is about), but it would be nice to see US-centric articles marked as such.
Article should be titled "What *US* Tech Workers Need to Know About Overtime".
Very few stories on here are US-specific, and they should be labelled as such.
DirectPlay is deprecated.
"Profitable for apple" could mean that they aren't making a profit on the warranty and repairs themselves, but they cover the costs easily in the profit of the pc and the customer is so happy they buy more apple stuff later.
"Not losing your customers to the competition" can have a value too. It's a bit too indirect for most modern companies unfortunately, they seem to instead prefer to give all sorts of incentives to new customers and allow their existing customers to be drawn away by their competitors' new customer incentives. "We'll treat you like crap when you try to claim on the warranty, to make sure you never buy from us again!"
But that's not up to Futuremark to fix.
Of course the last two actually exist...
If one fails with probability p, and you have n of them, a total system failure is probability p^n, not 1-p^n. Well technically it's Mult(p,1->n) where p1 is the probability of the first failing, p2 the probability of the second, etc, multiplying them all together to get the chance of a total system failure.
The probability of any one device in a redundant system failing is (1-((1-p)^n)). This equation rapidly approaches 1, so in larger setups failures will be a common occurrence, but they'll largely be harmless due to redundancy.
Of course this all assumes the failure mode of the device is "off" or "non-functioning". If it fails in a way which routes 15A of mains power into a network cable, redundancy might not help a whole lot.
Obviously that's not what happened, but it's not outside possibility for one device to take down an entire redundant system.
Mod parent super informative.
HJKL does in fact work.
Though I wouldn't be surprised if it was 80mph for 30 miles or 30mph for 100 miles...
The real question is: "What's its range under normal motorway/town driving?"
Quantum computing is statistical, it doesn't really have states at all.
A quantum bit (qbit) has an X% chance of being 1 and Y% chance of being 0. Depending on the value of X, the bit could be a guaranteed 1 or 0, or could be randomly one or the other.
Even more confusingly, the probability of a quantum bit is actually a squared complex number, with the complex number (unsquared) being used in calculations. The (squared) numbers have to total 1.0, but the unsquared numbers can have negative terms. This doesn't have any effect normally, but makes some really interesting things happen when you operate on qbits, such as a quantum gate which will make a qbit's probability 0.5:0.5 (perfectly random) on first use and change it back to its original value on the second use (unrandomising it).
From the question:
I unfortunately must admit that I am not very skilled with programming.
Looks like you need to hire him.
It's also F11 in firefox. I gives you a minimalistic address and toolbar, which auto-hides, leaving all but a few lines of pixels of your screen for rendering the page.
IPv6 router: http://www.apple.com/airportextreme/specs.html
That just leaves ISP.
2. Update all clients to IPv6 capable systems (i.e., junk Windows)
Windows XP SP2 and Vista both support IPv6. Vista even has it on by default.
But you already knew that, and just wanted to bash MS again.