As long as they believed "in good faith" that the material was infringing they'll get off scott free. The bar for proving bad behavior on the claimants part is extremely high.
Github isn't going to drive out to the address you wrote in there to verify that you are who you say you are. They're going to hit "reply" in the email. To date I know of no entity that has been punished for fradulant DMCA takedowns more than a written admonishment. The law is utterly one sided because it was written by people who were intending to use it to send millions of takedown requests. They didn't want any possibily of suffering legal liability if they could get away with it, so the sender only has to hurdle the lowest legal hurdle (good faith) to completely indemnify themselves against counter claims. The law was written to be abused, and shock, people are abusing it.
Either that of you could read it as "Jesus Christ, an email? Why didn't you just hand type it and deliver it? You want to leave a paper trail?!?! Just how new are you to lobbying? Never leave a paper trail that the rules guys might find, they're total buzzkills. By the way, I'll be at the country club next Thursday if you want to discuss anything--it's not bugged."
Even more fun was when people entered the Unicode character that reverses the following text on the page.
That said, sanitizing problematic characters seems like a far more reasonable solution than throwing the baby out with the bathwater because Unicode is scary.
I did think it was weird that T-Mo was the one getting slammed for this when of the three carriers I've had, they were by far the best at handling it. AT&T and Verizon were way worse about having those stupid things appear and making them difficult to remove.
1TB of storage is 1TB of storage. I have several spinning rust platters that are older than that just because they keep doing their job and don't give me any trouble. Plus hard drives really stalled out there for a couple of years after the Typhoon hit and SSDs exploded onto the scene.
I bought an 840 Evo 1TB for $450 on sale a couple of weeks ago. Granted, this is a TLC drive and will probably fail early, but it broke the $0.50 price barrier and has been excellent thus far.
You forget that in modern RE, '.' is a wildcard as well. *.* is a bastard of old and new styles, but most shells will take it and run with it, happily globbing every single thing in the directory.
The -f flag to rm should be using sparingly. Also, people just learning how to work on machines should not have administrator accounts.
They didn't technically steal anything yet. Kickstarter doesn't release funds until the end of the campaign, so they've gotten zilch thus far. They might get hit by some false advertising fine or something, but I doubt they're going to see any jail time.
It seems like his solution is: Simply don't release code that has bugs in it. Which is kind of like saying that the airline industry would be so much more efficient if we could just get rid of wind resistance.
If you want to be pedantic they were also sharing the same power source and signal on the air. Aereo doesn't use DVRs either, each antenna has its own dedicated encoder that spits out compressed video packets to the end user. If you want to start arguing that they're sharing internet access, I'll just point out that you're either wrong (you are because they don't pack multiple customers data into individual packets) or all video streaming on the internet is illegal.
But mostly you're violently agreeing with me. Aereo was ruled to be a cable service, and must be shut down. Well, I guess technically they could negotiate internet broadcast rights with the channels, but it will be a cold day in hell before they agree to that. Aereo is fucked, big corporations win again, potential threats to obsolete business models are averted. Good job Supreme Court.
Aren't Aereo antennas storing TV signal content on servers and retransmitting/uploading that content to multiple members of the public? That's what's prohibited by copyright law, according to the broadcasters.
No. When you activate the Aereo service, you are assigned a dedicated (not shared) antenna and the video is streamed from that antenna to your device. There is no storing or sharing of anything.
IMHO, this ruling was not surprising. The justices were openly hostile to Aereo and saw it as basically someone setting up a cable company without following the rules set up for cable companies--mostly the part where cable companies pay local stations for the content they rebroadcast. The thousands of tiny antennas did not impress the judges.
Re:Perl 6ers just can't get shit done.
on
Perl Is Undead
·
· Score: 1
I don't think there's a second-system effect going on with Perl 6. Every two or three years some new team has come along and tried to implement it, only to totally fail and produce nothing usable. These people didn't implement Perl 5, so I don't think we can say that Perl 6 is a second attempt for them.
Nope, this is exactly what happens with the Second System effect. Everybody gathered up all of the ideas that percolated and were grafted on to Perl 5 and wrote a huge requirements document for the next version. Then when people try to implement it they discover that it takes way more effort than they expected and fail. Repeat a few more times and you have a language that either never comes out, or finally appears from a single vendor and costs a small fortune because they had to pour so many man hours into it. Even then it's buggy and slow and most people never touch 90% of the features because it's way too big to grok and even the reference manual is a monster. Plus, a lot of the tertiary features are poorly tested and likely buggy.
The proper solution is to build a small(ish) but relatively clean core language and have a robust module system to let people pull in only the features they need, and to let developers focus on relatively small parts of the design and get it right. Perl5 actually does a pretty good job of this, but it could use some fixes here and there.
Requirements documents are a two edged sword. Without them you end up with a hodgepodge language (see: Perl 5), but it's a lot easier to write requirements than it is to fulfill them. Put too many in there and the system becomes colossally expensive to build. This is the primary reason Government work is so inefficient, because simply writing the requirements and then verifying that they were followed is an enormous job, and training everybody in what their specific requirements are is also a massive undertaking.
I don't think we're ever going to get as clear of an example of the second system effect as Perl 6. If you asked me back in 2005 if I thought it was going to take more than a decade for the next Perl version bump, I would have said no way. Now I'm wondering if Larry and company shouldn't just ditch Perl 6 and come out with Perl 7, that is basically just Perl 5 with some tweaks to make complex data structures less of a nightmare and better integrate the object model, plus some tweaks around the edges like the implicit/x switch on regular expressions.
The devil is in the details I guess. It wouldn't be practical to regulate every single person who drives a car, but regulation for car companies is something that could make a big difference.
Yes, back in the 70s. Fourty years ago. They have not been commonplace for decades. That's why I was impressed that they still exist and are were apparently still being updated. The x86 of today is almost nothing like a 8008 except for supporting it via microcode translation if someone wants to run some really old code. Chip development is expensive, you can't support it with a tiny niche market forever. At some point it becomes more efficient to just build an emulator that runs on x86, which is I think the path forward for any of these old applications. Emulating the 36 bit architecture in a 64 bit architecture shouldn't be too bad, although the 1-s complement math will be a problem if stuff depends on the overflow behavior or uses a lot of negative zeros.
Certificates are renewed on multi-year timeframes. We're talking about 2 months here, relatively few of the websites in question would have needed to re-up their certs.
Slashdot Mirror
As long as they believed "in good faith" that the material was infringing they'll get off scott free. The bar for proving bad behavior on the claimants part is extremely high.
Github isn't going to drive out to the address you wrote in there to verify that you are who you say you are. They're going to hit "reply" in the email. To date I know of no entity that has been punished for fradulant DMCA takedowns more than a written admonishment. The law is utterly one sided because it was written by people who were intending to use it to send millions of takedown requests. They didn't want any possibily of suffering legal liability if they could get away with it, so the sender only has to hurdle the lowest legal hurdle (good faith) to completely indemnify themselves against counter claims. The law was written to be abused, and shock, people are abusing it.
Either that of you could read it as "Jesus Christ, an email? Why didn't you just hand type it and deliver it? You want to leave a paper trail?!?! Just how new are you to lobbying? Never leave a paper trail that the rules guys might find, they're total buzzkills. By the way, I'll be at the country club next Thursday if you want to discuss anything--it's not bugged."
Even more fun was when people entered the Unicode character that reverses the following text on the page.
That said, sanitizing problematic characters seems like a far more reasonable solution than throwing the baby out with the bathwater because Unicode is scary.
Ah, that makes more sense. I thought this was one of the TV viewing optimized tablets, not a set top box.
He must have left his Kindle plugged in constantly. Sucking down 80GB over WiFi every day is a sure way to kill the battery.
I did think it was weird that T-Mo was the one getting slammed for this when of the three carriers I've had, they were by far the best at handling it. AT&T and Verizon were way worse about having those stupid things appear and making them difficult to remove.
1TB of storage is 1TB of storage. I have several spinning rust platters that are older than that just because they keep doing their job and don't give me any trouble. Plus hard drives really stalled out there for a couple of years after the Typhoon hit and SSDs exploded onto the scene.
I bought an 840 Evo 1TB for $450 on sale a couple of weeks ago. Granted, this is a TLC drive and will probably fail early, but it broke the $0.50 price barrier and has been excellent thus far.
Well of couse the Solar guys were in trouble, they were in Portland. Solar doesn't work so well when it's always overcast.
It's built into getopt now I think, so anything that uses getopt should automatically support it.
You forget that in modern RE, '.' is a wildcard as well. *.* is a bastard of old and new styles, but most shells will take it and run with it, happily globbing every single thing in the directory.
The -f flag to rm should be using sparingly. Also, people just learning how to work on machines should not have administrator accounts.
They didn't technically steal anything yet. Kickstarter doesn't release funds until the end of the campaign, so they've gotten zilch thus far. They might get hit by some false advertising fine or something, but I doubt they're going to see any jail time.
Do you have a link explaining how to do this? Maybe a link to the community? I wouldn't mind getting Kohan working again.
And there would be no software, expect for the stupidly expensive stuff that does very little.
It seems like his solution is: Simply don't release code that has bugs in it. Which is kind of like saying that the airline industry would be so much more efficient if we could just get rid of wind resistance.
What do you mean? He voted same as Scalia and didn't say anything. Classic Thomas.
If you want to be pedantic they were also sharing the same power source and signal on the air. Aereo doesn't use DVRs either, each antenna has its own dedicated encoder that spits out compressed video packets to the end user. If you want to start arguing that they're sharing internet access, I'll just point out that you're either wrong (you are because they don't pack multiple customers data into individual packets) or all video streaming on the internet is illegal.
But mostly you're violently agreeing with me. Aereo was ruled to be a cable service, and must be shut down. Well, I guess technically they could negotiate internet broadcast rights with the channels, but it will be a cold day in hell before they agree to that. Aereo is fucked, big corporations win again, potential threats to obsolete business models are averted. Good job Supreme Court.
No. When you activate the Aereo service, you are assigned a dedicated (not shared) antenna and the video is streamed from that antenna to your device. There is no storing or sharing of anything.
IMHO, this ruling was not surprising. The justices were openly hostile to Aereo and saw it as basically someone setting up a cable company without following the rules set up for cable companies--mostly the part where cable companies pay local stations for the content they rebroadcast. The thousands of tiny antennas did not impress the judges.
Nope, this is exactly what happens with the Second System effect. Everybody gathered up all of the ideas that percolated and were grafted on to Perl 5 and wrote a huge requirements document for the next version. Then when people try to implement it they discover that it takes way more effort than they expected and fail. Repeat a few more times and you have a language that either never comes out, or finally appears from a single vendor and costs a small fortune because they had to pour so many man hours into it. Even then it's buggy and slow and most people never touch 90% of the features because it's way too big to grok and even the reference manual is a monster. Plus, a lot of the tertiary features are poorly tested and likely buggy.
The proper solution is to build a small(ish) but relatively clean core language and have a robust module system to let people pull in only the features they need, and to let developers focus on relatively small parts of the design and get it right. Perl5 actually does a pretty good job of this, but it could use some fixes here and there.
Requirements documents are a two edged sword. Without them you end up with a hodgepodge language (see: Perl 5), but it's a lot easier to write requirements than it is to fulfill them. Put too many in there and the system becomes colossally expensive to build. This is the primary reason Government work is so inefficient, because simply writing the requirements and then verifying that they were followed is an enormous job, and training everybody in what their specific requirements are is also a massive undertaking.
I don't think we're ever going to get as clear of an example of the second system effect as Perl 6. If you asked me back in 2005 if I thought it was going to take more than a decade for the next Perl version bump, I would have said no way. Now I'm wondering if Larry and company shouldn't just ditch Perl 6 and come out with Perl 7, that is basically just Perl 5 with some tweaks to make complex data structures less of a nightmare and better integrate the object model, plus some tweaks around the edges like the implicit /x switch on regular expressions.
The devil is in the details I guess. It wouldn't be practical to regulate every single person who drives a car, but regulation for car companies is something that could make a big difference.
Yes, back in the 70s. Fourty years ago. They have not been commonplace for decades. That's why I was impressed that they still exist and are were apparently still being updated. The x86 of today is almost nothing like a 8008 except for supporting it via microcode translation if someone wants to run some really old code. Chip development is expensive, you can't support it with a tiny niche market forever. At some point it becomes more efficient to just build an emulator that runs on x86, which is I think the path forward for any of these old applications. Emulating the 36 bit architecture in a 64 bit architecture shouldn't be too bad, although the 1-s complement math will be a problem if stuff depends on the overflow behavior or uses a lot of negative zeros.
Certificates are renewed on multi-year timeframes. We're talking about 2 months here, relatively few of the websites in question would have needed to re-up their certs.
ECM? Do you mean EDM?