It would be nice to learn of other ways that we developers can fight such management intransigence. Find some other company that was sued for not being accessible, then point it out to your boss and say "look what happened to THESE guys!"
We shouldn't leave them to die, but if they do have a condition that will likely be passed to their children, they should consider whether they should help perpetuate its existence in our gene pool before they decide to have kids.
If we're going to circumvent the natural gene pool filter, we have the responsibility to our species to do it on our own.
I too have often wondered why more datacenters don't use water. (aside from the fact that you'd have to build the place from the ground up for it, probably)
I think a standardized interface could help immensely: - each rack-mount server has a cold water input on one side, and a hot water output on the other. - the rack has a cold water rail up one side and a hot return down the other. - under the floor, each rack is plugged into hot and cold "bus" pipes, which feed into one of those industrial waterfall coolers like you see on big a/c systems
It also highlights that the speed of light is going to quickly become a barrier to further speed advances.
What happens when "from your knuckle to your fingertip" becomes "from one side of the chip to the other?" The chip will have to wait on internal communication.
I keep thinking that ubiquitous electric cars will solve the "only works at night" problem. My normal car usage goes like this: - drive car to work - car sits in garage for 8 hours (where it could be solar charging) - drive car home - car sits in garage, where it could be powering stuff while it's dark Now multiply that by however many hundred million cars there are in the US. A previous discussion here had a normal tank of gas at around 900MJ, so replacing 150 million gas tanks with that many 900MJ batteries, you have 135,000TJ of energy, or about 70,000TJ if you set your car to stop giving back to the grid at half charge. How much energy do we use in a night?
I will have to second this. Some rough calculations yields about 1 billion blocked connections due to the PBL at our site since I put it in about a year ago, and I haven't had a *single* complaint about false positives from any of the 70,000 or so users behind it.
This even though the organization in question has hundreds of small operations (dr. offices) that are likely using cheap dynamic IP DSL sending them email.
Actually, using something like the Spamhaus PBL (which pre-emptively lists IP ranges that shouldn't be sending direct-to-MX email, such as ISP dynamic ranges), you actually CAN block significant portions of these botnets.
The three of my relays that use the combined Spamhaus SBL, XBL, and PBL block about 3.5 million connection attempts per day, and let 1 million emails/day through to the next layer of filtering. (about 78% of the flow, assuming that each connection would only drop off one email) The PBL accounts for about half of those blocks.
Your same logic could also be used to support the argument that closed source software would gain traction in that environment. If it becomes the case that cleverly designed software is the only way to improve performance once hardware advances slow, then companies will be much more likely to jealously guard their code!
Actually, I don't think a properly implemented system would need an encrypted link to the bank. The card has a keypad and a fingerprint reader (if we can get those small enough). It would work like this: - Plug card into POS device - Use keypad on card to choose which card to use (so you only have to carry one device) - POS device sends merchant ID and amount to the card - Use keypad enter card PIN/PW and fingerprint to decrypt the private key for the card you're using - Card signs a bank ID and key ID (so the bank knows what key to use on their end) and encrypts your account #, amount, and merchant id, then sends this back to the POS device - Merchant can send it however the heck they want to the bank, because only the bank can read it.
Another thing people never seem to consider is that the people in the US armed forces aren't stupid, and are probably some of our strongest patriots. If the government gets too out of hand, I think they'd be more likely to join a revolution than fight it. (assuming, of course, they can get reliable information as to what's really going on) I think they'd balk at oppressing the domestic population no matter what they were told, however.
Yahoo is all FreeBSD, the engineers there HATE and laugh at Microsoft and its products. I know for a fact that moral will sink and people will leave Yahoo.
I wonder what would happen if MS did buy Y!, and tried to migrate to MS systems, and 90% of the engineers (having previously arranged things) simply said, "No." MS couldn't really fire them all without really screwing things up.
I haven't checked the Cox TOS lately, but don't they prohibit running a home web server like all the other residential internet providers? Hasn't this been the case since for essentially the same length of time that the Internet has been a commercial venture?
That's only the case if you're using a *Content Delivery Provider* like Cox or Comcast, instead of an *Internet Service Provider* like Speakeasy. Unfortunately, real ISPs are becoming rather rare...
I've maintained that your option 3 is how things should work for some time now. You can tier the service based on the initial unrestricted bandwidth, but you get throttled across the board after that.
You can even set it up so that throttled users keep good burst bandwidth (so web browsing isn't affected), but sustained transfers are severely restricted.
The grocery is that close, but you can't walk? You have to take the bus to go a mile and a half?! Normal residential speed limits top out at 30mph, and assuming that you can start and stop instantaneously, that means your grocery store is at most 1.5 miles away. A reasonably healthy person can walk that in about 15 minutes. Children and the elderly might take 30, but that's not bad at all (and they'll be healthier for it).
I think 15 minutes is a little optimistic, but even if you could make it in 5 or 10, fine... I'm at the store, and I've bought 50lb of bulky groceries. Now what? Push the cart all the way home? I tend to make many small trips to the store (since it's on the way home from work, and thus a "free" stop), and even the small quantity of stuff I buy is tough to get into the house all in one trip. There's no way I could walk more than half a block that way (if that).
I don't think the freeways will be self-drive only any time soon. There are *far* too many existing cars that stick around for a long time to be able to bar them from the freeways.
For people like you that have those insanely long commutes, they need to have self driving vans with a bathroom, closet, etc. Your alarm clock just moves your bed into the van in the morning, and then you can wake up and get ready for work on the way.:)
Ah ha! That's why you use the dictionary in reverse. You make sure that your script only registers garbage domains, not ones that people would actually want to use. Heck, just generate random 25-character strings.
The way to deal with that is to have a "salary cap" on legal fee rewards. If you want to go out and hire an insanely expensive lawyer (or a whole department of them), go ahead, but don't expect to be reimbursed for your excess.
Virtualization can actually help with redundancy. If you need a mail relay, an AD server, and a DNS box, would you rather have two of each on their own hardware (six boxes), or three of each, with one each on each of three boxes (system load permitting)?
Actually, I think your number 6 might solve your number 5. Millions of plug-in electric cars with fast charging Li-ion batteries would be one heck of a distributed energy storage system. Just build the cars and charging systems with that in mind. If I'm doing my normal commute, I could set my car to maintain a minimum 25% charge, letting the grid use 75% for storage/peak mitigation. If I need long range for a trip in the next few days, I can set it to 75% or 100% minimum. This would even reduce the load on the transmission system, since the storage would be local (drive to work and plug in in the garage, and they can draw power straight from there).
Just give everyone a blanket 5 years. Then you can pay $25 per work for the first 2-year extension, $125 for the next, $625 for the next, etc. Unless it's really raking in the cash, it will become unprofitable after 15-20 years, and after 25 probably completely counter-productive (about $50M for another 2 years). I don't have any problem with that kind of time frame.
Actually, here in TX, you could use this to *cool* the roads. The extreme heat tends to crack and buckle the concrete. You'd also get some pretty hot water (even from the light-colored concrete). It's energy, and I'm sure someone could use it!
Slashdot Mirror
We shouldn't leave them to die, but if they do have a condition that will likely be passed to their children, they should consider whether they should help perpetuate its existence in our gene pool before they decide to have kids.
If we're going to circumvent the natural gene pool filter, we have the responsibility to our species to do it on our own.
I too have often wondered why more datacenters don't use water. (aside from the fact that you'd have to build the place from the ground up for it, probably)
I think a standardized interface could help immensely:
- each rack-mount server has a cold water input on one side, and a hot water output on the other.
- the rack has a cold water rail up one side and a hot return down the other.
- under the floor, each rack is plugged into hot and cold "bus" pipes, which feed into one of those industrial waterfall coolers like you see on big a/c systems
Leaks would be fun, though!
It also highlights that the speed of light is going to quickly become a barrier to further speed advances.
What happens when "from your knuckle to your fingertip" becomes "from one side of the chip to the other?" The chip will have to wait on internal communication.
I keep thinking that ubiquitous electric cars will solve the "only works at night" problem. My normal car usage goes like this:
- drive car to work
- car sits in garage for 8 hours (where it could be solar charging)
- drive car home
- car sits in garage, where it could be powering stuff while it's dark
Now multiply that by however many hundred million cars there are in the US. A previous discussion here had a normal tank of gas at around 900MJ, so replacing 150 million gas tanks with that many 900MJ batteries, you have 135,000TJ of energy, or about 70,000TJ if you set your car to stop giving back to the grid at half charge. How much energy do we use in a night?
I will have to second this. Some rough calculations yields about 1 billion blocked connections due to the PBL at our site since I put it in about a year ago, and I haven't had a *single* complaint about false positives from any of the 70,000 or so users behind it.
This even though the organization in question has hundreds of small operations (dr. offices) that are likely using cheap dynamic IP DSL sending them email.
Actually, using something like the Spamhaus PBL (which pre-emptively lists IP ranges that shouldn't be sending direct-to-MX email, such as ISP dynamic ranges), you actually CAN block significant portions of these botnets.
The three of my relays that use the combined Spamhaus SBL, XBL, and PBL block about 3.5 million connection attempts per day, and let 1 million emails/day through to the next layer of filtering. (about 78% of the flow, assuming that each connection would only drop off one email) The PBL accounts for about half of those blocks.
Your same logic could also be used to support the argument that closed source software would gain traction in that environment. If it becomes the case that cleverly designed software is the only way to improve performance once hardware advances slow, then companies will be much more likely to jealously guard their code!
Actually, I don't think a properly implemented system would need an encrypted link to the bank. The card has a keypad and a fingerprint reader (if we can get those small enough). It would work like this:
- Plug card into POS device
- Use keypad on card to choose which card to use (so you only have to carry one device)
- POS device sends merchant ID and amount to the card
- Use keypad enter card PIN/PW and fingerprint to decrypt the private key for the card you're using
- Card signs a bank ID and key ID (so the bank knows what key to use on their end) and encrypts your account #, amount, and merchant id, then sends this back to the POS device
- Merchant can send it however the heck they want to the bank, because only the bank can read it.
But how fast does it leak? Are a tank of water and some solar panels enough to make up for the leakage?
Another thing people never seem to consider is that the people in the US armed forces aren't stupid, and are probably some of our strongest patriots. If the government gets too out of hand, I think they'd be more likely to join a revolution than fight it. (assuming, of course, they can get reliable information as to what's really going on) I think they'd balk at oppressing the domestic population no matter what they were told, however.
I wonder what would happen if MS did buy Y!, and tried to migrate to MS systems, and 90% of the engineers (having previously arranged things) simply said, "No." MS couldn't really fire them all without really screwing things up.
It would be funny, anyway...
That's only the case if you're using a *Content Delivery Provider* like Cox or Comcast, instead of an *Internet Service Provider* like Speakeasy. Unfortunately, real ISPs are becoming rather rare...
It sounds like you were training for a Darwin Award
I've maintained that your option 3 is how things should work for some time now. You can tier the service based on the initial unrestricted bandwidth, but you get throttled across the board after that.
You can even set it up so that throttled users keep good burst bandwidth (so web browsing isn't affected), but sustained transfers are severely restricted.
Forget the bedroom... what about my home theatre? Cover everything but the projection area of the screen and the seating with this stuff.
:D
And for a practical joke, wait for your friend to do this, then paint his remote controls with it, too
...and the are filth-captial-E! I'm sure the thick layer of dust mixed with oily residue inside the monitor had NOTHING to do with this.
I'm willing to be the other one is similar... cat or dog hair, maybe?
I think 15 minutes is a little optimistic, but even if you could make it in 5 or 10, fine... I'm at the store, and I've bought 50lb of bulky groceries. Now what? Push the cart all the way home? I tend to make many small trips to the store (since it's on the way home from work, and thus a "free" stop), and even the small quantity of stuff I buy is tough to get into the house all in one trip. There's no way I could walk more than half a block that way (if that).
I don't think the freeways will be self-drive only any time soon. There are *far* too many existing cars that stick around for a long time to be able to bar them from the freeways.
:)
For people like you that have those insanely long commutes, they need to have self driving vans with a bathroom, closet, etc. Your alarm clock just moves your bed into the van in the morning, and then you can wake up and get ready for work on the way.
Ah ha! That's why you use the dictionary in reverse. You make sure that your script only registers garbage domains, not ones that people would actually want to use. Heck, just generate random 25-character strings.
The way to deal with that is to have a "salary cap" on legal fee rewards. If you want to go out and hire an insanely expensive lawyer (or a whole department of them), go ahead, but don't expect to be reimbursed for your excess.
Virtualization can actually help with redundancy. If you need a mail relay, an AD server, and a DNS box, would you rather have two of each on their own hardware (six boxes), or three of each, with one each on each of three boxes (system load permitting)?
Actually, I think your number 6 might solve your number 5. Millions of plug-in electric cars with fast charging Li-ion batteries would be one heck of a distributed energy storage system. Just build the cars and charging systems with that in mind. If I'm doing my normal commute, I could set my car to maintain a minimum 25% charge, letting the grid use 75% for storage/peak mitigation. If I need long range for a trip in the next few days, I can set it to 75% or 100% minimum. This would even reduce the load on the transmission system, since the storage would be local (drive to work and plug in in the garage, and they can draw power straight from there).
Just give everyone a blanket 5 years. Then you can pay $25 per work for the first 2-year extension, $125 for the next, $625 for the next, etc. Unless it's really raking in the cash, it will become unprofitable after 15-20 years, and after 25 probably completely counter-productive (about $50M for another 2 years). I don't have any problem with that kind of time frame.
Actually, here in TX, you could use this to *cool* the roads. The extreme heat tends to crack and buckle the concrete. You'd also get some pretty hot water (even from the light-colored concrete). It's energy, and I'm sure someone could use it!