There's basically one place for energy to go besides heat on the planet. It can be turned into EM and sent outward, and some of it will make it. (Hence lighted cities from outer space.)
Every other bit of solar energy that's turned into electricity eventually turns into heat, somewhere.
As almost all the light that's sent into space comes from space in the first place, this isn't really a worry. One solar panel will block more light from reflecting off the dirt back into space than we could possible turn into EM and spend back into space.
Basically, think of an air conditioner. Operating ten thousand air conditioners will not cause a city to freeze, because air conditions make things hotter on average. Likewise, solar panels make things hotter on average. All you've accomplished is to move heat around.
Nothing in my proposal requires it to use the entire electromagnetic spectrum. Did you not read what I said? I said divide the spectrum into specific frequencies with specific powers attached to them, and then, and only then, let people broadcast anything they want, within those boundaries. (And following a sort of low-level network protocol.) When dividing out the new channels, it would be trivial to say 'Okay, we can't use frequencies X to Y, because they need that to look at the sky.' In fact, you'd have to do that for the military anyway.
And it wouldn't cause more EM pollution, it would cause less, because we'd be able to broadcast at low powers and not worry about high-powered devices stepping on us on that frequency. Just like you can operate 1000 low-powered cell phones in the same area you can operate 40 CB channels...cell phones broadcast shorter distances, and thus take up less space, not more, in the EM spectrum.
In fact, it's been pointed out to me that 'repeaters' shouldn't be talking to each other via radio waves, but via wires. At that point, this is basically the cell phone network, with the addition of direct connection between cell phones, and the replacement of cell phones with anything that uses radio waves. Come up with some economic incentive to operate towers, and we'll see all the cell phone towers turn into them.
Of course, in a sane world, we'd be building our frickin observeries on the far side of the moon in the first place.
It's easy, and completely impossible to impliment at this point in time.
First, divide the spectrum into a million different slices. Specify some of them as high power, and some as low power, some as very long distance, some as fairly long distance, some as short distance, and a few as few very short distance, aka, bluetooth. (You need less as the distance gets shorter, because, duh, everyone can use the same ones.) OSI Layer 1.
Next, come up with some protocol. It needs a sender address, an optional destination address, and data, and that's it. Include a 'logical link control' to let people move around at will. Automatically negotiate a 'backchannel'. OSI Layer 2.
Then let anyone broadcast on any power/freqency, anything. But, and this is the key, require them to always negotiate downward to the 'worst' power/freqency that works, unless they have a good reason not to. (Aka, they're a TV station, and they don't want TVs to constantly have to call them back and say 'Hey, up the power a bit more.' Possibly you'd have to license this, but that's not important because most people would use devices that are bidirectional and thus don't need to worry about it, just the broadcast people.)
But, remember, each frequency has a set power, so if they want to broadcast stronger or lower, they'd need to change power/freqency. And, yes, attennas are designed for certain frequences, so we'd need to have evenly distributed strong and weak ones. (Aka, for every antenna size, we need to make sure we have a 'right next to the tower' power/frequency we can broadcast, and a 'A strong as possible' power/frequency too, that we can both hit with that antenna.)
Then build an assload of repeater stations. For any power/freqency, with the brains to let us link through them instead of directly. (In fact, if you have these, you can ignore the TV broadcast problem. Just have the TV station aim for these guys. If you can get it direct, good for you, if you can't, get it from them.)
The problem is that we're trying to solve a technological problem with regulations. There's plenty of bandwidth for everyone. It's just that we build devices that can't move around to get more. If we stop that, if we build some sort of 'airnet' that lets me use a specifically designated low power/freqency when I'm right under a cell phone tower, but flip to what is currently UHF at near-TV station power when I need drive behind a mountain (Thus sucking all my batteries, but that's not important.), we'd never have to worry again.
And, depending on how smart we design the network on top of this infrastructure, we can magically have cell phones and TV that can tune in radio stations, and direct-connect cell phones. Because there won't be any difference, except hopefully a layer of encryption on the cell phones.
Actually, every device will need some encryption, or at least authentication. So every idiot can't wander around pretending to be CBS. But, hey, we now have a world-wide wired infrastructure to grab public keys off of. And, really, no reason we couldn't hand out keys over the airwaves...we'd just have to what happens with web browsers now. You can get a signed cert, or you can make your own. In fact, make this part of layer 2, also, just because.
Of course, no way in hell this will ever happen...it requires throwing out all TVs and radios and cell phones and everything.
I just thought of something. If you use the person as the flywheel, the person can control their spin, and therefore the speed of the rotors, by sticking out their arms.
What do you mean, make money from FOSS? I think businesses do it all the time, when they install and use it. Otherwise, they're kinda wasting their time and resources no matter what OS they use.
Oh! You mean make money creating FOSS. Why the hell should 99% of the business world worry about that? They're not writing software, they're using software.
I love how these crazy meme is going around 'No one can make money from FOSS, therefore it won't catch on.'. Well, no one makes money from selling air, but, interestingly enough, we continue to use it.
No one sits down and goes 'Well, I could chose A or B, but B is cheaper and won't make other people as much money, so I better choose A.', and the idea they do is rather surreal.
That's why I'm laughing at all the people question if this possibly can work...it can. Maybe not under the rule 'no energy storage', but it can.
You just need to make the flywheel/rotor spin really fast. We're talking about ten times faster than the ideal speed of a rotor. And then slowly slant the blades into place, starting with a very small slant. Whoosh, up into the air you go.
Incredibly ineffient, yes. Possible, certainly.
Alternately, there's my suggestion of making the person be the flywheel. Dizzying, but I don't see why it can't work.
But with a flywheel, you can use just one rotor...you just rig the flywheel to turn the opposite direction. So the design might be easier.
Which would result in really sucky landings...not only would you run out of lift, but you'd start spinning right before you did so. But I don't see anything about landing in the rules.
There's the weight issue, but I have a solution: use the person as the flywheel.
Yes, your insurance can vary based on how far you drive.
Can vary. You don't pay twice as much insurance because you drive twice as far a week. You remember that 75% of accidents happen within 10 miles of your house? Well, that's a stupid fact, because that's where you usually drive, but most accidents happen before you get on or after you get off the freeway, aka, on 'surface streets'. 15 miles split into 5 three mile trips around the subdivision is much more dangerous than a mile to the highway, a 13 mile trip down it, and amile from the exit.
While, yes, distance can affect your insurace, it doesn't determine your insurance.
And the great-grandparent also completely ignored the average damage done in each accident. If a woman gets in a fender bender every six months, but a man totals someone else's car every year, guess which costs more?
Pretending that charging someone more who has less 'accidents-per-mile' is unfair is just silly. If they were being charged, per mile, for accidents, then that might make sense, but car insurance doesn't work anything like that.
I've always thought they should sell computers in what MS calls 'Hibernate', but everyone else calls 'Suspend to Disk'.
Where you plug it in, flip the switch, and boom, have a running OS in 10 seconds or so.
And let them play with it for a bit...yeah, they'll eventually have to configure some stuff, so have a 'finalize setup' window on the screen, but make it clear they can ignore that. And put a list of tasks in it, like 'Set up Internet' and whatnot, so they can just click on the task when they need it.
WTF does accidents per mile have to do with anything? You don't pay insurance per mile, do you?
No, you pay insurace per time period. If your group have more accidents per time period, then you pay more. Duh.
It doesn't matter that you're a safer driver...if I always get in an accident every time I drive, but only drive once a year, I'm cheaper to insure than someone who only gets in an accident every hundred times, but drives every single day.
Yes, explosives are out. Of any side. What we need to do is start drilling holes in the front of it, trying to get small bits to fall off. Not only will this, obviously, reduce the total mass when it does fall, but hopefully these bits will slow the remaining mass's fall, be getting caught underneither. (I can't seem to find a diagram of this, so that could be crazy.)
Also, it soulds like it would be a good idea if we could drill a hold into the volcano from the other side and start letting pressure out. But that's just a temporary fix, and it assumes we can do that without actually having the shockwaves of a full eruption that would knock the rock loose.
Alternately...how possible is a wall? A thirty foot high artifical reef around the west side of the island? I know it would be ripped to shreads, but if it would bounce most of the wave back towards the island, or even, say, north or south, where there's no land, it would be better than nothing.
Yeah, let's make sure to outlaw everything that doesn't achieve anything for society as a whole. And we'll rest easier knowing you're in charge of what, exactly, that is.
All this 'minor wound' stuff is crap, anyway. You get purple hearts for minor wounds. It's not like there's some sort of ranking system there. You get wounded in any way while in the military in a war zone, you can legitimately get a purple heart.
Now, they probably don't give them out for very very minor wounds, or fairly minor wounds you stupidly inflict on yourself. You cut yourself shaving or fall off a ladder and sprain your ankle, you probably won't get one...but you could, technically.
What I want to see is someone who was ever denied a purple heart while wounded under fire. Because you won't find it. If people are shooting at you, you can get one for running too fast down a hill and breaking your leg.
The implication that Kerry somehow got special awards that others did simply isn't true.
The KKK didn't exist until after the Civil War. (In fact, almost immediately after.)
However, the KKK is not the best example of anything, considering the current KKK is, really, the third organization going by that name, or at least the third version of the same organization.
But, yes, the KKK's 'issues' are not 140 years old.
To clarify: The patches to the OS/2 version of Windows were very small. Some very low level memory management stuff. Basically it was reintroducing standard mode, having Windows use normal extended memory instead of using a flat address space. Yes, IBM had the source code at the time, but they really didn't do a lot of changes. Think 'user-mode Windows', minus the hardware emulation. (Yes, Windows somehow managed to have direct access to your real hardware, which means that the OS/2 GUI managed to move out the way really quickly.)
As for Win4Lin, it runs a standard version of Windows, but I could have sworn it loads said standard version into memory and patches it there. I can't find any reference to this on google, though, so maybe I'm wrong.
WRT the memory space, I meant it was doing trickery to Windows, not Linux. I was under the impression that it didn't do the 'allocate X megs of memory to Windows and pretend that was all there is', but rather it basically made Window's allocate memory from Linux when it needed it, just like other programs. In other words, instead of the generic 'memory emulation' that VMWare does, it installed a memory 'driver' that just talked to Linux and got memory.
Of couse, I've never used Win4Lin, so I could be completely wrong about all of this. This is just the impressions I got of the differences between it and VMWare. The way you're describing it, it sounds exactly like VMWare.
Win4Lin was basically the same thing OS/2 used to run Windows 3.1 applications. It actually ran a patched version Windows next to Linux. It required kernel patches to Linux, too, and it was doing some very low-level trickery to basically make Windows and Linux run in the same memory space.
I forget if it was 3.1 or 9x, though. I'm thinking 9x, but could be wrong.
That niche in the market has basically been taken over by VMWare. People realized that running a full virtual machine was, indeed, partical, as long as you didn't emulate the CPU.
And, duh, his quote is exactly what he did, against the English. He dared them to shoot him. That was the entire base of his passive resistence movement. He wasn't advocating mass suidcide because he disliked Jews, he was advocating it it was the logical extension of his non-violence policy: Allow your enemy to kill you while you do absolutely nothing wrong, and let the world watch.
Nothing can or will do photo searches. There are exactly two ways to do them, currently, the first one involving strong AI image recognitation, and, I assure you, MS hasn't suddenly invented it. Their software can no more tell one photo from another than my cell phone can.
The other way, of course, involves you putting metatags on all your files. And there are plenty of programs to search metatags.
Develpoers have acknowlodged sendmail's shortcomings (And security flaws.)...that's why Postfix and Exim exist.
Hell, sendmail isn't even a Linux app, sendmail is a POS Unix application laying around since the begining of time. I have no idea how it ended up open source, but I wish it hadn't.
sendmail is crap. Everyone knows it. The single reason that it used to come with Linux servers was inertia. And some people have really stupid mail configurations that require some features. (Again, I invite people to tell me required features of sendmail that other, better designed servers don't have. No, milter isn't it, postfix can do real time mail filtering also.)
If it's really a hardship, you could always give them a year leeway. Give them a patent, but require they demonstrate a working model within the year or it's void.
Or, heck, it doesn't have to be a model, it could be a factory floor or something. Anything that actually did what the patent said. If you haven't built any implimentation of it in a year, tough.
And this would stop people from patenting things that are currently impossible, and I don't see that as a problem. The point of patents isn't to reward people who can predict future inventions before others, it's to encourage people to reveal actually existing inventions.
All this is ignoring the fact that purchasing bolt cutters seriously wastes time that you could be trying to locate your laptop. The solution is simple: Take the cable, hide it somewhere on your person. Duh.
If you phrase things right, you don't even have to 'lie' to the police. Just 'forget' to mention you removed the cable once you arrived at the scene.
This does slightly hurt you, as the cable can't be fingerprinted anymore. But, honestly, if they were stupid enough to touch the cable and then leave it, they probably touched something else. To be safe, don't grab the end when you pick it up, so if the cops figure out what happened, you can say 'oops' and hand them the cable.
Slashdot Mirror
There's basically one place for energy to go besides heat on the planet. It can be turned into EM and sent outward, and some of it will make it. (Hence lighted cities from outer space.)
Every other bit of solar energy that's turned into electricity eventually turns into heat, somewhere.
As almost all the light that's sent into space comes from space in the first place, this isn't really a worry. One solar panel will block more light from reflecting off the dirt back into space than we could possible turn into EM and spend back into space.
Basically, think of an air conditioner. Operating ten thousand air conditioners will not cause a city to freeze, because air conditions make things hotter on average. Likewise, solar panels make things hotter on average. All you've accomplished is to move heat around.
And it wouldn't cause more EM pollution, it would cause less, because we'd be able to broadcast at low powers and not worry about high-powered devices stepping on us on that frequency. Just like you can operate 1000 low-powered cell phones in the same area you can operate 40 CB channels...cell phones broadcast shorter distances, and thus take up less space, not more, in the EM spectrum.
In fact, it's been pointed out to me that 'repeaters' shouldn't be talking to each other via radio waves, but via wires. At that point, this is basically the cell phone network, with the addition of direct connection between cell phones, and the replacement of cell phones with anything that uses radio waves. Come up with some economic incentive to operate towers, and we'll see all the cell phone towers turn into them.
Of course, in a sane world, we'd be building our frickin observeries on the far side of the moon in the first place.
First, divide the spectrum into a million different slices. Specify some of them as high power, and some as low power, some as very long distance, some as fairly long distance, some as short distance, and a few as few very short distance, aka, bluetooth. (You need less as the distance gets shorter, because, duh, everyone can use the same ones.) OSI Layer 1.
Next, come up with some protocol. It needs a sender address, an optional destination address, and data, and that's it. Include a 'logical link control' to let people move around at will. Automatically negotiate a 'backchannel'. OSI Layer 2.
Then let anyone broadcast on any power/freqency, anything. But, and this is the key, require them to always negotiate downward to the 'worst' power/freqency that works, unless they have a good reason not to. (Aka, they're a TV station, and they don't want TVs to constantly have to call them back and say 'Hey, up the power a bit more.' Possibly you'd have to license this, but that's not important because most people would use devices that are bidirectional and thus don't need to worry about it, just the broadcast people.)
But, remember, each frequency has a set power, so if they want to broadcast stronger or lower, they'd need to change power/freqency. And, yes, attennas are designed for certain frequences, so we'd need to have evenly distributed strong and weak ones. (Aka, for every antenna size, we need to make sure we have a 'right next to the tower' power/frequency we can broadcast, and a 'A strong as possible' power/frequency too, that we can both hit with that antenna.)
Then build an assload of repeater stations. For any power/freqency, with the brains to let us link through them instead of directly. (In fact, if you have these, you can ignore the TV broadcast problem. Just have the TV station aim for these guys. If you can get it direct, good for you, if you can't, get it from them.)
The problem is that we're trying to solve a technological problem with regulations. There's plenty of bandwidth for everyone. It's just that we build devices that can't move around to get more. If we stop that, if we build some sort of 'airnet' that lets me use a specifically designated low power/freqency when I'm right under a cell phone tower, but flip to what is currently UHF at near-TV station power when I need drive behind a mountain (Thus sucking all my batteries, but that's not important.), we'd never have to worry again.
And, depending on how smart we design the network on top of this infrastructure, we can magically have cell phones and TV that can tune in radio stations, and direct-connect cell phones. Because there won't be any difference, except hopefully a layer of encryption on the cell phones.
Actually, every device will need some encryption, or at least authentication. So every idiot can't wander around pretending to be CBS. But, hey, we now have a world-wide wired infrastructure to grab public keys off of. And, really, no reason we couldn't hand out keys over the airwaves...we'd just have to what happens with web browsers now. You can get a signed cert, or you can make your own. In fact, make this part of layer 2, also, just because.
Of course, no way in hell this will ever happen...it requires throwing out all TVs and radios and cell phones and everything.
I just thought of something. If you use the person as the flywheel, the person can control their spin, and therefore the speed of the rotors, by sticking out their arms.
My God, both of you are exactly right.
Oh! You mean make money creating FOSS. Why the hell should 99% of the business world worry about that? They're not writing software, they're using software.
I love how these crazy meme is going around 'No one can make money from FOSS, therefore it won't catch on.'. Well, no one makes money from selling air, but, interestingly enough, we continue to use it.
No one sits down and goes 'Well, I could chose A or B, but B is cheaper and won't make other people as much money, so I better choose A.', and the idea they do is rather surreal.
You just need to make the flywheel/rotor spin really fast. We're talking about ten times faster than the ideal speed of a rotor. And then slowly slant the blades into place, starting with a very small slant. Whoosh, up into the air you go.
Incredibly ineffient, yes. Possible, certainly.
Alternately, there's my suggestion of making the person be the flywheel. Dizzying, but I don't see why it can't work.
Which would result in really sucky landings...not only would you run out of lift, but you'd start spinning right before you did so. But I don't see anything about landing in the rules.
There's the weight issue, but I have a solution: use the person as the flywheel.
Heck, leave the person behind while you're at it. Hey, wait, I had a toy like that...
My clothes happen to be filled with gasoline-filled balloons.
Can vary. You don't pay twice as much insurance because you drive twice as far a week. You remember that 75% of accidents happen within 10 miles of your house? Well, that's a stupid fact, because that's where you usually drive, but most accidents happen before you get on or after you get off the freeway, aka, on 'surface streets'. 15 miles split into 5 three mile trips around the subdivision is much more dangerous than a mile to the highway, a 13 mile trip down it, and amile from the exit.
While, yes, distance can affect your insurace, it doesn't determine your insurance.
And the great-grandparent also completely ignored the average damage done in each accident. If a woman gets in a fender bender every six months, but a man totals someone else's car every year, guess which costs more?
Pretending that charging someone more who has less 'accidents-per-mile' is unfair is just silly. If they were being charged, per mile, for accidents, then that might make sense, but car insurance doesn't work anything like that.
Where you plug it in, flip the switch, and boom, have a running OS in 10 seconds or so.
And let them play with it for a bit...yeah, they'll eventually have to configure some stuff, so have a 'finalize setup' window on the screen, but make it clear they can ignore that. And put a list of tasks in it, like 'Set up Internet' and whatnot, so they can just click on the task when they need it.
No, you pay insurace per time period. If your group have more accidents per time period, then you pay more. Duh.
It doesn't matter that you're a safer driver...if I always get in an accident every time I drive, but only drive once a year, I'm cheaper to insure than someone who only gets in an accident every hundred times, but drives every single day.
Also, it soulds like it would be a good idea if we could drill a hold into the volcano from the other side and start letting pressure out. But that's just a temporary fix, and it assumes we can do that without actually having the shockwaves of a full eruption that would knock the rock loose.
Alternately...how possible is a wall? A thirty foot high artifical reef around the west side of the island? I know it would be ripped to shreads, but if it would bounce most of the wave back towards the island, or even, say, north or south, where there's no land, it would be better than nothing.
Fucktard.
Now, they probably don't give them out for very very minor wounds, or fairly minor wounds you stupidly inflict on yourself. You cut yourself shaving or fall off a ladder and sprain your ankle, you probably won't get one...but you could, technically.
What I want to see is someone who was ever denied a purple heart while wounded under fire. Because you won't find it. If people are shooting at you, you can get one for running too fast down a hill and breaking your leg.
The implication that Kerry somehow got special awards that others did simply isn't true.
However, the KKK is not the best example of anything, considering the current KKK is, really, the third organization going by that name, or at least the third version of the same organization.
But, yes, the KKK's 'issues' are not 140 years old.
As for Win4Lin, it runs a standard version of Windows, but I could have sworn it loads said standard version into memory and patches it there. I can't find any reference to this on google, though, so maybe I'm wrong.
WRT the memory space, I meant it was doing trickery to Windows, not Linux. I was under the impression that it didn't do the 'allocate X megs of memory to Windows and pretend that was all there is', but rather it basically made Window's allocate memory from Linux when it needed it, just like other programs. In other words, instead of the generic 'memory emulation' that VMWare does, it installed a memory 'driver' that just talked to Linux and got memory.
Of couse, I've never used Win4Lin, so I could be completely wrong about all of this. This is just the impressions I got of the differences between it and VMWare. The way you're describing it, it sounds exactly like VMWare.
I forget if it was 3.1 or 9x, though. I'm thinking 9x, but could be wrong.
That niche in the market has basically been taken over by VMWare. People realized that running a full virtual machine was, indeed, partical, as long as you didn't emulate the CPU.
Here's what Gandhi actually thought about the situtation. Notice that, while 'violently' anti-violence, he conceeded that, if there ever was a just war, WWII was it, simply because of the genocide attempted by the Nazis.
And, duh, his quote is exactly what he did, against the English. He dared them to shoot him. That was the entire base of his passive resistence movement. He wasn't advocating mass suidcide because he disliked Jews, he was advocating it it was the logical extension of his non-violence policy: Allow your enemy to kill you while you do absolutely nothing wrong, and let the world watch.
The other way, of course, involves you putting metatags on all your files. And there are plenty of programs to search metatags.
Hell, sendmail isn't even a Linux app, sendmail is a POS Unix application laying around since the begining of time. I have no idea how it ended up open source, but I wish it hadn't.
sendmail is crap. Everyone knows it. The single reason that it used to come with Linux servers was inertia. And some people have really stupid mail configurations that require some features. (Again, I invite people to tell me required features of sendmail that other, better designed servers don't have. No, milter isn't it, postfix can do real time mail filtering also.)
'Hey, Frank, my wench isn't working right.' 'Ah, you're holding her wrong. Flip her around.'
Or, heck, it doesn't have to be a model, it could be a factory floor or something. Anything that actually did what the patent said. If you haven't built any implimentation of it in a year, tough.
And this would stop people from patenting things that are currently impossible, and I don't see that as a problem. The point of patents isn't to reward people who can predict future inventions before others, it's to encourage people to reveal actually existing inventions.
If you phrase things right, you don't even have to 'lie' to the police. Just 'forget' to mention you removed the cable once you arrived at the scene.
This does slightly hurt you, as the cable can't be fingerprinted anymore. But, honestly, if they were stupid enough to touch the cable and then leave it, they probably touched something else. To be safe, don't grab the end when you pick it up, so if the cops figure out what happened, you can say 'oops' and hand them the cable.