Yes, they should move on to a new host. Too bad their only copy of the data is at the hosting company that has held it hostage. So it's time to sue the bastards!
They should make the tabs be movable like everything else, and reconfigurable with respect to shape (let you enter a number and specify if it is number of columns or number of rows).
Third the whole "expand a widget to fill the screen then save the state stuff" is ridiculously bad design and ruins the usability of the site as a whole.
My guess is they want some room to add in the configuration/settings selections while still showing the original content. But it would be nice if this were a global settable option.
All that said, it's pretty clear that this is an example of developers doing something cool because they can not because it is useful in any way. In fact, it completely ruins the usability but as a developer myself I can see how some of it is very technically "neat". Unfortunately they destroyed usable in favor of neat. This is why developers need architects and designers to direct what they build and make sure it aligns with user needs. Purely technically driven development, while fun and cool, often leads to high quality but useless products. It is rarely as useful as when the various disciplines work together to produce something of both quality and value.
Unfortunately, I've never seen the original. Never heard of it before. I guess they forgot to spam me about it on my 5 Gmail accounts.
I have played both roles, as developer and as designer. I've also seen a similar problem where developers make things so extremely flexible for end users to design things their own way, it makes it too easy for end users to completely screw up and effectively lock themselves out of their own access. But sometimes the UI can do that, too. For example, one page I used once let me change the background and foreground color. One error is it only let people change one color at a time. I wanted to change black on white to white on black. Fortunately, I was smart enough to first change one of them to an intermediate color first. I'm sure some poor sucker ended up with his whole access in black on black:-)
The whole mentality here is that anybody can change the source of a project, submit it, and you never know what kind of compiled binary you're going to get.
That's why open source has source. You can examine the source code to see if there are any strange patches. Compile it yourself and then you know what kind of binary you're going to get.
That's also the big benefit of open source. There are thousands of eyes looking through it for the larger projects. You also get the benefit of customizing the source for your own purposes (and if you don't distribute the end results, you don't need to distribute the source of your changes, either, for the software under GPL).
I might worry about the projects where anyone in the world has CVS/SVN/GIT/HG commit access. Most don't do that. It's not like Wikipedia. And if you wonder if some project may have some nasty patches applied by less than honorable people, just look through the revision history or download some older tarballs, and look through the changes.
The real key *WAS* a big 32768 bit binary string stored in a key file. The key I memorized is just a pass-phrase key used to decrypt the real key. Unfortunately, the big binary key file was... accidentally deleted and written over by another file. Or maybe the police damaged it or lost it when they were making that first image copy of the hard drive.
...as a routine matter of course. If everyone does this, then all those unallocated blocks look like maybe they could be hidden data. But since everyone does this (that is, if we start doing this) it can be easily blamed on the residule random data. Need an excuse for even doing random data at all? It was a device test and there's no real reason to spend time to wipe it back to zero afterwards.
They already made an image copy of the disk. They are working from copies of copies. But maybe what you could do is use a program that uses more than just a key. It also uses specific gestures in how you personally interact with the computer as part of hashing that key into the data table used to actually decrypt.
Right now they are just going to record who sent something to whom. So send only SMALL messages and send a lot of them. And use a lot of different email addresses so every possible combination gets recorded. And be sure to reply. Drown out the spam!
... Linux version, or a 64-bit version, or whatever. So why don't the browser writers make their browsers just do videos as an integrated feature using a tag as simple as images (but with some extra properties appropriate for videos), with pluggable codecs compatible with the ones that come in mplayer (just install mplayer's codecs in the usual location and the browser finds them), and include Theora already integrated and ready to play.
The programmers at Adobe don't know much about how to write portable code that "just works" [TM] on all standard compliant platforms... or if they do, the managers are telling them to play dumb.
So the registered sex-offender just gives them "*@hotsexydaddylovingyou.com" or "anyname@hotsexydaddylovingyou.com". But given that the law requires a zero knowledge exchange, they might end up using SHA1 checksums of the email addresses. They would have to understand and know about this possibility as part of the protocol so that the site doing the lookup provides the checksum of the whole email, as well as the checksum of just the domain name. The latter would match if the pedo gave one of the forms recognized as any user name in the domain. But what if all they own is a pattern? The case of "+" as a separator in Gmail is one example. But other mail servers and provider, if they offer that, might be using some other character instead. My server is configured to use "-" for that (not "+"). Others might be doing it differently. And what about subdomains? What about "freecandy@themost.hostsexydaddylovingyou.com" being used? They are going to need to have someone really smart about this at the AG's office to make sure this system works right. Do you really think people that wear ties for a living can accomplish that?
And that's assuming the pedos are going to be both honest and thorough.
There's more than just design involved in parts that can run at higher temperatures. These parts will also be more expensive to manufacture. You also need to design and manufacture the other parts to operate at the higher temperatures. And you also need to make sure all the parts operate more efficiently at higher temperatures (normally as temperature goes up, parts are less efficient). Compare that to the cost of better insulation for the building. Compare that to the cost of arranging the building construction so that there is less surface for thermal ingress. It is a big complex model to work out.
Temperature is just the stable point across a heat flow. You could immerse an entire data center in liquid nitrogen, and you still only need to remove energy at the same rate in goes in. One problem with a lower temperature (relative to outside) is that the rate of leakage from outside is higher. That's fixed by having more/better insulation, in addition to raised solar panels covering the entire building.
Higher temperatures also increases resistance in conductors and electrical parts. That leads to more I2R power loses which is energy that doesn't get used but still has to be removed. Superconductors would be a plus for some of the core power feeds, too (you still do have to cool them).
Computers should be fed power at the highest practical voltage to keep current low (I2R losses, again). Most power supplies are more efficient at the lower current levels. That means at least 230 volts, if not higher. Commodity power supplies handle that fine. It wouldn't take much design change to bring them up to 277 volts (US) or 347 volts (Canada). And of course there might be even better efficiency involved in delivering 340 volts DC right to the PSU designed for it (most AC ones have that voltage as an intermediate step, anyway).
And efficient coding can be a factor here, as well, at the scale Google operates. Fewer cycles used for a given transaction means less energy needed to carry it out. Then the CPU goes back to idle and the clock can be kicked back to low frequency. And fewer machines needed to do searching means more machines can be completely off.
You can run a data center cheaper at a cooler temperature simply by having better insulation. The rate of energy in (power) equals the rate of energy out (power) at any stable temperature. But there is more energy in than just the electricity being used. Sunlight on the building is also energy in, to the extent that it bypasses the insulation. Better insulation limits this energy going in. If the insulation reduces the energy in from outside at a rate greater than the energy used in the form of electricity needed to pump heat around (blowers, etc), then you have a win and the stable temperature goes down.
Locating a data center on the north side of a mountain and/or at latitudes closer to the poles, is another way to reduce solar input leakage. But at the same time, it's also less opportunity for free solar electricity. One location, Iceland, does offer the cooler northern climate, reduced solar impact, and cheap geothermal electricity. They just need to build some big pipes (to North America and Europe). It could be a great place to put in an "extra capacity on demand" data center that could be used for European lookups when it peaks there, then North American lookups when the peak shifts over a few hours later, and then do crawls the rest of the time.
Iceland. It has cheap geothermal energy. And that's energy that's going to heat the Earth, anyway, similar to solar. They just need some big pipes between there are North America and Europe.
Slashdot Mirror
Yes, they should move on to a new host. Too bad their only copy of the data is at the hosting company that has held it hostage. So it's time to sue the bastards!
Frist, the left tabs waste real estate.
They should make the tabs be movable like everything else, and reconfigurable with respect to shape (let you enter a number and specify if it is number of columns or number of rows).
Third the whole "expand a widget to fill the screen then save the state stuff" is ridiculously bad design and ruins the usability of the site as a whole.
My guess is they want some room to add in the configuration/settings selections while still showing the original content. But it would be nice if this were a global settable option.
All that said, it's pretty clear that this is an example of developers doing something cool because they can not because it is useful in any way. In fact, it completely ruins the usability but as a developer myself I can see how some of it is very technically "neat". Unfortunately they destroyed usable in favor of neat. This is why developers need architects and designers to direct what they build and make sure it aligns with user needs. Purely technically driven development, while fun and cool, often leads to high quality but useless products. It is rarely as useful as when the various disciplines work together to produce something of both quality and value.
Unfortunately, I've never seen the original. Never heard of it before. I guess they forgot to spam me about it on my 5 Gmail accounts.
I have played both roles, as developer and as designer. I've also seen a similar problem where developers make things so extremely flexible for end users to design things their own way, it makes it too easy for end users to completely screw up and effectively lock themselves out of their own access. But sometimes the UI can do that, too. For example, one page I used once let me change the background and foreground color. One error is it only let people change one color at a time. I wanted to change black on white to white on black. Fortunately, I was smart enough to first change one of them to an intermediate color first. I'm sure some poor sucker ended up with his whole access in black on black :-)
...it's still in beta, like everything else at Google.
... movable like everything else. Also make them configurable vertical, square, horizontal. Problem solved!
...when you can't commit changes to fix things?
... and it doesn't show the correct channels at all. There needs to be a way to customize it.
... would determine how it affects this video.
The whole mentality here is that anybody can change the source of a project, submit it, and you never know what kind of compiled binary you're going to get.
That's why open source has source. You can examine the source code to see if there are any strange patches. Compile it yourself and then you know what kind of binary you're going to get.
That's also the big benefit of open source. There are thousands of eyes looking through it for the larger projects. You also get the benefit of customizing the source for your own purposes (and if you don't distribute the end results, you don't need to distribute the source of your changes, either, for the software under GPL).
I might worry about the projects where anyone in the world has CVS/SVN/GIT/HG commit access. Most don't do that. It's not like Wikipedia. And if you wonder if some project may have some nasty patches applied by less than honorable people, just look through the revision history or download some older tarballs, and look through the changes.
...to prevent people from opt-ing out on their own? Router based IP filtering?
The real key *WAS* a big 32768 bit binary string stored in a key file. The key I memorized is just a pass-phrase key used to decrypt the real key. Unfortunately, the big binary key file was ... accidentally deleted and written over by another file. Or maybe the police damaged it or lost it when they were making that first image copy of the hard drive.
...as a routine matter of course. If everyone does this, then all those unallocated blocks look like maybe they could be hidden data. But since everyone does this (that is, if we start doing this) it can be easily blamed on the residule random data. Need an excuse for even doing random data at all? It was a device test and there's no real reason to spend time to wipe it back to zero afterwards.
They already made an image copy of the disk. They are working from copies of copies. But maybe what you could do is use a program that uses more than just a key. It also uses specific gestures in how you personally interact with the computer as part of hashing that key into the data table used to actually decrypt.
Right now they are just going to record who sent something to whom. So send only SMALL messages and send a lot of them. And use a lot of different email addresses so every possible combination gets recorded. And be sure to reply. Drown out the spam!
... Linux version, or a 64-bit version, or whatever. So why don't the browser writers make their browsers just do videos as an integrated feature using a tag as simple as images (but with some extra properties appropriate for videos), with pluggable codecs compatible with the ones that come in mplayer (just install mplayer's codecs in the usual location and the browser finds them), and include Theora already integrated and ready to play.
... so it fits in the 32-bit memory model. Just turn off Cookies, Java, JavaScript, and Flash. Oh wait.
The programmers at Adobe don't know much about how to write portable code that "just works" [TM] on all standard compliant platforms ... or if they do, the managers are telling them to play dumb.
They can make computers he could use. Many people without arms use computers.
So the registered sex-offender just gives them " *@hotsexydaddylovingyou.com " or " anyname@hotsexydaddylovingyou.com ". But given that the law requires a zero knowledge exchange, they might end up using SHA1 checksums of the email addresses. They would have to understand and know about this possibility as part of the protocol so that the site doing the lookup provides the checksum of the whole email, as well as the checksum of just the domain name. The latter would match if the pedo gave one of the forms recognized as any user name in the domain. But what if all they own is a pattern? The case of "+" as a separator in Gmail is one example. But other mail servers and provider, if they offer that, might be using some other character instead. My server is configured to use "-" for that (not "+"). Others might be doing it differently. And what about subdomains? What about " freecandy@themost.hostsexydaddylovingyou.com " being used? They are going to need to have someone really smart about this at the AG's office to make sure this system works right. Do you really think people that wear ties for a living can accomplish that?
And that's assuming the pedos are going to be both honest and thorough.
... that gets CmdrTaco's email address added?
... for every site I sign up to. What if a convicted sex-offender did the same thing?
That's what they deliver in Denver.
There's more than just design involved in parts that can run at higher temperatures. These parts will also be more expensive to manufacture. You also need to design and manufacture the other parts to operate at the higher temperatures. And you also need to make sure all the parts operate more efficiently at higher temperatures (normally as temperature goes up, parts are less efficient). Compare that to the cost of better insulation for the building. Compare that to the cost of arranging the building construction so that there is less surface for thermal ingress. It is a big complex model to work out.
Temperature is just the stable point across a heat flow. You could immerse an entire data center in liquid nitrogen, and you still only need to remove energy at the same rate in goes in. One problem with a lower temperature (relative to outside) is that the rate of leakage from outside is higher. That's fixed by having more/better insulation, in addition to raised solar panels covering the entire building.
Higher temperatures also increases resistance in conductors and electrical parts. That leads to more I2R power loses which is energy that doesn't get used but still has to be removed. Superconductors would be a plus for some of the core power feeds, too (you still do have to cool them).
Computers should be fed power at the highest practical voltage to keep current low (I2R losses, again). Most power supplies are more efficient at the lower current levels. That means at least 230 volts, if not higher. Commodity power supplies handle that fine. It wouldn't take much design change to bring them up to 277 volts (US) or 347 volts (Canada). And of course there might be even better efficiency involved in delivering 340 volts DC right to the PSU designed for it (most AC ones have that voltage as an intermediate step, anyway).
And efficient coding can be a factor here, as well, at the scale Google operates. Fewer cycles used for a given transaction means less energy needed to carry it out. Then the CPU goes back to idle and the clock can be kicked back to low frequency. And fewer machines needed to do searching means more machines can be completely off.
You can run a data center cheaper at a cooler temperature simply by having better insulation. The rate of energy in (power) equals the rate of energy out (power) at any stable temperature. But there is more energy in than just the electricity being used. Sunlight on the building is also energy in, to the extent that it bypasses the insulation. Better insulation limits this energy going in. If the insulation reduces the energy in from outside at a rate greater than the energy used in the form of electricity needed to pump heat around (blowers, etc), then you have a win and the stable temperature goes down.
Locating a data center on the north side of a mountain and/or at latitudes closer to the poles, is another way to reduce solar input leakage. But at the same time, it's also less opportunity for free solar electricity. One location, Iceland, does offer the cooler northern climate, reduced solar impact, and cheap geothermal electricity. They just need to build some big pipes (to North America and Europe). It could be a great place to put in an "extra capacity on demand" data center that could be used for European lookups when it peaks there, then North American lookups when the peak shifts over a few hours later, and then do crawls the rest of the time.
Iceland. It has cheap geothermal energy. And that's energy that's going to heat the Earth, anyway, similar to solar. They just need some big pipes between there are North America and Europe.