I'm an ass? You benefited from these laws, yet you'd deny that to the next generation. Look at yourself.
How about, we fix the system so our children don't end up having to lose out as well, when they grow up and are as-yet unmarried? You do admit that there are people losing out. That the system is not fair immediately follows, when there are people losing out.
Nobody loses out if you look at their whole life. Everybody gains as children. While it may seem that the parents are somehow gaining, they actually pay a great deal to help the next generation. The only freeloaders are those few people who are married without children; the law can not be perfect.
If anything, the single (including homosexual) people are better off than the people raising kids. Look at the lifestyle differences. Single people have nice cars, all the latest toys, more "culture" (movies, plays, concerts...), more travel, and so on. You're not contributing to the support of the next generation via raising kids. The financial impact of the extra taxes you pay is minor compared to the cost of supporting a family. Judging by the lifestyle you lead, a tax increase might be in order.
What part of "Tax laws and other laws will never be perfectly accurate and fair." do you not understand?
Perhaps this is the biggest tax loophole, but it's by no means unusual.
When people write the law, they think kids==families and families==married. As a very gross approximation, it works decently well. Kids don't pay the taxes; things would be easy if that were so.
When you attack marriage, you're attacking kids. This even includes kids like you once were.
Dig it up yourself if you want it, but I'll give you hints.
First study: Womb order matters. In a run of closely-spaced boys, the last boy born is more likely to be homosexual. This is true even after adjustment for post-birth factors studied via adoptions. (in other words, NOT the family life) The researchers speculate that the mother's immune system attacks the unborn child's brain.
Second study: Rams are known to often be homosexual. It turns out that this is caused by low sex hormone levels in the mother prior to birth. When hormone levels are manipulated, the problem can be made more or less frequent.
BTW, it is interesting that people wish to pretend that genes and the pre-birth environment play no role in mental issues. It seems that we prefer to believe that we are all born mentally identical, despite obvious evidence to the contrary. (with Down's syndrome being genetic and fetal alcohol syndrome being the pre-birth environment)
Us athiests often find that stuff just plain NASTY. (or sometimes funny... I mean really, you do WHAT???)
Since recent research strongly suggests that this is all about a birth defect caused by womb conditions, the government's interest in public health should lead lead to funding a search for early detection and prevention methods.
Though slightly inaccurate in modern times, "man and woman" roughly means "people who will make kids".
The benefits are for kids, not the adults.
Every homosexual has benefited from this. Despite having benefited as children, they selfishly wish to deny helping out future generations. These future generations even include homosexuals.
Yes, the married-no-kids people are getting a bit of a free ride. Oh well. Tax laws and other laws will never be perfectly accurate and fair. Live with it.
You lose out a bit now, as did other unmarried people when YOU were a kid. We can't go back in time to tax your parents more, causing you to have grown up in poverty. Too bad, because you deserve it.
Want to support LGBT people? Start by realizing that some of them are kids growing up in struggling families. Nearly none have non-heterosexual parents.
Heh. Do you know nothing of government? Efficent???
Government should pay only for care that must be mandated. That is, the treatment of people who are unable to discuss pricing and alternatives. (those who are spurting blood, leaking brain matter, etc.) For all the rest, we need to require that full pricing information be made available in advance of treatment. Without price competition, there can be no hope.
We also need to fully eliminate doctor liability and the practice of doctors buying insurance. Evil doctors go to prison. Incompetant doctors lose the right to practice medicine. For injury compensation, buy your own accident insurance if you want it.
Damn that's a fine shot. Being non-vertical, it even shows the reactor's service door.
The irregular octogon to the above left is a large auditorium attached to the physics building. The building with the white rectangle on top contains the swimming pool. The police are under the pedestrian overpass to the left.
Supposedly the core got redone in 2004 with low-grade uranium. Previously, it was using a very worn-out core of high-grade uranium.
BTW, there is an undergrad nuke program. UML is pretty decent for engineering and science, particularly the plastics engineering program. Non-nerds are segregated on the "South Campus" several miles away.
This thing probably got caught up in a general order to obscure ALL nuclear plants.
It's a really lame little plant, with barely any fuel. The white thing is a metal containment dome, attached to a 3-story or 4-story research building. It's about 4 stories tall. They give tours; you can look down into a pool of water to see the glowing blue core. It's called the Pinanski Energy Center.
Attacking this plant would do nothing of any real interest, though some idiots would surely freak out. The radiation source is deep below ground and really weak.
Most of the obscured area is just a parking lot. The research building extends to the northwest of the white reactor; they are attached. The area to the southwest is a parking lot for that building and the adjacent ones. The area to the northeast is a parking lot for the gym, which you can see with the white rectangle on the roof. The farthest west obscured area is a pedestrian overpass at the 3rd-floor level that runs between two unrelated buildings, the physics building (north) and engineering building (south). Most everything in the area is 4-story.
There are far more interesting things on campus that a person could attack, starting with the dorms!
You can find pictures on the web, including a lame attack by ABC news.
Instead of bluring, save as a minimum-quality JPEG and then load it again.
As long as you maintain alignment with the 8x8 JPEG compression blocks (possibly 8x16, 16x8, or 16x16 in the chroma channels) you'll get very little additional loss from subsequent recompression. The high-frequency information is simply gone.
Now the non-critical parts of the image will compress really well.
The problem will vary with zoom and apreture, and maybe even with focus. If a flash is involved (yuck), you have to deal with even worse problems from that.
Even if you left the lens cap on, you can repair the image the The GIMP. It does take some manual editing of the RBG values at each pixel location though.
Maybe I am worth 2 seconds on an already-existing highly parallel hardware-based cracking machine. (that is, let's assume the machine is already built and paid for -- the only costs are electrical power and the cost of lost opportunity to attack some other target)
That doesn't make me worth the costs of ASIC engineering, chip mask creation, chip manufacture, board fabrication, and all the work associated with setting up a machine that is only useful for a 2-second attack against me.
That could be $3 in the first case, and $500000 or more in the second case. Perhaps I'm only an interesting contact worth $7.
A hardware-based key cracker might not be all that adaptable. Forcing the attacker to build new hardware JUST FOR ATTACKING YOU is rather nice.
Even software-based key crackers would require a bit of effort to retarget. You might not be worth the effort. The effort could well involve putting a contract out for bids, waiting, selecting a bidder, and waiting some more.
The best spot I can imagine is right above 1st-class, but that would require a rather large section of non-metallic surface to get coverage decently close to the horizon. The top of the tail could work, but it is rather small and probably full of mechanical parts. The tail isn't a place to be putting stuff that isn't critical for flight.
The situation gets much better if you don't mind having 3 to 6 dishes.
Every semester, you pack all your stuff into the car to go to school. You carry your stuff up the stairs to the fourth floor. You place your computer on a small desk, perhaps 60x110 cm or a bit more than 2x3 feet. All your stuff must fit in a small room that you share with somebody you probably hate. Five months later, you carry your stuff down the stairs to your car again.
Probably there is no air conditioning to deal with the heat given off by a CRT.
If you are unlucky, you keep tripping a circuit breaker that was designed (40 years ago) to handle the load of a shaver and an alarm clock.
The CRT's shadow mask or apreture grill gets misaligned from all those trips up and down the stairs, as well as from the occasional fistfight with your roommate or his drunken girlfriend.
By "Can I move a stream from one file to another?" I mean "move filename.ext:mystream otherfile.ext:newlocation". I don't mean copying the data. One file gains a stream that is lost from some other file.
The read() system call is not normally implemented for directories. It once was how directory reads were done, back when UNIX only had one type of filesystem. It was then kept around for a while, rather useless, but working. Linux even had it long ago, despite not sharing code with the old UNIX systems and not really having any use for the ability.
Even if you use read() on a directory as the implementation, lots of tools still break. The file type can only be one or the other, not both. Either it looks like a file or it looks like a directory. Either way, apps will refuse to deal with it.
It'll always be a thorn in your side. It's costly. It can make you sick. It can kill a baby. It will compete with you for attention. It will compete with your kids for attention. It won't go away; it will be replaced with another cat.
Normal APIs don't support extra streams. Getting fopen() to work with streams is a hack, to put it mildly.
The notation used on Windows is... interesting. If you are in D:\ with a file called C, does C:foo refer to a stream on D:\C or to a file called foo in the current directory of the C drive?
On a Linux or MacOS system, all characters except '/' and '\0' are valid in filenames, so we have nothing to spare. No, you can't steal the ':'.
Today I can copy a file with the dd command. I can copy a file using the cat command and shell redirection. Multi-forked files would lose data.
It looks like you need a directory... why not use one? This is how MacOS X apps work.
There are fundamental difficulties with on-disk data structures related to fragmentation and bloat. You add complexity for little gain.
Do these extra streams get permission bits? Can you solidly justify your choice?
Can a stream have a stream? If not, why the limitation?
Can I move a stream from one file to another? Can I move a stream to be just a regular file? Can I move a file into another file, to become an extra stream?
Why should everything become more complex (buggy, slow, insecure, confusing, etc.) for this barely-useful feature?
Slashdot Mirror
Get a piece of depleted uranium (or tungsten) the size and shape of a telephone pole. Drop it from space.
For bonus points, slingshot it around Jupiter. It then travels in the direction of the bunker, helped by both Earth and Sun gravity.
Verizon wants to disable EVERYTHING on the phone that isn't pay-per-use. If you were thinking the iPhone was restrictive, think again.
Nobody loses out if you look at their whole life. Everybody gains as children. While it may seem that the parents are somehow gaining, they actually pay a great deal to help the next generation. The only freeloaders are those few people who are married without children; the law can not be perfect.
If anything, the single (including homosexual) people are better off than the people raising kids. Look at the lifestyle differences. Single people have nice cars, all the latest toys, more "culture" (movies, plays, concerts...), more travel, and so on. You're not contributing to the support of the next generation via raising kids. The financial impact of the extra taxes you pay is minor compared to the cost of supporting a family. Judging by the lifestyle you lead, a tax increase might be in order.
What part of "Tax laws and other laws will never be perfectly accurate and fair." do you not understand?
Perhaps this is the biggest tax loophole, but it's by no means unusual.
When people write the law, they think kids==families and families==married. As a very gross approximation, it works decently well. Kids don't pay the taxes; things would be easy if that were so.
When you attack marriage, you're attacking kids. This even includes kids like you once were.
Dig it up yourself if you want it, but I'll give you hints.
First study: Womb order matters. In a run of closely-spaced boys, the last boy born is more likely to be homosexual. This is true even after adjustment for post-birth factors studied via adoptions. (in other words, NOT the family life) The researchers speculate that the mother's immune system attacks the unborn child's brain.
Second study: Rams are known to often be homosexual. It turns out that this is caused by low sex hormone levels in the mother prior to birth. When hormone levels are manipulated, the problem can be made more or less frequent.
BTW, it is interesting that people wish to pretend that genes and the pre-birth environment play no role in mental issues. It seems that we prefer to believe that we are all born mentally identical, despite obvious evidence to the contrary. (with Down's syndrome being genetic and fetal alcohol syndrome being the pre-birth environment)
No need for religion!
Us athiests often find that stuff just plain NASTY. (or sometimes funny... I mean really, you do WHAT???)
Since recent research strongly suggests that this is all about a birth defect caused by womb conditions, the government's interest in public health should lead lead to funding a search for early detection and prevention methods.
Though slightly inaccurate in modern times, "man and woman" roughly means "people who will make kids".
The benefits are for kids, not the adults.
Every homosexual has benefited from this. Despite having benefited as children, they selfishly wish to deny helping out future generations. These future generations even include homosexuals.
Yes, the married-no-kids people are getting a bit of a free ride. Oh well. Tax laws and other laws will never be perfectly accurate and fair. Live with it.
You lose out a bit now, as did other unmarried people when YOU were a kid. We can't go back in time to tax your parents more, causing you to have grown up in poverty. Too bad, because you deserve it.
Want to support LGBT people? Start by realizing that some of them are kids growing up in struggling families. Nearly none have non-heterosexual parents.
"more efficent single system health care"
Heh. Do you know nothing of government? Efficent???
Government should pay only for care that must be mandated. That is, the treatment of people who are unable to discuss pricing and alternatives. (those who are spurting blood, leaking brain matter, etc.) For all the rest, we need to require that full pricing information be made available in advance of treatment. Without price competition, there can be no hope.
We also need to fully eliminate doctor liability and the practice of doctors buying insurance. Evil doctors go to prison. Incompetant doctors lose the right to practice medicine. For injury compensation, buy your own accident insurance if you want it.
Damn that's a fine shot. Being non-vertical, it even shows the reactor's service door.
The irregular octogon to the above left is a large auditorium attached to the physics building. The building with the white rectangle on top contains the swimming pool. The police are under the pedestrian overpass to the left.
Supposedly the core got redone in 2004 with low-grade uranium. Previously, it was using a very worn-out core of high-grade uranium.
BTW, there is an undergrad nuke program. UML is pretty decent for engineering and science, particularly the plastics engineering program. Non-nerds are segregated on the "South Campus" several miles away.
You can walk right up to the containment building. (the white dome)
You can fondle it all you want. You'd be about 250 to 300 feet (100 meters) from the campus police though, so keep your clothes on.
This thing probably got caught up in a general order to obscure ALL nuclear plants.
a services/north_campus/pinanski_hall.htmli d=988778
It's a really lame little plant, with barely any fuel. The white thing is a metal containment dome, attached to a 3-story or 4-story research building. It's about 4 stories tall. They give tours; you can look down into a pool of water to see the glowing blue core. It's called the Pinanski Energy Center.
Attacking this plant would do nothing of any real interest, though some idiots would surely freak out. The radiation source is deep below ground and really weak.
Most of the obscured area is just a parking lot. The research building extends to the northwest of the white reactor; they are attached. The area to the southwest is a parking lot for that building and the adjacent ones. The area to the northeast is a parking lot for the gym, which you can see with the white rectangle on the roof. The farthest west obscured area is a pedestrian overpass at the 3rd-floor level that runs between two unrelated buildings, the physics building (north) and engineering building (south). Most everything in the area is 4-story.
There are far more interesting things on campus that a person could attack, starting with the dorms!
You can find pictures on the web, including a lame attack by ABC news.
http://www.uml.edu/maps/pinanski.htm
http://www.uml.edu/student-services/disability/ad
http://abcnews.go.com/Primetime/LooseNukes/story?
Instead of bluring, save as a minimum-quality JPEG and then load it again.
As long as you maintain alignment with the 8x8 JPEG compression blocks (possibly 8x16, 16x8, or 16x16 in the chroma channels) you'll get very little additional loss from subsequent recompression. The high-frequency information is simply gone.
Now the non-critical parts of the image will compress really well.
I got only 6.3 MP (6.0 MP active, 6.1 MP claimed) on
a 23.5x15.7 mm chip. Your example was 7 MP on 5.8x4.3 mm.
Going by the 6.3 MP figure...
Mine is thus 58.56 square micrometers per pixel.
You example is only 3.56 square micrometers per pixel.
That is a factor of 16.44 difference.
The camera is actually crap as far as this goes.
The problem will vary with zoom and apreture, and maybe even with focus. If a flash is involved (yuck), you have to deal with even worse problems from that.
The scaling just got fixed. It'll be in the next release AFAIK.
Even if you left the lens cap on, you can repair the image the The GIMP. It does take some manual editing of the RBG values at each pixel location though.
Maybe I am worth 2 seconds on an already-existing highly parallel hardware-based cracking machine. (that is, let's assume the machine is already built and paid for -- the only costs are electrical power and the cost of lost opportunity to attack some other target)
That doesn't make me worth the costs of ASIC engineering, chip mask creation, chip manufacture, board fabrication, and all the work associated with setting up a machine that is only useful for a 2-second attack against me.
That could be $3 in the first case, and $500000 or more in the second case. Perhaps I'm only an interesting contact worth $7.
A hardware-based key cracker might not be all that adaptable. Forcing the attacker to build new hardware JUST FOR ATTACKING YOU is rather nice.
Even software-based key crackers would require a bit of effort to retarget. You might not be worth the effort. The effort could well involve putting a contract out for bids, waiting, selecting a bidder, and waiting some more.
The best spot I can imagine is right above 1st-class, but that would require a rather large section of non-metallic surface to get coverage decently close to the horizon. The top of the tail could work, but it is rather small and probably full of mechanical parts. The tail isn't a place to be putting stuff that isn't critical for flight.
The situation gets much better if you don't mind having 3 to 6 dishes.
Every semester, you pack all your stuff into the car to go to school. You carry your stuff up the stairs to the fourth floor. You place your computer on a small desk, perhaps 60x110 cm or a bit more than 2x3 feet. All your stuff must fit in a small room that you share with somebody you probably hate. Five months later, you carry your stuff down the stairs to your car again.
Probably there is no air conditioning to deal with the heat given off by a CRT.
If you are unlucky, you keep tripping a circuit breaker that was designed (40 years ago) to handle the load of a shaver and an alarm clock.
The CRT's shadow mask or apreture grill gets misaligned from all those trips up and down the stairs, as well as from the occasional fistfight with your roommate or his drunken girlfriend.
By "Can I move a stream from one file to another?" I mean "move filename.ext:mystream otherfile.ext:newlocation". I don't mean copying the data. One file gains a stream that is lost from some other file.
The read() system call is not normally implemented for directories. It once was how directory reads were done, back when UNIX only had one type of filesystem. It was then kept around for a while, rather useless, but working. Linux even had it long ago, despite not sharing code with the old UNIX systems and not really having any use for the ability.
Even if you use read() on a directory as the implementation, lots of tools still break. The file type can only be one or the other, not both. Either it looks like a file or it looks like a directory. Either way, apps will refuse to deal with it.
They should be been destroyed cately.
Seriously, consider the cat to be a deal breaker.
It'll always be a thorn in your side. It's costly. It can make you sick. It can kill a baby. It will compete with you for attention. It will compete with your kids for attention. It won't go away; it will be replaced with another cat.
Normal APIs don't support extra streams. Getting fopen() to work with streams is a hack, to put it mildly.
The notation used on Windows is... interesting. If you are in D:\ with a file called C, does C:foo refer to a stream on D:\C or to a file called foo in the current directory of the C drive?
On a Linux or MacOS system, all characters except '/' and '\0' are valid in filenames, so we have nothing to spare. No, you can't steal the ':'.
Today I can copy a file with the dd command. I can copy a file using the cat command and shell redirection. Multi-forked files would lose data.
It looks like you need a directory... why not use one? This is how MacOS X apps work.
There are fundamental difficulties with on-disk data structures related to fragmentation and bloat. You add complexity for little gain.
Do these extra streams get permission bits? Can you solidly justify your choice?
Can a stream have a stream? If not, why the limitation?
Can I move a stream from one file to another? Can I move a stream to be just a regular file? Can I move a file into another file, to become an extra stream?
Why should everything become more complex (buggy, slow, insecure, confusing, etc.) for this barely-useful feature?
I'll make the anti-Microsoft "errors" for him to correct.