In this case, you could view the html source yourself, type in the URL for the image you want, and voila, just the image would pop up. No copyright infringement, because they have built their site to provide the image to any anonymous client on demand.
In much the same way, you can pick up a free newspaper from a rack, take it home, and cut out an article to paste on your door.
But now if I write a page that instructs your browser to go to the other site and request the original image, then surround it with flowers instead of ads, this is copy right infringement. But they gave it to you on your request.
...however, if you make a copy of the whole article and stick it in your own free newsletter, that's a violation of copyright, *even if you credit the author*.
They just don't want people taking credit for work that doesn't belong to them. Not such a bad thing, really. That's how copyright is supposed to work.
The problem with weighing security vulnerabilities is that, apart from just counting the bugs, it's a completely arbitrary measurement. One might assert that Bug X is worse than Bug Y, but there's no scientific way to back up those assertions.
Some people might argue that total cost in damages caused by security vulnerabilities is a good measurement (and certainly, Windows has racked up billions of dollars in this category). The truth, however, is that with Windows' wider deployment, it's far more prone to attack in general. Since Windows machines make up some 90% of all desktops, more virus writers target it, and the viruses written for it have more places to spread. Dense, non-diverse populations are inherently more vulnerable to plagues.
Is Linux really more vulnerable than Windows, in the grand scheme of things? Given the above facts, it's difficult to say. There are valid arguments for both sides.
That said, it's been shown that Linux users as a community have the resources to get in and fix security holes far quicker than Microsoft is capable of doing with Windows. So, if you feel like complaining about the security report, my advice would be to take that energy and use it to help with testing and patching instead.
About two years ago, when I was still cooped up in my tiny little freshman dorm room with my two roommates, I knew a guy named Tom Freck. Tom was a pretty nice guy, always willing to stop by and chat, or lend a hand with homework.
I always wondered, though, why he was a Computer Science major. His computer skills were at best mediocre--he could turn his system on and run a word processor without any problems, but when it came time to install hardware or write an actual program... well, suffice it to say that problems would arise.
Normally, this wouldn't have been too big a deal. There were at least seven other Computer Science majors living on our floor--so there were very few computer problems that, among all of us, couldn't be fixed. Tom's problem, as far as I could tell, was a general lack of faith in our abilities.
The event that I have thus far been leading up to took place in November of 1996, if I remember right. Somehow, one of Tom's Windows 95 driver files got corrupted. Tom immediately pulled out the number to Compaq's customer service line and dialed up to ask their assistance.
It should be noted at this point that the error occurred at about 4 o'clock in the afternoon. Myself and a few others offered to help him out, but he insisted that Compaq Tech Service would do a better job. Not thinking much of it, I proceeded to my evening classes, then went home and flopped into bed. The next morning, I was surprised to see Tom in his dorm room (the doors in Taylor Tower are routinely kept open--it's tradition or something), eyes bloodshot from lack of sleep, still on hold waiting for tech service to answer.
"You okay, man?" I asked him.
He gave no indication that he even noticed I was there, so I waved my hand in front of his face. He jumped about three feet in the air. "Huh?"
"I asked if you were doing alright."
He shook his head vigourously to clear the fog from his brain. "Yeah, I'm okay. Just waiting for tech support to take my call."
I shrugged. "Well, just lemme know if I can help out, okay?"
He just nodded dismissively, so I headed off to my freshman chemistry course, leaving him to his fate.
When I returned that night, he was still on hold. My attempts to get his attention were innefective this time, so I again shrugged it off and went to bed.
This went on for the better part of three days. It got to the point that people walking by his room were so used to him being glued to the telephone that they would hardly give him a second look as they passed.
Then, that fateful Saturday morning, he dissappeared. We asked around the building to get some idea of his whereabouts, getting a few responses about a strange figure stumbling out of the building some time around 3 AM.
We decided to file a missing persons report with the campus police--there wasn't much else we could do at that point. Later that day, one of my neighbors called me into his room to see something on the six o'clock news. Apparently, an unidentified man had been sighted running stark naked down North High Street, screaming, "I AM THE NEXT AVAILABLE SERVICE REPRESENTATIVE!" at the top of his lungs.
None of us ever saw him after that, but to this day, if you listen hard enough late at night, you can still hear a recorded voice saying, "Your call is important to us. Please stay on the line and wait for the next available service representative."
The code that allows Windows to antialias fonts appears to be in the form of a bunch of DLLs. Would it be possible to write a new DLL that uses the (obviously superior) antialiasing algorithm that's now becoming available under X?
Slashdot Mirror
+1 Sweet
+1 Awwwwww
+1 Cute
-1 Corny
-1 Sappy
In this case, you could view the html source yourself, type in the URL for the image you want, and voila, just the image would pop up. No copyright infringement, because they have built their site to provide the image to any anonymous client on demand.
In much the same way, you can pick up a free newspaper from a rack, take it home, and cut out an article to paste on your door.
But now if I write a page that instructs your browser to go to the other site and request the original image, then surround it with flowers instead of ads, this is copy right infringement. But they gave it to you on your request.
...however, if you make a copy of the whole article and stick it in your own free newsletter, that's a violation of copyright, *even if you credit the author*.
They just don't want people taking credit for work that doesn't belong to them. Not such a bad thing, really. That's how copyright is supposed to work.
Lendrick
A .PDF would be all over the internet within days. They're better off printing a book.
Figured it would end with the fence being built with a swiss army knife and some duct tape, or something.
The problem with weighing security vulnerabilities is that, apart from just counting the bugs, it's a completely arbitrary measurement. One might assert that Bug X is worse than Bug Y, but there's no scientific way to back up those assertions.
Some people might argue that total cost in damages caused by security vulnerabilities is a good measurement (and certainly, Windows has racked up billions of dollars in this category). The truth, however, is that with Windows' wider deployment, it's far more prone to attack in general. Since Windows machines make up some 90% of all desktops, more virus writers target it, and the viruses written for it have more places to spread. Dense, non-diverse populations are inherently more vulnerable to plagues.
Is Linux really more vulnerable than Windows, in the grand scheme of things? Given the above facts, it's difficult to say. There are valid arguments for both sides.
That said, it's been shown that Linux users as a community have the resources to get in and fix security holes far quicker than Microsoft is capable of doing with Windows. So, if you feel like complaining about the security report, my advice would be to take that energy and use it to help with testing and patching instead.
Peace,
Lendrick
I guess Agent Smith's job just got a lot easier.
To be honest, I was always a bit dissappointed that I wasn't living in a barred spiral. Turns out I am. Nifty. :)
You are clear to mod my previous post down to -1. I'll go grab a glass of water to wash down my foot.
Lendrick
Very few people ever get this right, so get a good look and do everyone a favor by not modding it down.
If a name ends in an 's' (Scott Adams, for example), the apostrophe should appear after the end of the word.
Correctly written: "Scott Adams' God's Debris."
About two years ago, when I was still cooped up in my tiny little freshman dorm room with my two roommates, I knew a guy named Tom Freck. Tom was a pretty nice guy, always willing to stop by and chat, or lend a hand with homework.
I always wondered, though, why he was a Computer Science major. His computer skills were at best mediocre--he could turn his system on and run a word processor without any problems, but when it came time to install hardware or write an actual program ... well, suffice it to say that problems would arise.
Normally, this wouldn't have been too big a deal. There were at least seven other Computer Science majors living on our floor--so there were very few computer problems that, among all of us, couldn't be fixed. Tom's problem, as far as I could tell, was a general lack of faith in our abilities.
The event that I have thus far been leading up to took place in November of 1996, if I remember right. Somehow, one of Tom's Windows 95 driver files got corrupted. Tom immediately pulled out the number to Compaq's customer service line and dialed up to ask their assistance.
It should be noted at this point that the error occurred at about 4 o'clock in the afternoon. Myself and a few others offered to help him out, but he insisted that Compaq Tech Service would do a better job. Not thinking much of it, I proceeded to my evening classes, then went home and flopped into bed. The next morning, I was surprised to see Tom in his dorm room (the doors in Taylor Tower are routinely kept open--it's tradition or something), eyes bloodshot from lack of sleep, still on hold waiting for tech service to answer.
"You okay, man?" I asked him.
He gave no indication that he even noticed I was there, so I waved my hand in front of his face. He jumped about three feet in the air. "Huh?"
"I asked if you were doing alright."
He shook his head vigourously to clear the fog from his brain. "Yeah, I'm okay. Just waiting for tech support to take my call."
I shrugged. "Well, just lemme know if I can help out, okay?"
He just nodded dismissively, so I headed off to my freshman chemistry course, leaving him to his fate.
When I returned that night, he was still on hold. My attempts to get his attention were innefective this time, so I again shrugged it off and went to bed.
This went on for the better part of three days. It got to the point that people walking by his room were so used to him being glued to the telephone that they would hardly give him a second look as they passed.
Then, that fateful Saturday morning, he dissappeared. We asked around the building to get some idea of his whereabouts, getting a few responses about a strange figure stumbling out of the building some time around 3 AM.
We decided to file a missing persons report with the campus police--there wasn't much else we could do at that point. Later that day, one of my neighbors called me into his room to see something on the six o'clock news. Apparently, an unidentified man had been sighted running stark naked down North High Street, screaming, "I AM THE NEXT AVAILABLE SERVICE REPRESENTATIVE!" at the top of his lungs.
None of us ever saw him after that, but to this day, if you listen hard enough late at night, you can still hear a recorded voice saying, "Your call is important to us. Please stay on the line and wait for the next available service representative."
Note: This is a serious question and not a troll.
The code that allows Windows to antialias fonts appears to be in the form of a bunch of DLLs. Would it be possible to write a new DLL that uses the (obviously superior) antialiasing algorithm that's now becoming available under X?