In that context, this usage of a DMCA takedown makes sense and is completely appropriate.
Sorry, but a DMCA takedown notice doesn't make sense. The site is Canadian (so no DMCA, lack of jurisdiction), and the use of the video conforms to Canadian copyright laws wrt news.
DMCA notices only affect 5% of the worlds' population.
And the Canadians got LOTS of practice runs while the course was closed to the rest of the world. Not fair at all, and the lack of adequate practice time on a course that others have said is "stupid fast" was definitely a contributing factor to the death.
http://www.njnnetwork.com/?p=33411Here's the site (and the video) in question. Don't just watch it - listen to it! You can HEAR him bouncing off the metal columns.
Vancouver was supposed to do that with a portion of the village to go as low-cost housing but last I heard the new plan is to sell it as expensive condo's.
WILMINGTON, Del. - Whistler Blackcomb won't go on the block in a foreclosure auction on Friday as scheduled, winning a one-week reprieve from creditors, a source with direct knowledge of the talks said on Thursday.
Creditors of Intrawest Holdings, which owns stakes in Whistler Blackcomb resort, the site of downhill events during the Vancouver Olympics, agreed to delay the auction from Friday until Feb. 26, two days before the end of the Olympics.
The agreement delays the auction until after the marquee men's combined downhill event at Whistler, which will feature American Bode Miller. That event is scheduled to end on Feb. 22.
Intrawest and its owner, U.S. private equity equity firm Fortress Investment Group LLC FIG.N, have been haggling with creditors over refinancing the $1.7 billion of debt Fortress took on in buying Intrawest in 2006.
Intrawest holdings also include Squaw Valley in California and Steamboat and Winter Park in Colorado, and it has sold off other resorts in recent months as it reorganizes its finances.
Olympic officials have dismissed talk of a foreclosure as nothing more than a minor distraction and they are not worried that Intrawest's financial situation will disrupt Olympic events at Whistler.
"For the athletes it would be a non-issue. It would be an esoteric business issue beyond anything they would think about (on the hill)," said Chris Rudge, secretary general of the Canadian Olympic Committee.
Vancouver Games Organizers say it was unlikely any of the parties involved in the financial discussion would try to disrupt the Olympics or the Paralympics in March, because that would only reduce Whistler's potential value.
Games organizers have an agreement to compensate Whistler for any business lost because of the Games, which utilize only a small portion of the resort. The amount of compensation has yet to be determined.
yes, but if it follows the general trend of technology, better units will be less expensive in just a few years. Its always more expensive for first movers
Not true at all. Let's take a look at the most high-tech consumer good - the modern automobile, with multiple computers, many advanced materials, etc.
If we applied Moores law to it, the same car that sold new for $2000 in 1972 and got 20mpg should now only cost me $0.00000745 (yes, I actually did this on a spreadsheet just to see what the answer is).
Even if we were to posit that today's care is 1,000 x better than the car from 40 years ago (it's not - it doesn't have 1,000 times the capacity, nor does it get 20,000 mpg), it should still cost only 0.00745, or less than a penny.
The problem is that "economies of scale", etc., in one area are not directly translatable to other areas. This is certainly true with bloom boxes, or other high-capital-cost, bulky machinery. Now if you could shrink it so that each subsequent generation required half the materials, etc., you could get the cost down - but you'd also be increasing the energy density to the point where even ceramics melt. In other words, there is a built-in limitation to how dense you can make this device, and how much you can save in subsequent generations.
My wife recently discovered that some big PDFs and images she had were being hotlinked to a forum and was getting perilously close to going over our bandwidth,
And you didn't do a "cp goatse.pdf interesting_stuff.pdf", after adjusting your local links to point to another copy of interesting_stuff.pdf?
It would have saved you a ton of bandwidth (its not just the cost, which as you point out is minimal, but also the server load, which affects all your users).
New discoveries in math have nothing to do with the average high school graduate not being able to make change at the 7-11.
These new discoveries were not made by high school students who can't count.
So, your point is not relevant to the issue, any more than crediting the declining ability of people to string coherent sentence together can be credited to the flourishing of new genres of science fiction.
I did the upgrade-in-place thing as well (11.1 -> 11.2), with no problems. Well, there was one weird one - it swapped my dual monitors left-to-right on reboot, so I fixed it manually, and it swapped them again... in other words, I should have just done the old ctl+alt+bksp thing to restart the x server a second time after the reboot, and it would have been okay.
No, I thought of that and checked the numbers. Anything between 10.05 hours and 11.95 hours in a day had exactly 1 full hour added to it. Very badly done.
And then those days that went over 12 hours, guess who gets screwed?
It got to be a running joke. The accountant would print out the time sheets, and we'd spend half an hour reconciling them (because they were THAT badly done) before handing them back in. It ended up costing a lot of money in wasted time (not to mention that I was the only one who bothered to correct the over-payments as well as the under-payments, so I don't know how many thousands in over-payments were made to everyone else...)
I'm not a clock-watcher - I usually rounded my time in the following fashion: If I came in at 8:05 am, I'd mark my starting time as 8:15 am. If I left at 7:05 pm, I'd mark my exit time as 7:00 pm. On average, I under-reported about 15 minutes a day, or a couple of hours every two weeks. No big deal, because I enjoy coding.
When they put in the time clock, all of a sudden I'm no longer "rounding" in their favour, so it actually ended up costing them an extra hours pay for the same amount of work. When they asked why I, unlike everyone else, didn't hate the time-clock, I explained that it meant I was accumulating an extra 4 to 6 hours a month of bankable time off for the same amount of work, so why should I complain?
If you want to try something that works almost all the time, get slack.
If you can get that up and running, it gives you a baseline. It usually works even with machines that are somewhat funky due to, for example, bad cpu clockings.
Let us know how it went, either here or via email. Hope this helps.
The problem with that, (and others have also pointed it out) is that if it looks too much like Windows, then people will expect it to work like Windows.
That means that not only will they get frustrated over the parts that work differently, they also lose out on the parts that work better because they just assume the more limited functionality.
It would be like giving someone a laptop and not telling them that they now have wireless Internet access and they don't HAVE to be plugged into the wall to use it.
Or, for a bad car analogy, swapping their summer tires for top-of-the-line snow tires right before the first snowfall and not telling them, and then watching them refuse to take the car out because "it's snowing."
... and I'm from East Kanuckistan (also known as PoutineVille:-)
The schools lost the ability to teach mathematics properly a couple of decades ago, starting with the "new math" in grade school and the "dumbing down" of math in high school.
Grading to the curve just sealed the deal. But like a bad TV infomercial - BUT WAIT! THERE'S MORE! By insisting that students solve all problems using calculators, students lost the ability to guestimate what range an answer should be in. We see the effects of this today, from cashiers unable to make change to people not realizing that the "answer" they got is obviously off by several orders of magnitude.
I'm not saying slide rules were all that great - but to use one you at least had to have some idea of what range your answer should be in before you did the calculations.
Memo is just slang for "memorandum", which can be as short or as long as required. Just head over to Groklaw and look at the various filings. Gee, look - multi-page memos.
Memos can be quite detailed, including all sorts of things, such as who was present, who discussed each point raised, what agreements were reached, justifications for same, etc.
After the first two weeks, it kept saying (in a REALLY annoying voice) "Please try again..." "Please try again..." "Please try again..." "Please try again..."
It was tempting to just hack into the PC it was running on and just update the stupid database manually, but that would have been too much work to maintain, running after everyone and asking them what hours they wanted to show on the timesheet.
And if you did more than 12 hours, it got confused.
And if you forgot to punch out the night before, it would SAY you were punching out the next morning when you punched in, but in reality it was punching you in, since you had exceeded the 12-hour limit. So people would quickly "correct" it by punching in, and it would SAY that they were now punched in, but in reality they just punched out. And 8 hours later, when the went to punch out... it would say they just punched in.
And it didn't update when the time changed between DST and EDT, and vice versa.
After a few weeks of that, it's understandable that people began beating on it.
It also must have had a math aversion - it couldn't add up time properly. I would take the numbers on the print-out, add them up manually, and get an hour LESS than I was being credited for. It can't add. Not if one day had 10 or more hours worked, but less than 12 - it would throw in an extra hour, giving 11 hours worked. for example, a 4-day week, 4 x 10 hours, is not 44 hours.
Multi-function devices can be a bear. Support for them is usually late, because the manufacturers think that a 10-year-old linux driver is good enough to say "linux-compatible" on the box.
Slashdot Mirror
Is this the first slashdot article that mentions nazis right in the title?
Sorry, but a DMCA takedown notice doesn't make sense. The site is Canadian (so no DMCA, lack of jurisdiction), and the use of the video conforms to Canadian copyright laws wrt news.
DMCA notices only affect 5% of the worlds' population.
And the Canadians got LOTS of practice runs while the course was closed to the rest of the world. Not fair at all, and the lack of adequate practice time on a course that others have said is "stupid fast" was definitely a contributing factor to the death.
http://www.njnnetwork.com/?p=33411Here's the site (and the video) in question. Don't just watch it - listen to it! You can HEAR him bouncing off the metal columns.
http://www.njnnetwork.com/?p=33242Letterman had it right.
It's all up in the air again because the venue is bankrupt and goes on the auction block in a week.
*cough* Toyota brakes *cough*
Accidents and fatalities haven't dropped by 99.99%.
It's not thrown away - look at LNG bulk tankers, pipelines, etc.
Not true at all. Let's take a look at the most high-tech consumer good - the modern automobile, with multiple computers, many advanced materials, etc.
If we applied Moores law to it, the same car that sold new for $2000 in 1972 and got 20mpg should now only cost me $0.00000745 (yes, I actually did this on a spreadsheet just to see what the answer is).
Even if we were to posit that today's care is 1,000 x better than the car from 40 years ago (it's not - it doesn't have 1,000 times the capacity, nor does it get 20,000 mpg), it should still cost only 0.00745, or less than a penny.
The problem is that "economies of scale", etc., in one area are not directly translatable to other areas. This is certainly true with bloom boxes, or other high-capital-cost, bulky machinery. Now if you could shrink it so that each subsequent generation required half the materials, etc., you could get the cost down - but you'd also be increasing the energy density to the point where even ceramics melt. In other words, there is a built-in limitation to how dense you can make this device, and how much you can save in subsequent generations.
You mean we can't just hook these bloom boxes up to our congressional methane supply? I thought pork production produced LOTS of methane.
Well, unless you're into reincarnation or something like that, I don't think it's even possible to care after you're dead and gone.
They don't run on air - they need a source of methane. Your local pig wallow isn't going to be big enough - so you're still using fossil fuels.
In other words, they have a negative ROI.
And of course security is not something you can buy, any more than trust.
With that in mind, here's a stat that Symantec doesn't want you to know:
100% of the companies that depend on Symantec to make them secure are vulnerable.
And you didn't do a "cp goatse.pdf interesting_stuff.pdf", after adjusting your local links to point to another copy of interesting_stuff.pdf?
It would have saved you a ton of bandwidth (its not just the cost, which as you point out is minimal, but also the server load, which affects all your users).
Is it too late?
New discoveries in math have nothing to do with the average high school graduate not being able to make change at the 7-11.
These new discoveries were not made by high school students who can't count.
So, your point is not relevant to the issue, any more than crediting the declining ability of people to string coherent sentence together can be credited to the flourishing of new genres of science fiction.
... because I can troll^wblog with the best of them :-)
I did the upgrade-in-place thing as well (11.1 -> 11.2), with no problems. Well, there was one weird one - it swapped my dual monitors left-to-right on reboot, so I fixed it manually, and it swapped them again ... in other words, I should have just done the old ctl+alt+bksp thing to restart the x server a second time after the reboot, and it would have been okay.
No, I thought of that and checked the numbers. Anything between 10.05 hours and 11.95 hours in a day had exactly 1 full hour added to it. Very badly done.
And then those days that went over 12 hours, guess who gets screwed?
It got to be a running joke. The accountant would print out the time sheets, and we'd spend half an hour reconciling them (because they were THAT badly done) before handing them back in. It ended up costing a lot of money in wasted time (not to mention that I was the only one who bothered to correct the over-payments as well as the under-payments, so I don't know how many thousands in over-payments were made to everyone else ...)
I'm not a clock-watcher - I usually rounded my time in the following fashion: If I came in at 8:05 am, I'd mark my starting time as 8:15 am. If I left at 7:05 pm, I'd mark my exit time as 7:00 pm. On average, I under-reported about 15 minutes a day, or a couple of hours every two weeks. No big deal, because I enjoy coding.
When they put in the time clock, all of a sudden I'm no longer "rounding" in their favour, so it actually ended up costing them an extra hours pay for the same amount of work. When they asked why I, unlike everyone else, didn't hate the time-clock, I explained that it meant I was accumulating an extra 4 to 6 hours a month of bankable time off for the same amount of work, so why should I complain?
The law of unintended consequences strikes again.
If you want to try something that works almost all the time, get slack.
If you can get that up and running, it gives you a baseline. It usually works even with machines that are somewhat funky due to, for example, bad cpu clockings.
Let us know how it went, either here or via email. Hope this helps.
That means that not only will they get frustrated over the parts that work differently, they also lose out on the parts that work better because they just assume the more limited functionality.
It would be like giving someone a laptop and not telling them that they now have wireless Internet access and they don't HAVE to be plugged into the wall to use it.
Or, for a bad car analogy, swapping their summer tires for top-of-the-line snow tires right before the first snowfall and not telling them, and then watching them refuse to take the car out because "it's snowing."
What can I say ... this account has too much good karma to just dump ... (and you'll find out what t.o.m. means if you look at my user profile)
The schools lost the ability to teach mathematics properly a couple of decades ago, starting with the "new math" in grade school and the "dumbing down" of math in high school.
Grading to the curve just sealed the deal. But like a bad TV infomercial - BUT WAIT! THERE'S MORE! By insisting that students solve all problems using calculators, students lost the ability to guestimate what range an answer should be in. We see the effects of this today, from cashiers unable to make change to people not realizing that the "answer" they got is obviously off by several orders of magnitude.
I'm not saying slide rules were all that great - but to use one you at least had to have some idea of what range your answer should be in before you did the calculations.
Let me take a guess - you're running crapuntu?
please install a real linux (not a bastardized version) and try again ... it lists fine on mine.
And you'd be wrong.
Memo is just slang for "memorandum", which can be as short or as long as required. Just head over to Groklaw and look at the various filings. Gee, look - multi-page memos.
Memos can be quite detailed, including all sorts of things, such as who was present, who discussed each point raised, what agreements were reached, justifications for same, etc.
There's no set format to the length of a memo.
After the first two weeks, it kept saying (in a REALLY annoying voice) "Please try again ..." "Please try again ..." "Please try again ..." "Please try again ..."
It was tempting to just hack into the PC it was running on and just update the stupid database manually, but that would have been too much work to maintain, running after everyone and asking them what hours they wanted to show on the timesheet.
And if you did more than 12 hours, it got confused.
And if you forgot to punch out the night before, it would SAY you were punching out the next morning when you punched in, but in reality it was punching you in, since you had exceeded the 12-hour limit. So people would quickly "correct" it by punching in, and it would SAY that they were now punched in, but in reality they just punched out. And 8 hours later, when the went to punch out ... it would say they just punched in.
And it didn't update when the time changed between DST and EDT, and vice versa.
After a few weeks of that, it's understandable that people began beating on it.
It also must have had a math aversion - it couldn't add up time properly. I would take the numbers on the print-out, add them up manually, and get an hour LESS than I was being credited for. It can't add. Not if one day had 10 or more hours worked, but less than 12 - it would throw in an extra hour, giving 11 hours worked. for example, a 4-day week, 4 x 10 hours, is not 44 hours.
If you're stuck, email.