They also have to figure out how to deliver and store the hydrogen in the cars themselves. Hydrogen gas is incredibly unstable and in an accident, if the canister holing the gas ruptures, there will be an explosion. Currently, fuel cell vehicles, use technology that pulls hydrogen from ethanol (or some other similar compound including std 93 octane) but that is only marginally more efficient than burning it.
It is like fusion, they know how to get the reaction going but have yet to develop a way to feed it without killing the reaction.
Finally, it is about time that an auto manufacturer step up to the plate. Too bad it is not an american mfg.
Re:This can't be that big of a problem
on
Cheating at Seti@home
·
· Score: 3, Interesting
Fair enough on the corruption point. I understand however, the position of the admins who are near the end of the project and have very few resources left. Although the overwhelming support they have received from the public for their work is a blessing, it has been a curse too. The more users they got, the more money they had to spend to support them (although cost per user has probably gone down). I would not be surprised that the whole project is being run by Grad students right now and the university would probably lend support for any big catastrophes should they occur.
They are probably unable to cope at this point, so near the end, to deal with it real time. There is nothing to prevent them from going in later to adjust and obviously, any published work based on the project will have to deal with the issue.
As for the future, you have a point that the public at large may take exception with this and feel any future work is comprimised but people tend to have short memories.
I would imagine that the Seti@HomeII project will deal with this issue as they are going to need to distribute new software anyway. They could easily come up with a mechanism similar to that used by software publishers who tie their registration id to the hardware. This way the work units can't be transferred from machine to machine. I just can't see them pulling this off in the next few months.
I have not had seti running for 6 months and am currently in 95 percentile. Before that I was running it occasionaly on a PII 400 mHz NT4 machine. Anyhow, who cares??? I have better things to worry about than people who are in a race to be the first to not discover alien life...
The bluelight.com unit was apparently small and only had a 25 seat license. Since when does Mickeysoft send lawyers out to monitor the legal docs of the sale of a small business unit for license issues. Maybe they are actually interested in railroading bluelight.com for another reason...
What we really need to know is what technology they licensed from MS and why it is so important to them. What was Bluelight running on the backend of their webservers, etc?
Where do you propose the old ones go? At least with CRT the environmental nightmare is on a ~5 year life-cycle. With this it may be just as toxic (not to mention the mfg process used) but it would be on a much faster life-cycle.
Correction: The first two sentences should read:
That is possibly correct. Fonts (the files) themselves can be copyrighted but I do not know if the ones that ship with the OS are. Depending on the license, they may be limited to a particular OS.
I swear I previewed it twice and made corrections both times. I guess that should have made me preview it a third...
I am still hung over from stumbling around Cambridge last night. You have got to love the Cellar!
That is correct. Fonts (the files) themselves can be copyrighted but I not know if the ones that ship with the OS are. Just as an example, Adobe charges about $30 - $50 for recently released decorative fonts when purchased in individual packs. They get $8,999 (yes, that's right) for 2,750 ($3.27 per) fonts if you buy them in bulk.
Imangine what the printing houses that publishers use to print their stuff have to pay for all of those fonts. Adobe is not the only one people use and the printing house has to have their own copy for their presses.
This just in. Foxes have asks chicken farmers to place stronger locks on hen house doors to prevent aberant foxes from getting into the coop and swiping a meal. Farmers are currently reviewing the proposal which includes protections for foxes who belong to hunting co-ops and who happen to sneak into the hen house via the windows, cause we all know how insecure those are...
As a fellow govsub, I agree completely with the Professor. Also, I have seen first hand how software subcontractors will do work for the government and then lock the source up to make renewing the contract with a new firm, upon expiration of the original contract, that much more difficult. It sickens me sometimes what crap happens in the government.
This morning I read the Science Times and read a piece on Botulism and it detailed how a bottom feeder named a goby fish, an invasive species from Eastern Europe, was killing the eco-system of the lake. I guess here is an example of a bottom feeder killing the eco-system of the web...
If I read all of this right, it appears that the discoverers of the bug copyrighted their white paper in a way that prohibited distribution to anyone in the US. Thereby allowing them to invoke the DMCA if they so choose. As the register article points out, Red Hat was forced to go along with this because the authors of the bug whitepaper wanted to prove a point. With all of the real issues (Here & here) surrounding the DMCA, why are we even wasting our time with this?
Slashdot Mirror
They also have to figure out how to deliver and store the hydrogen in the cars themselves. Hydrogen gas is incredibly unstable and in an accident, if the canister holing the gas ruptures, there will be an explosion. Currently, fuel cell vehicles, use technology that pulls hydrogen from ethanol (or some other similar compound including std 93 octane) but that is only marginally more efficient than burning it.
It is like fusion, they know how to get the reaction going but have yet to develop a way to feed it without killing the reaction.
Finally, it is about time that an auto manufacturer step up to the plate. Too bad it is not an american mfg.
Fair enough on the corruption point. I understand however, the position of the admins who are near the end of the project and have very few resources left. Although the overwhelming support they have received from the public for their work is a blessing, it has been a curse too. The more users they got, the more money they had to spend to support them (although cost per user has probably gone down). I would not be surprised that the whole project is being run by Grad students right now and the university would probably lend support for any big catastrophes should they occur.
They are probably unable to cope at this point, so near the end, to deal with it real time. There is nothing to prevent them from going in later to adjust and obviously, any published work based on the project will have to deal with the issue. As for the future, you have a point that the public at large may take exception with this and feel any future work is comprimised but people tend to have short memories.
I would imagine that the Seti@HomeII project will deal with this issue as they are going to need to distribute new software anyway. They could easily come up with a mechanism similar to that used by software publishers who tie their registration id to the hardware. This way the work units can't be transferred from machine to machine. I just can't see them pulling this off in the next few months.
I have not had seti running for 6 months and am currently in 95 percentile. Before that I was running it occasionaly on a PII 400 mHz NT4 machine. Anyhow, who cares??? I have better things to worry about than people who are in a race to be the first to not discover alien life...
...or 2001234 (Verizon Boston Area)
The bluelight.com unit was apparently small and only had a 25 seat license. Since when does Mickeysoft send lawyers out to monitor the legal docs of the sale of a small business unit for license issues. Maybe they are actually interested in railroading bluelight.com for another reason... What we really need to know is what technology they licensed from MS and why it is so important to them. What was Bluelight running on the backend of their webservers, etc?
Where do you propose the old ones go? At least with CRT the environmental nightmare is on a ~5 year life-cycle. With this it may be just as toxic (not to mention the mfg process used) but it would be on a much faster life-cycle.
Correction: The first two sentences should read: That is possibly correct. Fonts (the files) themselves can be copyrighted but I do not know if the ones that ship with the OS are. Depending on the license, they may be limited to a particular OS.
I swear I previewed it twice and made corrections both times. I guess that should have made me preview it a third...
I am still hung over from stumbling around Cambridge last night. You have got to love the Cellar!
That is correct. Fonts (the files) themselves can be copyrighted but I not know if the ones that ship with the OS are. Just as an example, Adobe charges about $30 - $50 for recently released decorative fonts when purchased in individual packs. They get $8,999 (yes, that's right) for 2,750 ($3.27 per) fonts if you buy them in bulk. Imangine what the printing houses that publishers use to print their stuff have to pay for all of those fonts. Adobe is not the only one people use and the printing house has to have their own copy for their presses.
Yeah, that's the boys and girls from Haarrvaarrd...
This just in. Foxes have asks chicken farmers to place stronger locks on hen house doors to prevent aberant foxes from getting into the coop and swiping a meal. Farmers are currently reviewing the proposal which includes protections for foxes who belong to hunting co-ops and who happen to sneak into the hen house via the windows, cause we all know how insecure those are...
How about the (') and ("")???
For non windows users, that is (') and (")...
So then why paper??? Why not just make a special tablet that provides all of that functionality?
As a fellow govsub, I agree completely with the Professor. Also, I have seen first hand how software subcontractors will do work for the government and then lock the source up to make renewing the contract with a new firm, upon expiration of the original contract, that much more difficult. It sickens me sometimes what crap happens in the government.
This morning I read the Science Times and read a piece on Botulism and it detailed how a bottom feeder named a goby fish, an invasive species from Eastern Europe, was killing the eco-system of the lake. I guess here is an example of a bottom feeder killing the eco-system of the web...
Yeah, but they still write speeding tickets...
Uh people, has anyone been to ND in the dead of Winter??? No amount of Coke and Quake can get a semi-sane person through to Spring.
I know, I am a newbie! But what is 31337? It is not a valid zip and not in /etc/services so I am stumped.
This probably would have solved the cracking problem in Apples now defunct cube...
If I read all of this right, it appears that the discoverers of the bug copyrighted their white paper in a way that prohibited distribution to anyone in the US. Thereby allowing them to invoke the DMCA if they so choose. As the register article points out, Red Hat was forced to go along with this because the authors of the bug whitepaper wanted to prove a point. With all of the real issues (Here & here) surrounding the DMCA, why are we even wasting our time with this?