you're talking about "good enough" encoding now, while in the grandparent post you were talking about "optimal" encoding.
My objection was that you suggested if you had several days worth of cycles, you could search all the tree and find optimal encoding. I still think this is false, even with a massive cluster at your fingertips.
I agree with you that "good enough" is good enough, though. And to reach that, you do not have to brute-force every possibility, you can use some heuristic to chop off some parts of the search-space.
Of course I agree with your original point that not having to do it in realtime enables you to find a better solution.
If any substantial change will happen, it will be in the programming of our computers. And who, other than you, behind that screen, would be able to implement that change?
Gravatar just needs every user to supply a "salt" along with there email where ever there gravatar is used, they could even call it a password. Combine the password/salt with the emacs to generate the hash. This would make guessing the email from the hash much more difficult.
yeah, as salt they could even use the gravatar image itself. In other words: I think this approach would render the usefullness of the service almost non-existant. It's not much harder to up a png than to remember some salt and enter it.
I'm no expert in cryptography, but would it be helpful for them to add a salt? (Unless they do that already, of course)
The salt would have to be secret, which would ruin the whole point of other sites being able to calculate the md5 and use the gravatar. Making it public wouldn't work, because it would then be known to the attacker.
On one hand the GPL violations are not so great...however action like this isn't going to encourage people to embrace open source...
I'm really glad they're doing this. Otherwise we would be back to the old days when OSS-Developers where just releasing their stuff to the public domain.
GPL != OSS. Unenforced GLP == public domain software.
But it will not stop that. All you have to do is include a link to the source on your website and a GPL statment with the product. You don't even have to include a link to the source you could "require" that they send you a written letter and pay for shipping of the source. Which frankly is all just silly. The source for BusyBox is freely available already so an extra link will not really make it any more free.
Dude, you have to make available also the _changes_ you made to the busybox code. e.g. some patches.
People tend to buy for worst-case instead of average-case scenarios - just in case they ever take that holiday to Disneyland, they don't want to pack in to a compact. Europeans on the other hand take a train.
instead of using floating point for representing decimal numbers, one can of coarse easily use fixed point... for currency computations, just store every value multiplied by 100 and use some fancy printing routine to put the decimal point at the right position.
in germany, you can't get a new one without it. Otto Schily received a lifetime bigbrother award in 2005 for introducing the biometric passport in germany.
Appliance computing would be very popular if it actually worked, if people could buy an appliance that would do what they need to do (mostly web surfing, email, light word processing, and games) without having to worry about all the problems of a general-purpose computer.
It _did_ work 8 years ago (sorry to reference my own post about the eVilla)
I think that did "actually work", but didn't become popular, which must've had some other reason,...
Slashdot Mirror
you're talking about "good enough" encoding now, while in the grandparent post you were talking about "optimal" encoding.
My objection was that you suggested if you had several days worth of cycles, you could search all the tree and find optimal encoding. I still think this is false, even with a massive cluster at your fingertips.
I agree with you that "good enough" is good enough, though. And to reach that, you do not have to brute-force every possibility, you can use some heuristic to chop off some parts of the search-space.
Of course I agree with your original point that not having to do it in realtime enables you to find a better solution.
this one is out, since it's not even stitched correctly. Zoom in on the "hotel" and you will notice a fault (the name of the hotel appears twice)
"How will it work? According to the Commitments document that was the basis of the agreement between Microsoft and the EU (download Word document)"
Download "Word document". wtf!
no, that would be 64%, damn.
rounded to -3rd in binary
"several days" will not suffice to brute-force all possible fractals
binary
"behind the screen, wanting for a change"?
If any substantial change will happen, it will be in the programming of our computers. And who, other than you, behind that screen, would be able to implement that change?
i think you're right on spot
Gravatar just needs every user to supply a "salt" along with there email where ever there gravatar is used, they could even call it a password. Combine the password/salt with the emacs to generate the hash. This would make guessing the email from the hash much more difficult.
yeah, as salt they could even use the gravatar image itself.
In other words: I think this approach would render the usefullness of the service almost non-existant. It's not much harder to up a png than to remember some salt and enter it.
I'm no expert in cryptography, but would it be helpful for them to add a salt? (Unless they do that already, of course)
The salt would have to be secret, which would ruin the whole point of other sites being able to calculate the md5 and use the gravatar. Making it public wouldn't work, because it would then be known to the attacker.
Yeah, I read it wrong :). Salt probably would've helped a bunch, though.
no, salt wouldn't help because it would have to be public and therefore known to the attacker, right?
On one hand the GPL violations are not so great...however action like this isn't going to encourage people to embrace open source...
I'm really glad they're doing this. Otherwise we would be back to the old days when OSS-Developers where just releasing their stuff to the public domain.
GPL != OSS.
Unenforced GLP == public domain software.
But it will not stop that.
All you have to do is include a link to the source on your website and a GPL statment with the product.
You don't even have to include a link to the source you could "require" that they send you a written letter and pay for shipping of the source.
Which frankly is all just silly.
The source for BusyBox is freely available already so an extra link will not really make it any more free.
Dude, you have to make available also the _changes_ you made to the busybox code. e.g. some patches.
And 300 pixels are worth 3.060575122 * 10^614 pictures
Most of which will resemble little more than random noise and have no value.
Yes, and some will show what the future looks like in 50 years.
The hard part is the selection.
People tend to buy for worst-case instead of average-case scenarios - just in case they ever take that holiday to Disneyland, they don't want to pack in to a compact. Europeans on the other hand take a train.
Across the Atlantic?
instead of using floating point for representing decimal numbers, one can of coarse easily use fixed point... for currency computations, just store every value multiplied by 100 and use some fancy printing routine to put the decimal point at the right position.
and let all hell break loose when someone forgets to multiply / divide by 100, like happened here: http://entertainment.slashdot.org/story/09/11/25/1448218/Moving-Decimal-Bug-Loses-Money
how is this flamebait?
in germany, you can't get a new one without it.
Otto Schily received a lifetime bigbrother award in 2005 for introducing the biometric passport in germany.
virtually well done, but for real... you loose
Googles approach here has been tried many times in the past and I am betting this attempt will end like all the others in complete failure.
I bet 10 euros against that.
mod parent up!
but let me disagree with the last argument.
Appliance computing would be very popular if it actually worked, if people could buy an appliance that would do what they need to do (mostly web surfing, email, light word processing, and games) without having to worry about all the problems of a general-purpose computer.
It _did_ work 8 years ago (sorry to reference my own post about the eVilla)
I think that did "actually work", but didn't become popular, which must've had some other reason,...
reminds me of eVilla and BeIA/BeOS.
I use adzapper for squid on my router. works well.
So, it's like changing the tires of a car to a larger or smaller one then miscounting the distance traveled based on rotations?
A very accurate, yet slashdot-compatible analogy. Congrats!