Fraud, easily. Treason, with a great torture (no pun intended) of the laws (is this an act of war against the US? We'd have to prove some sort of intent). Gross (or criminal) negligience might be a much easier sell. IANAL, but I don't think it requires someone to actually die, merely contribute to the likelihood, recklessly. Not sure if that's on the books in the US (or the particular state involved here) though. Involuntary manslaughter is another option, but only if someone died and it can be (reasonably) tracked back to the subpar parts that were fraudulently sold to the military.
Oh, I don't know about that one. I mean, we surely aren't evolved to hold civilised, intelligent debate on the internet, so there really is only one other option, and we appear to be doing it.
Or another reasonable conclusion: the spokesperson did not, in fact, talk to every single developer who may have worked with the NSA to confirm that no back door was put in, and managed to get independent "third-party" developers to code-review everything to confirm this, thereby saying the truth as s/he knows it, which does not need to line up with objective truth as it really is.
I've failed to keep count of the number of times I see a press release from $work claiming that we do or do not do something that I know damned well falls short of the truth. They don't usually ask me.
I had that at one time. Then I moved to Linux. And, no, I wasn't using Windows. OS/2's Extended Attributes were awesome for this. They could only total 64KB per file, IIRC, but that's still an awful lot of meta data you could stuff in there. And all OS/2 programs that wanted to use attributes were aware of them, including the zip tools for OS/2, meaning that I could send a file to someone else running OS/2 and they'd have my metadata.
It's one of those features I still miss from OS/2.
Meme aside, I am. And, before it came out, I was running the 32-bit flash on Linux/AMD64 just fine, even with 64-bit browsers. At least under firefox. Under konqueror, konqueror would crash sometimes, though I've not had that crash in a while now - probably fixed in KDE 4.3.3.
FYI: nspluginwrapper is what you need to run 32-bit plugins with 64-bit firefox (and konqueror, and, presumably, chromium).
Better way: all the airplanes should be required to carry 72 UGLY virgins as stewardesses. When the Holy Terror sees he future reward, he'll give up.
I always thought that having all stewardesses be topless was the better idea. Not only would it dissuade the terrorists from even getting on the plane, it would easily triple the amount of business travel, restoring profitability to the airlines.
(and "client" and "server" roles were reversed from convention, for some strange reason)
What? Since when? I always thought that the X server was the behemoth application that ran, waiting for connections from other apps (the clients), consolidated the requests, acted on them, and responded back to those clients. You're telling me that X itself is termed the client, and those little apps that all connect to it are called servers? Yeah, that IS backwards!
Oh, hold it, that's not what you're saying at all. You think that "server" is a designation of the size of the machine it runs on, not a designation of the model of communication the application itself uses. You do realise, though, that even a "web server" (which could just be a wall wart acts as a client for DNS querying, right? That "client" and "server" are fluid terms based on what the app is doing, and not where it is?
A server responds to incoming request(s), usually from multiple sources. A client initiates those request(s), usually to a single target. That is all. X uses these terms perfectly. The application sitting on my desktop machine is the server, and the xterm I'm running on the Linux/zSeries box is the client. For this particular purpose. Of course, that Linux/zSeries box is also the ssh server that I use to connect to it in the first place, over which a tunnel is created in the reverse direction to allow that xterm to come up at all. It's not the convention that is being ignored. It's just that you're using the wrong definition.
I've had a shaw HD PVR for longer than I've had an HDTV. And the skip-30-seconds button works just nicely here. The reverse-15-second button, too. They're not perfect, but they're manageable, and they work.
It is, however, odd to play an episode that recorded like crap and had to be downloaded off the net and burned to CD/DVD. Each time I pavlovly reach for the remote control because a commercial break is coming, I'm already into the next scene.
But think of the children who would be nuked by terrorists if those operations were compromised! Do you want to be responsible for that? DO YOU????
That depends on which children, I suppose. If they were the children of my political adversaries, then it might not be so bad. Don't want my kids cavorting with the likes of them.
:-P <-- last time I was as half as dry in my sarcasm as the above I got someone thinking I was serious. Please don't.
How is "The Pirate Bay" any different from, say, the "Liberals" or "Conservatives" in Canada, which are almost identical politically, and both slightly left of centre? It's a tag, intended to deceive, not necessarily indicative of purpose. I doubt, for example, that the Democrats in the US actually are looking to change the political system to be a direct democracy rather than the republic it (almost) is. And some would argue that the "Labour" party in the UK isn't always fighting for the working man against their employers. Even Microsoft has made software for non-micro computers. Heck, they produce hardware (as I type this on a MS keyboard and a MS mouse is sitting beside me... they work well with Linux!).
Names are not always indicative of purpose.
On the other hand, I suspect that their About page might still be useful in deriving their purpose.
Even giving the benefit of the doubt and calling it 8 hours, that's still once a (working) day, or 5 times a (working) week. Still not acceptable.
Of course, extrapolating a statistic out of such a small sample size (2 or even 8 hours) is somewhat premature. That may have been the only crash in 10,000 hours, just so happens it was at the beginning. Or it normally would crash 5,000 times in a year, and he just went to "safe" sites. Neither extreme seems likely, but merely possible given the low sample size.
Chrome, though, shows that we should ask an additional question: what happens when one site crashes the browser? Does it take the whole thing (and all 11 of my open tabs) with it? Or do I just lose the one tab. This is important information when figuring out the severity of the problem, too.
Still not acceptable crash rate. I'm upset when I get one crash on my entire system per week. I'm upset when I have to reboot more than once every six months. If users have high standards, developers will have to have them, too.
Same in Alberta. But that doesn't mean that some of those fines don't make it back to the municipality which then funnels portions of it right back into the police force. That is, the higher the revenue from tickets, the higher the police force's budget. It's a direct causal link, written in black and white in the law.
Not if the loader is written to avoid it. Just because you're suid-root doesn't mean you can't drop privileges before doing anything useful, such as running something. Functions like setuid are your friend.
I would have thought the easiest way is to only allow the loader to operate (at least in ldd mode) if it's suid-root. Since no one but root can do that, the loader must have been vetted by either root or by the distro (where, honestly, any number of back doors can already be put in anyway).
Let's say that Nokia decided not to play ball, and just didn't bother researching. That, too, locks out small companies, because they can't afford the billion-dollar research budget to get there.
Or let's say that Nokia decided to hoard the information. After spending the $1B, they decided to keep it a secret and not license it to anyone. The only way to get the technology was to buy it pre-made from Nokia. That, too, locks out small companies who can't afford predatory pricing from the monopoly.
I'm not sure that small companies should get a free pass just because a big corp has spent a billion on R&D.
At least this way, Nokia is likely to license their patents (because that's the only way to survive - eventually the patent runs out and they can't exact any money for it) for much less than the R&D costs, allowing smaller companies to get into the market, while Nokia spreads the R&D cost over many licensees, and ends up with a return on their investment. With many licensees, it also provides for competition in the end marketplace that, though Nokia may get a cut on each phone, will pressure phone makers to keep their prices down, or to provide unique features of value to allow them to charge more. Either way, the consumer wins: cheap phones, or pricier phones that do other things.
Get the popcorn... this is going to be an epic thread. We've already had the "Wish I was there" post, it's time for the feminist wing to turn up. Oh the objectification!
Actually, the awkward part is where a coworker "accidentally" sent a link to this article to our entire organisation. Including managers, and managers' managers. I wonder what his yearly review will say...
If I am the author of a piece of work, I may choose to offer it to the general public under a license, say GPL, LGPL, Creative Commons, whatever. But, say someone with more cash than brains comes along and doesn't want those licenses. In exchange for some consideration (usually cash), I may choose to offer the same code, which I own the copyright to, to them under a different license. Simple.
In this case, it appears that, in exchange for some consideration (probably cash, but also a job), the author chose to SELL that copyright to a third party (Rapid7) and give up further claims to the code. This does not remove anyone else's rights to the code prior to the purchase, though it may not offer future updates under the old licenses (or it may, that's up to the new copyright owner).
In exchange, the original author gets a) a job, and b) the ability to work full time on the code base he's passionate about. And probably some cash.
As to other contributors - that all depends. If the license doesn't change, then no compensation is required. If they turn around and try to add additional licenses, then it may get sticky (e.g., a binary-only license so they can embed it, or LGPL so they can derive from it or whatever).
Slashdot Mirror
Fraud, easily. Treason, with a great torture (no pun intended) of the laws (is this an act of war against the US? We'd have to prove some sort of intent). Gross (or criminal) negligience might be a much easier sell. IANAL, but I don't think it requires someone to actually die, merely contribute to the likelihood, recklessly. Not sure if that's on the books in the US (or the particular state involved here) though. Involuntary manslaughter is another option, but only if someone died and it can be (reasonably) tracked back to the subpar parts that were fraudulently sold to the military.
Tell that to those who fall for the Nigerian scams that are spammed to everyone.
working [...] in your underwear.
Mind you, if that's part of the contract, you may want to turn it down anyway.
Oh, I don't know about that one. I mean, we surely aren't evolved to hold civilised, intelligent debate on the internet, so there really is only one other option, and we appear to be doing it.
Or another reasonable conclusion: the spokesperson did not, in fact, talk to every single developer who may have worked with the NSA to confirm that no back door was put in, and managed to get independent "third-party" developers to code-review everything to confirm this, thereby saying the truth as s/he knows it, which does not need to line up with objective truth as it really is.
I've failed to keep count of the number of times I see a press release from $work claiming that we do or do not do something that I know damned well falls short of the truth. They don't usually ask me.
I had that at one time. Then I moved to Linux. And, no, I wasn't using Windows. OS/2's Extended Attributes were awesome for this. They could only total 64KB per file, IIRC, but that's still an awful lot of meta data you could stuff in there. And all OS/2 programs that wanted to use attributes were aware of them, including the zip tools for OS/2, meaning that I could send a file to someone else running OS/2 and they'd have my metadata.
It's one of those features I still miss from OS/2.
I run 64-bit flash, you insensitive clod!
Meme aside, I am. And, before it came out, I was running the 32-bit flash on Linux/AMD64 just fine, even with 64-bit browsers. At least under firefox. Under konqueror, konqueror would crash sometimes, though I've not had that crash in a while now - probably fixed in KDE 4.3.3.
FYI: nspluginwrapper is what you need to run 32-bit plugins with 64-bit firefox (and konqueror, and, presumably, chromium).
Better way: all the airplanes should be required to carry 72 UGLY virgins as stewardesses. When the Holy Terror sees he future reward, he'll give up.
I always thought that having all stewardesses be topless was the better idea. Not only would it dissuade the terrorists from even getting on the plane, it would easily triple the amount of business travel, restoring profitability to the airlines.
(and "client" and "server" roles were reversed from convention, for some strange reason)
What? Since when? I always thought that the X server was the behemoth application that ran, waiting for connections from other apps (the clients), consolidated the requests, acted on them, and responded back to those clients. You're telling me that X itself is termed the client, and those little apps that all connect to it are called servers? Yeah, that IS backwards!
Oh, hold it, that's not what you're saying at all. You think that "server" is a designation of the size of the machine it runs on, not a designation of the model of communication the application itself uses. You do realise, though, that even a "web server" (which could just be a wall wart acts as a client for DNS querying, right? That "client" and "server" are fluid terms based on what the app is doing, and not where it is?
A server responds to incoming request(s), usually from multiple sources. A client initiates those request(s), usually to a single target. That is all. X uses these terms perfectly. The application sitting on my desktop machine is the server, and the xterm I'm running on the Linux/zSeries box is the client. For this particular purpose. Of course, that Linux/zSeries box is also the ssh server that I use to connect to it in the first place, over which a tunnel is created in the reverse direction to allow that xterm to come up at all. It's not the convention that is being ignored. It's just that you're using the wrong definition.
I've had a shaw HD PVR for longer than I've had an HDTV. And the skip-30-seconds button works just nicely here. The reverse-15-second button, too. They're not perfect, but they're manageable, and they work.
It is, however, odd to play an episode that recorded like crap and had to be downloaded off the net and burned to CD/DVD. Each time I pavlovly reach for the remote control because a commercial break is coming, I'm already into the next scene.
But think of the children who would be nuked by terrorists if those operations were compromised! Do you want to be responsible for that? DO YOU????
That depends on which children, I suppose. If they were the children of my political adversaries, then it might not be so bad. Don't want my kids cavorting with the likes of them.
:-P <-- last time I was as half as dry in my sarcasm as the above I got someone thinking I was serious. Please don't.
And now, with today's progress, that'd be CØBÖL.
How is "The Pirate Bay" any different from, say, the "Liberals" or "Conservatives" in Canada, which are almost identical politically, and both slightly left of centre? It's a tag, intended to deceive, not necessarily indicative of purpose. I doubt, for example, that the Democrats in the US actually are looking to change the political system to be a direct democracy rather than the republic it (almost) is. And some would argue that the "Labour" party in the UK isn't always fighting for the working man against their employers. Even Microsoft has made software for non-micro computers. Heck, they produce hardware (as I type this on a MS keyboard and a MS mouse is sitting beside me ... they work well with Linux!).
Names are not always indicative of purpose.
On the other hand, I suspect that their About page might still be useful in deriving their purpose.
Even giving the benefit of the doubt and calling it 8 hours, that's still once a (working) day, or 5 times a (working) week. Still not acceptable.
Of course, extrapolating a statistic out of such a small sample size (2 or even 8 hours) is somewhat premature. That may have been the only crash in 10,000 hours, just so happens it was at the beginning. Or it normally would crash 5,000 times in a year, and he just went to "safe" sites. Neither extreme seems likely, but merely possible given the low sample size.
Chrome, though, shows that we should ask an additional question: what happens when one site crashes the browser? Does it take the whole thing (and all 11 of my open tabs) with it? Or do I just lose the one tab. This is important information when figuring out the severity of the problem, too.
Still not acceptable crash rate. I'm upset when I get one crash on my entire system per week. I'm upset when I have to reboot more than once every six months. If users have high standards, developers will have to have them, too.
Same in Alberta. But that doesn't mean that some of those fines don't make it back to the municipality which then funnels portions of it right back into the police force. That is, the higher the revenue from tickets, the higher the police force's budget. It's a direct causal link, written in black and white in the law.
Not if the loader is written to avoid it. Just because you're suid-root doesn't mean you can't drop privileges before doing anything useful, such as running something. Functions like setuid are your friend.
I would have thought the easiest way is to only allow the loader to operate (at least in ldd mode) if it's suid-root. Since no one but root can do that, the loader must have been vetted by either root or by the distro (where, honestly, any number of back doors can already be put in anyway).
Let's say that Nokia decided not to play ball, and just didn't bother researching. That, too, locks out small companies, because they can't afford the billion-dollar research budget to get there.
Or let's say that Nokia decided to hoard the information. After spending the $1B, they decided to keep it a secret and not license it to anyone. The only way to get the technology was to buy it pre-made from Nokia. That, too, locks out small companies who can't afford predatory pricing from the monopoly.
I'm not sure that small companies should get a free pass just because a big corp has spent a billion on R&D.
At least this way, Nokia is likely to license their patents (because that's the only way to survive - eventually the patent runs out and they can't exact any money for it) for much less than the R&D costs, allowing smaller companies to get into the market, while Nokia spreads the R&D cost over many licensees, and ends up with a return on their investment. With many licensees, it also provides for competition in the end marketplace that, though Nokia may get a cut on each phone, will pressure phone makers to keep their prices down, or to provide unique features of value to allow them to charge more. Either way, the consumer wins: cheap phones, or pricier phones that do other things.
By the way, due to libel laws, this post may not legally be read in England.
To be safe, you may want to put that at the top of your post so anyone in England can know before they read it accidentally.
That's ok. Not only do the Brits drive on the wrong side of the road, they read posts backwards too. Bottoms up, as they so cutely say.
Get the popcorn... this is going to be an epic thread. We've already had the "Wish I was there" post, it's time for the feminist wing to turn up. Oh the objectification!
Actually, the awkward part is where a coworker "accidentally" sent a link to this article to our entire organisation. Including managers, and managers' managers. I wonder what his yearly review will say...
Because Oracle doesn't have a competing VM, but does have a competing DB? (And even has a free DB that was a direct response to MySQL?)
If I am the author of a piece of work, I may choose to offer it to the general public under a license, say GPL, LGPL, Creative Commons, whatever. But, say someone with more cash than brains comes along and doesn't want those licenses. In exchange for some consideration (usually cash), I may choose to offer the same code, which I own the copyright to, to them under a different license. Simple.
In this case, it appears that, in exchange for some consideration (probably cash, but also a job), the author chose to SELL that copyright to a third party (Rapid7) and give up further claims to the code. This does not remove anyone else's rights to the code prior to the purchase, though it may not offer future updates under the old licenses (or it may, that's up to the new copyright owner).
In exchange, the original author gets a) a job, and b) the ability to work full time on the code base he's passionate about. And probably some cash.
As to other contributors - that all depends. If the license doesn't change, then no compensation is required. If they turn around and try to add additional licenses, then it may get sticky (e.g., a binary-only license so they can embed it, or LGPL so they can derive from it or whatever).
To all that I add: IANAL.
Isn't this what PDF is for?
If davidwr is a telephone sanitizer, we don't necessarily have to wait that long...
AKA negative masses would "fall" up.
Ah, like Helium balloons.
</sarcasm> <-- for the humour impaired, and those that think I might be posting from the Southern US.