I would strongly suggest you either ideally do as others have suggested and put in ducting that means you can pull more cables later, or, if for some reason you can't, put in both fibre and cat5e - even if you only initially use the cat5, you've still got the fibre there for later, as running new cables without ducting will cost a fortune (in the redecorating costs if nothing else!)
The tricky bit about the whole thing is software, while there are lots of good individual bits and pieces for the various functions you probably want (MythTV for example), there isn't anything (AFAIK anyway) that lets you manage all these things centrally - if you want the house to be really clever, then having everything coordinated by one system is what you want...
think about how much damage even a small chip of paint can do at orbital speeds (low Earth orbit = approx. 5 miles per second). Then think of a 2 lb. chunk of metal at the same speed (8 times the speed of a rifle bullet). That's fine, apart from the fact that anything it would collide with would also be moving at a comparable speed, so the relative speed would be much much less, so while yes there could quite easily be an impact that could cause some damage to a spacecraft, it wouldn't be an impact at 8 times the speed of a rifle bullet...
A sensor on one of the wings registered a very small possible impact, below the level they are normally worried about. To be safe, they added an extra inspection of the wing using one of the robotic arms (I can't remember whether it was the shuttles or the stations) - this showed nothing so the shuttle was cleared to return, they didn't have to fix anything...
The extra space walk was to fix one of the space station solar array wings which hadn't retracted like it was supposed to, nothing to do with the shuttle at all!
I'm not sure about the weather, but I believe it could still have landed OK on Saturday, it was after that they would have fuel problems...
For those that haven't read the actual proposed court order, all the way through it talks about blocking www.spamhaus.org - well fine, block the www. bit, but that means the sbl/rbl will be fine since that doesn't use www. anywhere.
Before people try and state the obvious that ICANN can't specifically block the www. bit alone, they can only block the entire spamhaus.org domain, I would have thought that since it's presumably not ICANN's place to do *more* than the court order says, they simply can't comply with it for technical reasons...
Why wouldn't they want to embrace safety technology like this?
The most obvious reason is cost. If a company hasn't been hit by an accident in the past, then if (like a lot of companies) they're purely looking at their bottom line, why would they pay more for this saw than the one they've already got...
I don't know if this is the case or not, but if AOL's anything like Google, they may also use a cookie to track you, so just using something like Torpark won't help, you also need to disable cookies...
The tricky bit about the whole thing is software, while there are lots of good individual bits and pieces for the various functions you probably want (MythTV for example), there isn't anything (AFAIK anyway) that lets you manage all these things centrally - if you want the house to be really clever, then having everything coordinated by one system is what you want...
Very good point, I hadn't thought of that...
A sensor on one of the wings registered a very small possible impact, below the level they are normally worried about. To be safe, they added an extra inspection of the wing using one of the robotic arms (I can't remember whether it was the shuttles or the stations) - this showed nothing so the shuttle was cleared to return, they didn't have to fix anything...
The extra space walk was to fix one of the space station solar array wings which hadn't retracted like it was supposed to, nothing to do with the shuttle at all!
I'm not sure about the weather, but I believe it could still have landed OK on Saturday, it was after that they would have fuel problems...
For those that haven't read the actual proposed court order, all the way through it talks about blocking www.spamhaus.org - well fine, block the www. bit, but that means the sbl/rbl will be fine since that doesn't use www. anywhere.
Before people try and state the obvious that ICANN can't specifically block the www. bit alone, they can only block the entire spamhaus.org domain, I would have thought that since it's presumably not ICANN's place to do *more* than the court order says, they simply can't comply with it for technical reasons...
Why wouldn't they want to embrace safety technology like this?
The most obvious reason is cost. If a company hasn't been hit by an accident in the past, then if (like a lot of companies) they're purely looking at their bottom line, why would they pay more for this saw than the one they've already got...
I don't know if this is the case or not, but if AOL's anything like Google, they may also use a cookie to track you, so just using something like Torpark won't help, you also need to disable cookies...