Kind of hard to teach a company a lesson by leaving them when they are a monopoly.
Many people have exactly 2 options for ISPs: Cable and DSL.
What if both are evil? How do I switch to a better company in that case?
(My solution is to have the ISP/content provider be legally prevented from having a share of the "last-mile" stuff, so that you can have competition in the ISP space, and then last-mile provider has many requirements, like no filtering of any kind, upgrades every so often, a specified maximum fee structure, etc.)
Or are they doing all this for show, and there is no real substance in OOXML?
The reason MS is bothering with ISO is because a few places have started to require that documents be stored in an ISO defined format.
The problem is that having a true ISO defined format means that you open yourself up to competition, so MS wants to get their format defined as ISO certified without allowing any competition.
I don't quite know what you mean. The court enforced the GPL license as it is written, and GPL is easily available. It isn't like Verizon couldn't see that the code was under the GPL, or what the GPL says.
If a company can't have someone look over a license to see if they want to accept it, then they probably shouldn't be using GPLd code.
Or do companies just blindly accept any sort of contract you send their way?
This also means that if a company wants to release code under the GPL, there is some precedent for enforcing it against someone else that uses the code without releasing their changes.
How is this different from a pantent troll? Create a program, GPL it, wait for some company to use it, and sue?
Except in this case the license is *right there* in the code they used. Also, they weren't prevented from writing something functionally similar to BusyBox.
Basically, Patents != Copyrights.
IP is "Imaginary Property" that doesn't actually exist or have any laws on it.
Ooh, look, little Johnny is acting a little weird! Quick, get a DNA sample from him, he could be a future criminal!
Sure it makes sense: Nobody thinks their precious little snowflake is going to be caught by that, so they want to defend their child against the evil little children.
(we don't even use PHP, so this is probably coming from other hacked servers that are running php)
The "feature" they are trying to exploit there is just crazy: If var in that case is used as a file name in a script load call, PHP will happily download the script from that website and run it instead of the local file that was expected. There are a bunch of problems with what is going on there, since having a file name in the url is just horrible, but then for the language to then take a url and download the file automatically is even worse.
Some PAL TVs use double scan, so they flash the same frame twice, getting 100Hz, which is quite a bit better than 60Hz. I wished I could find a double scan NTSC TV for a while, then I just got a LCD TV.
Replying to myself to add some more information about the Tmote Sky and similar wireless sensor nodes:
The main problem with these sensor nodes right now is mainly that they are just way too expensive for what they are, at $140 each. Since any application of them is in large numbers to get around the 10-meter radio range, it gets very expensive quickly to do anything really useful with them. That is $140 for a device that doesn't have a screen, case, keyboard or external antenna.
The goal is to get the cost under $1 per unit, which would allow them to be used in larger numbers. Right now people are developing OSs and software for them with the idea that they will become much cheaper in the future.
(Detailed picture with annotations on the components here
A wireless sensor node like the Tmote Sky(pdf) is a very tiny embedded computer that runs on 2 AA batteries, and is usually the size of the back of the 2 AA battery holder. They have a radio on it, but the radio isn't compatible with 802.11b instead compatible with 802.15.4, and is limited to about 256kbps. The Tmote Sky has a 8MHz 8-bit processor (the Atmega 128), 10KiB of ram, 1024KiB of flash, with a few A-D inputs and some digital outputs. It isn't exactly very fast, nor does it have a bunch of ram.
It is designed for a distributed sensor platform, and not doing a lot of computation.
A picture of one is here, connected to a 14-foot USB cable.
Well, I always have about 10 terminals open, so it is right there. And I like using the command line.
And, your Friday is better than mine:
There IS an A record right there in my query, with the IP of 208.69.32.130. Just that IP doesn't have a HTTP server on it. It has a TTL of 0, so it is looks like it might change often.
I was actually wrong with my original comment: the GPLONLY stuff is actually some functions that are only available to gpl modules, and this doesn't have anything to do with making the kernel tainted.
As for loading a non-gpl module, that makes your kernel "tainted", and generally kernel maintainers will not even accept a bug report for something that has to do with a "tainted kernel".
I didn't mean that the kernel maintainers would jump to fix the issue, but with a tainted kernel, like using the nvidia module, you generally can't submit kernel bug reports.
And, as you say, NDISWrapper is quite similar to the nvidia wrapper.
Doesn't that violate the copyright on the page held by
Kind of hard to teach a company a lesson by leaving them when they are a monopoly.
Many people have exactly 2 options for ISPs: Cable and DSL.
What if both are evil? How do I switch to a better company in that case?
(My solution is to have the ISP/content provider be legally prevented from having a share of the "last-mile" stuff, so that you can have competition in the ISP space, and then last-mile provider has many requirements, like no filtering of any kind, upgrades every so often, a specified maximum fee structure, etc.)
It is just like all of the new patents related to the internet and computers:
Laws are different when it is "on the internet", or "using a computer"
Reading mail not intended for you isn't a problem, "on the internet"
I agree with you that it shouldn't be like that at all, though.
I don't think it would be diving by N on every cycle, but adding 1 to a counter, and when the counter equals N, you do one of the low-frequency cycle.
Standard Oil would be prior art for the "Bag o' cash".
Any system where a person can verify their vote after it has been cast is open to a very real kind of attack:
"Vote for #{my_candidate} or you are fired. Signed, your boss"
Or, husband, wife, mother, creepy guy standing outside the polling place, etc.
Or are they doing all this for show, and there is no real substance in OOXML?
The reason MS is bothering with ISO is because a few places have started to require that documents be stored in an ISO defined format.
The problem is that having a true ISO defined format means that you open yourself up to competition, so MS wants to get their format defined as ISO certified without allowing any competition.
I don't quite know what you mean. The court enforced the GPL license as it is written, and GPL is easily available. It isn't like Verizon couldn't see that the code was under the GPL, or what the GPL says.
If a company can't have someone look over a license to see if they want to accept it, then they probably shouldn't be using GPLd code.
Or do companies just blindly accept any sort of contract you send their way?
This also means that if a company wants to release code under the GPL, there is some precedent for enforcing it against someone else that uses the code without releasing their changes.
How is this different from a pantent troll? Create a program, GPL it, wait for some company to use it, and sue?
Except in this case the license is *right there* in the code they used. Also, they weren't prevented from writing something functionally similar to BusyBox.
Basically, Patents != Copyrights.
IP is "Imaginary Property" that doesn't actually exist or have any laws on it.
Ooh, look, little Johnny is acting a little weird! Quick, get a DNA sample from him, he could be a future criminal!
Sure it makes sense:
Nobody thinks their precious little snowflake is going to be caught by that, so they want to defend their child against the evil little children.
Easy solution:
"I really like everything except steak and stout."
Honestly
At my work, we see a bunch of attempts to exploit PHP every week, usually like this: (we don't even use PHP, so this is probably coming from other hacked servers that are running php)
The "feature" they are trying to exploit there is just crazy:
If var in that case is used as a file name in a script load call, PHP will happily download the script from that website and run it instead of the local file that was expected. There are a bunch of problems with what is going on there, since having a file name in the url is just horrible, but then for the language to then take a url and download the file automatically is even worse.
From, quite approiately enough, The Daily WTF
Some PAL TVs use double scan, so they flash the same frame twice, getting 100Hz, which is quite a bit better than 60Hz.
I wished I could find a double scan NTSC TV for a while, then I just got a LCD TV.
Replying to myself to add some more information about the Tmote Sky and similar wireless sensor nodes:
The main problem with these sensor nodes right now is mainly that they are just way too expensive for what they are, at $140 each. Since any application of them is in large numbers to get around the 10-meter radio range, it gets very expensive quickly to do anything really useful with them. That is $140 for a device that doesn't have a screen, case, keyboard or external antenna.
The goal is to get the cost under $1 per unit, which would allow them to be used in larger numbers. Right now people are developing OSs and software for them with the idea that they will become much cheaper in the future.
(Detailed picture with annotations on the components here
A wireless sensor node like the Tmote Sky(pdf) is a very tiny embedded computer that runs on 2 AA batteries, and is usually the size of the back of the 2 AA battery holder. They have a radio on it, but the radio isn't compatible with 802.11b instead compatible with 802.15.4, and is limited to about 256kbps. The Tmote Sky has a 8MHz 8-bit processor (the Atmega 128), 10KiB of ram, 1024KiB of flash, with a few A-D inputs and some digital outputs. It isn't exactly very fast, nor does it have a bunch of ram.
It is designed for a distributed sensor platform, and not doing a lot of computation.
A picture of one is here, connected to a 14-foot USB cable.
Ah, thanks. I did think that might be because of opendns.
Yay for fucked up DNS results.
Well, I always have about 10 terminals open, so it is right there. And I like using the command line.
And, your Friday is better than mine:
There IS an A record right there in my query, with the IP of 208.69.32.130. Just that IP doesn't have a HTTP server on it. It has a TTL of 0, so it is looks like it might change often.
Actually, water can be toxic, and lethal if enough is ingested.
That has nothing to do with explosives or planes, though.
That surprises you?
This is TSA: even water is a dangerous substance, except when you throw it away.
Just like how "think of the children" is a useful phrase for fucking over the American people's rights.
"Free speech" - "Think of the children", by the FCC
"Marijuana/drugs" - "Think of the children", by the DOJ
So, combine "think of the children" and "terrorists", and the Constitution becomes irrelevant.
Someone coped that article about Darrin McGillis to wikitruth.info.
I have no idea why Jim Wales would get rid of that article and perma-ban anyone connected with it. That is just bizzare.
And that sounds just like Ron Paul's entire platform.
Why not have a monetary penalty awarded to the victim from the budget of the agency?
Like $1000 per incorrectly tapped phone call? (Not per tap, but per call that occurred while that tap was in place.)
I was actually wrong with my original comment: the GPLONLY stuff is actually some functions that are only available to gpl modules, and this doesn't have anything to do with making the kernel tainted.
As for loading a non-gpl module, that makes your kernel "tainted", and generally kernel maintainers will not even accept a bug report for something that has to do with a "tainted kernel".
I didn't mean that the kernel maintainers would jump to fix the issue, but with a tainted kernel, like using the nvidia module, you generally can't submit kernel bug reports.
And, as you say, NDISWrapper is quite similar to the nvidia wrapper.