Something I think your approach overlooks is purchasing stuff on-line. I get two types of automated response from an online vendor:
1. An order confirmation with an order ID or other follow-up options.
2. A password or registration number that allows me to unlock trial software.
Won't your CRS keep me from getting these, since the follow ups are auto-generated, and don't reply to challenges?
I guess I could add the vendor to my white-list, but I'd need to add the vendor quickly enough so that the one confirmation/password E-Mail isn't rejected. That seems like a tough thing to do. Furthermore, I'd have to get the vendor's white-list entry correct, which is made more difficult by the fact that many on-line vendors use a third party to handle the money transaction/confirmation step.
And lastly, even if I was successful in getting the vendor in my white-list quickly enough, to truly protect against further unwanted E-mails from that vendor (new product offers, or whatever), I'd have to remove them from my white-list again.
Anyway, sounds like the simple CRS approach would need some additional refinements if one makes any on-line purchases.
Read the article. The thing doesn't use a lens. It works by direct refraction of a laser through a hologram.
However, I'll be interested in the quality anyway... The article goes on to say that coming up with the hologram in real-time is accomplished by minimizing noise variance, and not noise. My guess though is that initial units will be "good enough". After that, incremental improvement of the technology should bring the quality up to HDTV levels.
How long before nonvolatile memory becomes the solution to crash-prone software rather than better programming?
Errr.... Wouldn't non-volatile memory make life harder when programs crash? Say Windows wipes out on a computer with MRAM. Turning the machine off and then back on wouldn't erase the crashed image in memory, and you'd restore right back to the crashed state. Sounds like software (well, OS and drivers anyway) would have to be much more robust than they are today.
Slashdot Mirror
Something I think your approach overlooks is purchasing stuff on-line. I get two types of automated response from an online vendor:
1. An order confirmation with an order ID or other follow-up options.
2. A password or registration number that allows me to unlock trial software.
Won't your CRS keep me from getting these, since the follow ups are auto-generated, and don't reply to challenges?
I guess I could add the vendor to my white-list, but I'd need to add the vendor quickly enough so that the one confirmation/password E-Mail isn't rejected. That seems like a tough thing to do. Furthermore, I'd have to get the vendor's white-list entry correct, which is made more difficult by the fact that many on-line vendors use a third party to handle the money transaction/confirmation step.
And lastly, even if I was successful in getting the vendor in my white-list quickly enough, to truly protect against further unwanted E-mails from that vendor (new product offers, or whatever), I'd have to remove them from my white-list again.
Anyway, sounds like the simple CRS approach would need some additional refinements if one makes any on-line purchases.
Just some thoughts.
P.
~~~~~~~~
Read the article. The thing doesn't use a lens. It works by direct refraction of a laser through a hologram.
However, I'll be interested in the quality anyway... The article goes on to say that coming up with the hologram in real-time is accomplished by minimizing noise variance, and not noise. My guess though is that initial units will be "good enough". After that, incremental improvement of the technology should bring the quality up to HDTV levels.
P.
~~~~~~~~~~~~
How long before nonvolatile memory becomes the solution to crash-prone software rather than better programming?
Errr.... Wouldn't non-volatile memory make life harder when programs crash? Say Windows wipes out on a computer with MRAM. Turning the machine off and then back on wouldn't erase the crashed image in memory, and you'd restore right back to the crashed state. Sounds like software (well, OS and drivers anyway) would have to be much more robust than they are today.
P.