It is often about keeping employees 'in'; logging where they go, restricting what services they use, etc. Not every wall is to keep people out. Many places I have seen put far more effort into keeping the employees 'in-line' then blocking outside threats.
It isn't about money; AFAIK, Nikon doesn't even charge. It is about control. Adobe (and me, for that matter) want to process the files with their own algorithms. For Adobe, this adds value to their product. For the users, it gives more options in processing the files, with possibly better output. Nikon wants all the files processed their way (via their SDK) and are trying to make it difficult to do otherwise. Using the Nikon SDK is *not* the same as processing the RAW file yourself.
You would think so, wouldn't you? But camera manufacturers (esp Canon and Nikon) are very traditional. They never admit there is anything wrong with their camera's and go a long ways out of their way (especially Canon) to stop people from making compatible items. They treat software like a lens mount; the more propietary, the better. If they had been able to lock you into propietary film, they would have. They seen an oppurtunity to do that (after a fashion) with raw formats.
I would like to see reviewers get out there and strong critize any manufacturer who does not support an open raw format.
Firewall is ON by default. If you're going to turn it OFF, Windows warns you. Windows can't stop you from making your computer insecure if you want to. You could just as well make a Remote Desktop account with Admin priveleges and no password.
What a load of BS. There is *NO* excuse for vulnerability to this. "Making your computer insecure"???? No, Microsoft made my computer insecure; my only foolishness was installing windows. A firewall is an additional protection device, not the primary one. Still being vulnerable to age-old attacks is simply irresponsible.
8 years is hardly enough to figure out how to patch windows.
Besides, like all everyone here says, it is the users own fault for not using a firewall. Having an expectation that 8 yr old attacks should be fixed is just unreasonable.
Dude, that is so damn funny. The fact that there are essentially no responses just tells me that very few here have read his complete works and gets the joke.
He remains one of my favorite authors, but really can't write an ending worth a damn.
In many cases in Canada (and probably elsewhere), it comes down to distribution agreements. For example, Amazon may have a distribution agreement with Sony for the US, but does not hold it in Canada. In return for being an authorized dealer, they agree to not sell outside of their area. This is to prevent pissing off their Canadian distributors and to help support some price differences (sometimes in favour of Canada!)
"Eventually, they'll sort it out, but there is value to the attackers in how long that will take. If the Pentagon releases a nice, color-coded map of exactly where they dropped the bombs (they do know exactly what was hit, what with precision armaments), it *will* help the enemy du jour."
Although true, I wasn't commenting on such precision; more general information. We don't necessarily need to know exactly what happened. Naturally, war's go better if nothing is disclosed. However, the government is acting on behalf of its people and must inform them to a reasonable extent what actions it is taking on their behalf, particularly when those actions involve killing others. Withholding information many hours after the fact serves the governments PR interest much more then it serves a military purpose, even if there is some marginal military gain.
Is everyone forgetting that a part of the price of freedom is safety? An open society is a vulnerable society in some ways. The same vulnerability keeps society safe from itself and its own excesses.
Of course if we classified everything like this no one would have a road map to destruction. But they could still poison the water supply, blow up buildings and cause untold grief. They could still locate some of the bottlenecks themselves and exploit them.
Like so many things the government/corporations seek to classify, the real people they don't want to know are the ordinary people. It puts me in mind of the many "the area bombed last night is classified...we don't want to give the enemy important information" remarks we see. Like the enemy doesn't know they were bombed...
Sure if you have access to the source and the time/money/skill to do your own review/testing, you can do a lot better then FIPS. But what if you just want to buy a $5000 box? It would seem to me that at least you have _some_ assurance; it might not be perfect, but it is better then none.
Really, the biggest problem with FIPS is the boundries it is drawn at. Typically only some (crypto) modules are certified; there may be gaping holes in other modules. So your crypto might be bullet proof, but someone may still be able to hack the box and sniff off any data they want
My multimedia machine in my living room runs off 802.11b with a music server in another section of the house. When my 2.4 GHz phone rings, the music pauses nice and automatically (well after the buffer runs out). Its a great feature!
Seriously, webcams, phones, baby monitors all can clobber 802.11b pretty badly. I can't wait for affordable dual mode so I can put the multmedia machine at least in the 5 Ghz range. Home users with lots of tech toys are going to be much happier with 802.11a. 802.11g will do nothing for them.
"And software distributed for free would still be required under UCITA to carry a warranty if there's a charge for installation services or an accompanying maintenance contract."
You take money to install/maintain it, you provide a warrantee. I like the sound of that; otherwise you could be any old chump just taking peoples money.
Note also that:
"the new UCITA would exempt from warranty an Open Source product that was sold for the cost of the media it was on, such as a $3 Linux CD set."
Which again makes perfect sense. Where it gets hazy is when 'free' software is sold for a cost above media but obviously below the amount required for maintenance; this will be a tough thing to iron out.
Well, that is true to an extent. But the PC offers much more. I have a PVR machine set up and big-deal; record TV programs on a very overpriced Tivo. BUT I also have complete access to my audio streaming server with a web interface with my entire CD collection available (and soon adding mixes...) at the touch of a button. And 192 kb/s MP3 is pretty decent. Not to mention web access which can be fun, even with company (look up movies, trivia, etc). And all hooked up via HDTV connection. Eventually it will be hooked up to home automation.
Sure a PC PVR is overpriced (and a bit of a pain) but the potential is much better; it just needs to be realized with more turn-key software.
Now if the damn thing wasn't so noisy and stopped heating the room....
Reliable-syslog, from the syslog WG in the IETF, is based on BEEP. It is fairly clever.
In reviewing reliable-syslog, I had a good look at BEEP. It is clever and neat, but XML processing _can_ be a bit heavy for many applications and there can be quite a few options in BEEP. That being said, it is still feasible. It takes quite a long while for a new 'protocol' to gain acceptence; often years.
Not kidding...I think you just might have read my post backwards from the indended point. I was saying William Paley does exist and the "Theobiologist" Richard Paley is an obvious rip-off.
I recently set one up using: - ATI 8500 DV (yes, much more expensive) - Athlon 650 - 384 Mb RAM - 2x60 GB drive - Wireless KB, mouse, remove, 802.11b
I am surprised at his playback problems. The ATI easily plays back anything on my [much more] modest machine. Recording is a slightly diff issue. I can do "good" at about 90% CPU, anything more and the machine cannot keep up.
ATI's "multimedia center" is, IMO, crap in terms of quality and -- in some ways -- features. Really important things like 30-second skip isn't present on playback. It tends to crash with alarming regularity. The on-line guide is nice, though. But you can't schedule anything to be recorded from S-Video (or composite) because of a but which makes it all scheduled programs revert to the tuner, so no digital cable recordings for me. The library function is very marginally useful. The remote has very limited programming for other apps (like WinAmp). It is hooked up to a 53" wide-screen HDTV-capable; the quality is surprising good considering the very demanding display. Dual-head sort of works, but never does the bits you want to (i.e. desktop on one, TV playback on the other) but this is supposed to be "coming".
All-in-all, good hardware, software needs a _lot_ of work. Same old story for ATI. Hopefully someone will come out with much better software; ATI has been working on the mult-media center for years so I don't hold out much hope for it. I would like highly functional software with command-line options so I could script togather the wierd stuff. Is that too much to ask?
I haven't tried the 80 gig drives but I use a 1 gig microdrive with a firewire dongle regularly on 2.4.something. It doesn't work great. While transferring a lot of files, the computer becomes quite unresponsive (it seems to spend a lot of the time in the kernel). Finishing up the last file often takes a very long time, all the while the computer often appears frozen. It does freeze occasionally (only when using firewire).
In addition, unmounting/remounting only works sometimes. Often I have to unload the modules and reload them. Based on my experience, I would say mass-storage on firewire on Linux isn't ready for prime-time yet. YMMV.
Slashdot Mirror
It is often about keeping employees 'in'; logging where they go, restricting what services they use, etc. Not every wall is to keep people out. Many places I have seen put far more effort into keeping the employees 'in-line' then blocking outside threats.
Since when was Google's offering in this field highly hyped? Or hyped much at all? Have you been reading slashdot again?
a pack of tiny cigs like that?
Macrovision is a business, not a charity. If they can see a way to provide an exclusive service, they will certainly do so.
Sorry, it has to be posted.
s .html
http://www.usd.edu/~bwjames/humor/ms/microsoftcar
It isn't about money; AFAIK, Nikon doesn't even charge. It is about control. Adobe (and me, for that matter) want to process the files with their own algorithms. For Adobe, this adds value to their product. For the users, it gives more options in processing the files, with possibly better output. Nikon wants all the files processed their way (via their SDK) and are trying to make it difficult to do otherwise. Using the Nikon SDK is *not* the same as processing the RAW file yourself.
You would think so, wouldn't you? But camera manufacturers (esp Canon and Nikon) are very traditional. They never admit there is anything wrong with their camera's and go a long ways out of their way (especially Canon) to stop people from making compatible items. They treat software like a lens mount; the more propietary, the better. If they had been able to lock you into propietary film, they would have. They seen an oppurtunity to do that (after a fashion) with raw formats.
I would like to see reviewers get out there and strong critize any manufacturer who does not support an open raw format.
run on the OS, the OS runs on the Cell phone.
Try to get the whole hardware/software thing sorted; it sounds a lot more credible.
Firewall is ON by default. If you're going to turn it OFF, Windows warns you. Windows can't stop you from making your computer insecure if you want to. You could just as well make a Remote Desktop account with Admin priveleges and no password. What a load of BS. There is *NO* excuse for vulnerability to this. "Making your computer insecure"???? No, Microsoft made my computer insecure; my only foolishness was installing windows. A firewall is an additional protection device, not the primary one. Still being vulnerable to age-old attacks is simply irresponsible.
8 years is hardly enough to figure out how to patch windows.
Besides, like all everyone here says, it is the users own fault for not using a firewall. Having an expectation that 8 yr old attacks should be fixed is just unreasonable.
WTF, are you all on crack?
Dude, that is so damn funny. The fact that there are essentially no responses just tells me that very few here have read his complete works and gets the joke.
He remains one of my favorite authors, but really can't write an ending worth a damn.
In many cases in Canada (and probably elsewhere), it comes down to distribution agreements. For example, Amazon may have a distribution agreement with Sony for the US, but does not hold it in Canada. In return for being an authorized dealer, they agree to not sell outside of their area. This is to prevent pissing off their Canadian distributors and to help support some price differences (sometimes in favour of Canada!)
"Eventually, they'll sort it out, but there is value to the attackers in how long that will take. If the Pentagon releases a nice, color-coded map of exactly where they dropped the bombs (they do know exactly what was hit, what with precision armaments), it *will* help the enemy du jour."
Although true, I wasn't commenting on such precision; more general information. We don't necessarily need to know exactly what happened. Naturally, war's go better if nothing is disclosed. However, the government is acting on behalf of its people and must inform them to a reasonable extent what actions it is taking on their behalf, particularly when those actions involve killing others. Withholding information many hours after the fact serves the governments PR interest much more then it serves a military purpose, even if there is some marginal military gain.
Is everyone forgetting that a part of the price of freedom is safety? An open society is a vulnerable society in some ways. The same vulnerability keeps society safe from itself and its own excesses.
Of course if we classified everything like this no one would have a road map to destruction. But they could still poison the water supply, blow up buildings and cause untold grief. They could still locate some of the bottlenecks themselves and exploit them.
Like so many things the government/corporations seek to classify, the real people they don't want to know are the ordinary people. It puts me in mind of the many "the area bombed last night is classified...we don't want to give the enemy important information" remarks we see. Like the enemy doesn't know they were bombed...
The military will have the ability to shut down any wireless network by a simple transmission.
Sweet. For them anyway....
Sure if you have access to the source and the time/money/skill to do your own review/testing, you can do a lot better then FIPS. But what if you just want to buy a $5000 box? It would seem to me that at least you have _some_ assurance; it might not be perfect, but it is better then none.
Really, the biggest problem with FIPS is the boundries it is drawn at. Typically only some (crypto) modules are certified; there may be gaping holes in other modules. So your crypto might be bullet proof, but someone may still be able to hack the box and sniff off any data they want
My multimedia machine in my living room runs off 802.11b with a music server in another section of the house. When my 2.4 GHz phone rings, the music pauses nice and automatically (well after the buffer runs out). Its a great feature!
Seriously, webcams, phones, baby monitors all can clobber 802.11b pretty badly. I can't wait for affordable dual mode so I can put the multmedia machine at least in the 5 Ghz range. Home users with lots of tech toys are going to be much happier with 802.11a. 802.11g will do nothing for them.
...in particular:
"And software distributed for free would still be required under UCITA to carry a warranty if there's a charge for installation services or an accompanying maintenance contract."
You take money to install/maintain it, you provide a warrantee. I like the sound of that; otherwise you could be any old chump just taking peoples money.
Note also that:
"the new UCITA would exempt from warranty an Open Source product that was sold for the cost of the media it was on, such as a $3 Linux CD set."
Which again makes perfect sense. Where it gets hazy is when 'free' software is sold for a cost above media but obviously below the amount required for maintenance; this will be a tough thing to iron out.
Well, that is true to an extent. But the PC offers much more. I have a PVR machine set up and big-deal; record TV programs on a very overpriced Tivo. BUT I also have complete access to my audio streaming server with a web interface with my entire CD collection available (and soon adding mixes...) at the touch of a button. And 192 kb/s MP3 is pretty decent. Not to mention web access which can be fun, even with company (look up movies, trivia, etc). And all hooked up via HDTV connection. Eventually it will be hooked up to home automation.
Sure a PC PVR is overpriced (and a bit of a pain) but the potential is much better; it just needs to be realized with more turn-key software.
Now if the damn thing wasn't so noisy and stopped heating the room....
Reliable-syslog, from the syslog WG in the IETF, is based on BEEP. It is fairly clever.
In reviewing reliable-syslog, I had a good look at BEEP. It is clever and neat, but XML processing _can_ be a bit heavy for many applications and there can be quite a few options in BEEP. That being said, it is still feasible. It takes quite a long while for a new 'protocol' to gain acceptence; often years.
Whoa, the cover of the Quantum Rose looks like some cheesy romance novel.
http://www.sff.net/people/asaro/quantumrose.htp
Note for romance lovers: Get some taste. Oops, no, I meant it looks like the bad romance novels, as opposed to the, er, good ones.
Not kidding...I think you just might have read my post backwards from the indended point. I was saying William Paley does exist and the "Theobiologist" Richard Paley is an obvious rip-off.
Best indication its a hoax:
In 1802 a William Paley (you do get the name connection, right?) wrote a book entitled "Natural Theology"
This is too much concidence to be real.
I recently set one up using:
- ATI 8500 DV (yes, much more expensive)
- Athlon 650
- 384 Mb RAM
- 2x60 GB drive
- Wireless KB, mouse, remove, 802.11b
I am surprised at his playback problems. The ATI easily plays back anything on my [much more] modest machine. Recording is a slightly diff issue. I can do "good" at about 90% CPU, anything more and the machine cannot keep up.
ATI's "multimedia center" is, IMO, crap in terms of quality and -- in some ways -- features. Really important things like 30-second skip isn't present on playback. It tends to crash with alarming regularity. The on-line guide is nice, though. But you can't schedule anything to be recorded from S-Video (or composite) because of a but which makes it all scheduled programs revert to the tuner, so no digital cable recordings for me. The library function is very marginally useful. The remote has very limited programming for other apps (like WinAmp). It is hooked up to a 53" wide-screen HDTV-capable; the quality is surprising good considering the very demanding display. Dual-head sort of works, but never does the bits you want to (i.e. desktop on one, TV playback on the other) but this is supposed to be "coming".
All-in-all, good hardware, software needs a _lot_ of work. Same old story for ATI. Hopefully someone will come out with much better software; ATI has been working on the mult-media center for years so I don't hold out much hope for it. I would like highly functional software with command-line options so I could script togather the wierd stuff. Is that too much to ask?
I haven't tried the 80 gig drives but I use a 1 gig microdrive with a firewire dongle regularly on 2.4.something. It doesn't work great. While transferring a lot of files, the computer becomes quite unresponsive (it seems to spend a lot of the time in the kernel). Finishing up the last file often takes a very long time, all the while the computer often appears frozen. It does freeze occasionally (only when using firewire).
In addition, unmounting/remounting only works sometimes. Often I have to unload the modules and reload them. Based on my experience, I would say mass-storage on firewire on Linux isn't ready for prime-time yet. YMMV.